How to Capture Customer Requirements and Develop Project Scope with Greg Githens
What You Will Learn
Upon completion of this training, learners will be able to:
- Identify techniques for capturing both spoken and unspoken requirements.
- Ask better questions and ask them more effectively.
- Recognize characteristics of high-quality written requirements (customer centric, organized, verifiable, traceable, complete, etc.)
How can you better satisfy your customers’ needs, manage their expectations, banish scope creep, and assure project success? By capturing correct and complete project requirements!
This popular training provides pragmatic techniques for capturing, specifying, and managing requirements as part of a successful requirements management process. You will increase your skill in speeding delivery of the right solution and develop insights that can help you delight your customers with innovative solutions. It is rich with examples that will help you recognize good practices. You will learn fundamental concepts and practices through a step-by-step case study exercise. This training is applicable to any kind of project, not just software and systems.
- Recognizing Common Pitfalls in Project Requirements Capture
- How to Distinguish Wants From Needs
- How Requirements Fit to the Project Triple Constraint
- Why Distinguish Features From Benefits?
- Who Is Responsible for Determining Project Requirements?
- Why “Capture” Is a Better Word Than Gather
- Qualities of Good Requirements (solution free, verifiable, organized, etc.)
- Organizing Requirements With the Vee Model
- Introduction to Functional Analysis
- Stakeholders, Customers, and “Jobs to Be Done”
- Thinking Strategically and Anticipating Future Stakeholder Needs
- The Distinction Between Validation and Verification
- Leadership Is Leading With Questions
- Design Thinking
- A Better Way to Manage Due Dates and Deadlines
- Good Questions to Ask
- Avoiding “Solutioneering”
- Probe for Metrics
- Building Rapport
- The ESP Model of Interviewing
- Practice Customer Interview
- The Three Kinds of Scope
- Use Cases
- Functional Analysis
- Organizing Requirements Documents
- Specifying Detailed Requirements
- Quality Criteria for Requirements
- Using Stories to Develop Projects
PDU Allocation Table
|Ways of Working||Power Skills||Business Acumen||Total|
|CAPM® / PMP® / PgMP®||8||3||3||14.00|
|PMI-ACP® / Agile*||1||3||3||7.00|