Requirements Discovery for Business Analysts - 2023
Sergey Shimansky
37:57
Description
Introduction to Requirements Discovery for Business Analysts: Gather Team, Build Agenda, Run Meetings, Create Outcomes.
What You'll Learn?
- Overview of Requirements Discovery for Business Analysts and Product Owners
- Understand the stages of a Requirements Discovery and the Business Analyst's role in each of these stages: Preparation, Execution, Analysis & Transition
- Know roles on your Discovery Team: Consulting Lead, Business Analyst, Solution Architect, Project Manager
- Learn what deliverables Business Analysts need to prepare as a result of the Discovery
- How to create and maintain the Agenda for Discovery workshops and interviews
- What are the different types of Discovery meetings: Show-and-tell, Workshops, Interviews
- Typical Mistakes that need to be avoided at your Discovery engagement
Who is this for?
More details
DescriptionLEARN THE FUNDAMENTALS OF REQUIREMENTS DISCOVERY IN A SINGLE 38 MIN CRASH COURSE!
In less than 1 hour, I teach why successful Business Analysts and Product Owners run Requirements Discovery sessions for their Digital Projects, the purpose of the Preparation, Execution, Analysis & Transition phases of Discovery, and what deliverables are typically produced as a result of Discovery. All in One Course!
Have you ever been wondering - why we, business analysts, product owners, or other folks on the team, keep asking the client the same old questions about the project scope, business goals, or specifics of the client's workflow ... again and again?
Shouldnât we already know it or shouldnât someone in our organization have captured this before? And I bet you have heard the client telling you, frustratedly: âWe have already told it!â, or âYou guys need to align with your other team thatâs been asking us the same thing!â
Some project teams and business analysts, sometimes tend to think of requirements gathering and elicitation as an ongoing process, something that doesnât have a definite end. We are constantly discovering new requirements, aren't we? Well, though this is partially true, and in Agile we keep refining the backlog as we go, the sober reality is that clients donât necessarily think the same way. They pay us - vendors, consultants, and agencies - to ensure that project requirements and expectations are captured, understood, estimated, and communicated to the project team early on. Clients also expect us to start software development projects and consulting initiatives with a deep dive into their subject matter, and specifics of their business to define the exact problem they are trying to solve. Business analysts and other industry professionals call this deep-dive - Requirements Discovery phase of the project, or simply - Discovery.
I have been involved in software development projects for Healthcare, Retail, Automotive, Energy, and Public sector companies for more than 17 years, and have been blessed to lead project teams in my roles as a Business Analyst, Consulting Lead, and Project Manager. I have seen it many times as teams and sometimes clients repeatedly make the same mistake - neglecting the importance of properly conducting the Discovery phase. Or they may be doing Discovery but are not getting the best results out of it, or not sharing results across various members of their teams and client organization.
I have created this crash course to help teams better understand the purpose of Discovery and give practical recommendations to business analysts about planning, building an agenda, scheduling, gathering the team, capturing results, and sharing these across the organization. This course is based on years of hands-on experience in planning and leading successful discovery engagements for Fortune 500 organizations, in the United States and Europe.
This course is designed for Business Analysts, Product Owners, Project Managers, Solution Architects, and other project leaders involved in the planning or executing software development and consulting projects.
Here's what you'll learn:
How to prepare, execute and wrap up discovery engagements
What is a Discovery team and what is the role of the Business Analyst on the team
How to create discovery Agenda and prepare for the meetings
Different types of discovery meetings: show-and-tell, interviews, workshops, etc.
What artifacts should be created as a result of a discovery: backlog, user stories, Sprint #1
How to run the knowledge transfer and transition artifacts to the delivery team
Specifics of online/offline discovery workshops.
Extra: Discovery checklist
Extra: Further courses and recommended reading
ENROLL TODAY and join me and many others on the path to successful Requirements Discovery!
Who this course is for:
- IT Business Analysts
- IT Product Owners
- IT Project Managers
- IT Solution Architects
LEARN THE FUNDAMENTALS OF REQUIREMENTS DISCOVERY IN A SINGLE 38 MIN CRASH COURSE!
In less than 1 hour, I teach why successful Business Analysts and Product Owners run Requirements Discovery sessions for their Digital Projects, the purpose of the Preparation, Execution, Analysis & Transition phases of Discovery, and what deliverables are typically produced as a result of Discovery. All in One Course!
Have you ever been wondering - why we, business analysts, product owners, or other folks on the team, keep asking the client the same old questions about the project scope, business goals, or specifics of the client's workflow ... again and again?
Shouldnât we already know it or shouldnât someone in our organization have captured this before? And I bet you have heard the client telling you, frustratedly: âWe have already told it!â, or âYou guys need to align with your other team thatâs been asking us the same thing!â
Some project teams and business analysts, sometimes tend to think of requirements gathering and elicitation as an ongoing process, something that doesnât have a definite end. We are constantly discovering new requirements, aren't we? Well, though this is partially true, and in Agile we keep refining the backlog as we go, the sober reality is that clients donât necessarily think the same way. They pay us - vendors, consultants, and agencies - to ensure that project requirements and expectations are captured, understood, estimated, and communicated to the project team early on. Clients also expect us to start software development projects and consulting initiatives with a deep dive into their subject matter, and specifics of their business to define the exact problem they are trying to solve. Business analysts and other industry professionals call this deep-dive - Requirements Discovery phase of the project, or simply - Discovery.
I have been involved in software development projects for Healthcare, Retail, Automotive, Energy, and Public sector companies for more than 17 years, and have been blessed to lead project teams in my roles as a Business Analyst, Consulting Lead, and Project Manager. I have seen it many times as teams and sometimes clients repeatedly make the same mistake - neglecting the importance of properly conducting the Discovery phase. Or they may be doing Discovery but are not getting the best results out of it, or not sharing results across various members of their teams and client organization.
I have created this crash course to help teams better understand the purpose of Discovery and give practical recommendations to business analysts about planning, building an agenda, scheduling, gathering the team, capturing results, and sharing these across the organization. This course is based on years of hands-on experience in planning and leading successful discovery engagements for Fortune 500 organizations, in the United States and Europe.
This course is designed for Business Analysts, Product Owners, Project Managers, Solution Architects, and other project leaders involved in the planning or executing software development and consulting projects.
Here's what you'll learn:
How to prepare, execute and wrap up discovery engagements
What is a Discovery team and what is the role of the Business Analyst on the team
How to create discovery Agenda and prepare for the meetings
Different types of discovery meetings: show-and-tell, interviews, workshops, etc.
What artifacts should be created as a result of a discovery: backlog, user stories, Sprint #1
How to run the knowledge transfer and transition artifacts to the delivery team
Specifics of online/offline discovery workshops.
Extra: Discovery checklist
Extra: Further courses and recommended reading
ENROLL TODAY and join me and many others on the path to successful Requirements Discovery!
Who this course is for:
- IT Business Analysts
- IT Product Owners
- IT Project Managers
- IT Solution Architects
User Reviews
Rating
Sergey Shimansky
Instructor's Courses
Udemy
View courses Udemy- language english
- Training sessions 12
- duration 37:57
- Release Date 2023/03/16