Developing Requirements aims to help you advance your business analysis career by giving you the skills needed to elicit the best requirements.
Get to the Next Step as a Business Analyst by Mastering Requirements Elicitation
Business analysis is easy, right? You just ask your stakeholders what they want and write down their responses... No! Experienced Business Analysts know that real requirements development is a challenging endeavor, requiring a number of interviewing, observation, group facilitation, and documentation skills.
In this course, we'll step through how to plan effective requirements development phases for your project, cover the skills you need to run them effectively, and set you up for success in developing solutions to your organization's problems.
In this course, we'll cover:
How to plan your project's analysis phase. Determine where your requirements input should come from. Learn how best to gather requirements from those sources. Choose the best form of plan for your project.
How to gather requirements. Learn how to interview and observe stakeholders. Run effective brainstorming and group interview sessions. Learn the basics of JRP Session facilitation. Run surveys and focus groups. Gather requirements from documents and systems.
How to document requirements. Learn how to organize and categorize your notes into tangible requirements input. Streamline it to avoid duplication and bad requirements. Frame it all into a coherent document.
Throughout the course, you'll also see how the course material works in the real world through a series of scenarios.
This lecture covers where requirements come from: people, documents, and systems.
When we have a lot of stakeholders, it's inefficient to handle them all one-on-one. This lecture covers how to classify them effectively.
Once we know who our stakeholders are, and how they're classified, it's time to figure out how we're going to elicit requirements from them... which we cover in this lecture.
A requirements development plan will help to keep us on track. This lecture covers how to come up with an easy light-weight plan.
In this lecture we go through two scenarios which cover everything in this section.
One-on-one interviewing is the most common requirement-gathering method -- and one you must master. Learn how in this lecture.
Scenario time! See how Doug (our BA) interviews Solomon (our project sponsor).
Scenario time again! This is a more detailed scenario with Doug and Martha (the Product Analyst).
Observation is another critical skill in the BA toolbox. Get up to speed on it in this lecture.
Scenario again! See how Doug observes Martha as she works.
Group interviewing can be a powerful way to save time while gathering requirements from stakeholders. This lecture covers the unique skills you'll need.
Yes... another scenario! Here, Doug interviews several Product Managers all at once.
Brainstorming is a fun and effective way for gathering lots of input all at once. Here we'll cover how to do it effectively.
If you want to be a master Business Analyst, you'll need to know how to run JRP and JAD sessions. In this lecture, we cover the dynamics.
Focus groups can help you learn about stakeholder attitudes towards products and processes. This lecture covers how to run them most effectively.
Surveys can help you get feedback from dozens or hundreds (or more) of stakeholders in a relatively short timeframe. Learn how to develop and execute surveys in this lecture.
Documents contain tons of valuable information that your stakeholders might not even be aware of. Learn how to review them effectively in this lecture.
In this lecture, we'll cover systems as requirement gathering tools. Learn about interface analysis, reverse engineering, and prototyping here.
There's no point gathering requirements if we don't document them. In this lecture, we cover the best approach to doing so.
Organizing and categorizing your input will help ensure that your final requirements are solid. Learn how in this lecture.
In this lecture, we cover how to streamline all the requirements input you've received from your sources.
In this lecture, we cover the writing part of documenting the requirements.
In this lecture, we will cover some "interesting" situations that often cause problems for both novice and expert BAs.
This is where we wrap up the course (and say "thank you").
Don Hussey serves as Managing Director with NorwalkAberdeen.
Prior to founding NorwalkAberdeen, Mr. Hussey was Senior Vice President of Global Internet Strategy for a global financial institution. In this role, he drove online strategy for the private bank, oversaw all business analysis and project management for the bank’s online channel, and overhauled the way these functions were run.
Before this role, Mr. Hussey was a star Project Manager/Business Analyst with a major investment bank. There, he managed the delivery of numerous critical projects and participated on teams that re-engineered the project oversight process and introduced user-focused development disciplines.
Earlier in his career, Mr. Hussey held various roles in sales and sales management, client service, operations, and technology.