Class Introduction
The session, led by Naz, focused on Agile and predictive project management concepts, particularly around scope management, requirement collection, and planning. Naz recapped the previous session on MVP and MBA, then explained Agile release planning, product roadmaps, and the iterative nature of Agile deliveries. He detailed the process of collecting requirements from stakeholders, documenting them in a requirement register and traceability matrix, and then analyzing and agreeing on scope through the project scope statement. Naz described the decomposition of project scope into a WBS, including work packages, control accounts, and planning packages, and explained the concept of the scope baseline. He also covered various methods for requirement collection, such as brainstorming, interviews, workshops, surveys, benchmarking, and prototypes. In Agile, he discussed user stories, INVEST criteria, and prioritization techniques like MoSCoW and the 100-point method. Naz distinguished between scope creep and gold plating, emphasizing the need for controlled scope changes. The session concluded with a brief Q&A and Naz announcing a break due to health reasons.
Agile Release Planning Discussion
Naz led a discussion on Agile Release Planning, explaining the concepts of MVP (Minimum Viable Product) and MBA (Minimum Business Agreement) and their roles in product development. He outlined the process of creating a product roadmap, breaking it down into releases and iterations, and emphasized the importance of empowered, self-organized teams in committing work based on their velocity. Naz also detailed the steps involved in scope management, including collecting stakeholder requirements, analyzing them against project objectives, and finalizing the project scope statement by deciding what to include or exclude.
Related Offerings
Project Scope Decomposition Methods
Naz explained the process of decomposing project scope into manageable components through Work Breakdown Structure (WBS), demonstrating how to break down large projects into smaller parts using the analogy of cutting a piece of bread. He discussed the difference between predictive and Agile planning approaches, highlighting how Agile uses user stories instead of traditional requirements and follows inverse criteria including independence, negotiability, value, estimability, size limitations, and testability. The discussion covered various methods for requirement collection including expert judgment, brainstorming, and interviews, with Naz emphasizing that project managers can customize and tailor these methods based on project needs.
Requirement Gathering and Scope Management
Naz explained various methods for requirement gathering and project scope management, including brainstorming, focus groups, questionnaires, benchmarking, document analysis, decision-making techniques, affinity diagrams, nominal group technique, observation and conversation, mind mapping, context diagrams, and prototypes. He discussed Agile prioritization methods such as the MoSCo model (Must Have, Should Have, Could Have, Will Not Have) and the CANO model, as well as the 100-point method for team collaboration. Naz also covered scope management planning, emphasizing the importance of avoiding scope creep (uncontrolled changes) and gold plating (providing extra features not agreed upon).
Scope Management Process Overview
Naz explained the scope management process, covering requirement collection, scope defense, work breakdown structure (WBS) creation, and validation through stakeholder agreement. He detailed the importance of product analysis to clarify subjective requirements into specific, measurable specifications, and explained WBS components including work packages, control accounts, planning packages, and the WBS dictionary. The session was cut short due to Naz's health issues, with plans to resume the following week at 1:30 PM.
Ready to strengthen your PMP knowledge in requirements, scope, and Agile planning?
👉 Explore our PMP Certification Training Program and build practical expertise in requirements gathering, WBS, scope management, Agile release planning, user stories, prioritization, and change control.
