Over 61% of projects fail (according to the Standish Group Chaos Report) – never making it to implementation or delivering less than expected capabilities. Unclear or missing project requirements is one of the 4 top reasons associated with project failure. The discovery of missing, out of scope or poorly defined Business Requirements frequently occurs much too late in the project lifecycle, driving avoidable and costly project rework.
During this 3 part webinar series, students will learn about 4 common mistakes in the requirements definition process which result in failure to define the “real” business needs or “Whats” for a project. They will learn why starting with a project solution – even when the business stakeholders think they really know what they want, will likely lead to project rework after the solution is delivered.
Students will learn how to discover and close gaps in their Business Requirement document and how to ensure that traceability exists between every proposed technical requirement and the approved project business requirements.
Learning objectives for the Requirements Definition Series include:
- Using the Project Scope Statement as the foundation and guide for identifying all of the project’s business needs
- Techniques for differentiating between project “What’s” and project “How’s”
- How to focus stakeholder participation on business drivers and project needs before discussing solutions
- Using the “Wave Concept” to progressively elaborate through detail levels of requirements
- Techniques to uncover the gaps in the Business Requirements documents before establishing the Scope Baseline for the project
- Creating traceability between business requirement statements and project solutions and knowing when to exclude requirements from the project effort
All webinars in this series align to the PMI Talent Triangle – Technical