5.2 Define Scope

 

Back to Process Group Mappings
5.2 Define Scope The process of developing a detailed description of the project and product.   Simple Version: Describing the project scope. This will likely be refined as the project progresses, a process termed “Progressive Elaboration” in the PMBOK.
PMI	Agile PMBOK, Agile Difference, Comment
Inputs Project charter Requirements documentation Organizational process assets   Tools and Techniques Expert Judgement Product analysis Alternatives Identification Facilitated workshops   Outputs Project scope statement Project document updates	Inputs Project charter Requirements documentation / Candidate story lists / Backlog Organizational process assets   Tools and Techniques Expert Judgement Product analysis Alternatives Identification Facilitated workshops Prioritisation   Outputs Project scope statement Project document updates   A ‘detailed description of project and product” might be an unrealistic early goal or an agile project since agile projects are often in domains characterised by high requirements uncertainty and/or high technology risk uncertainty. Instead of “Define Scope” as a single activity, agile projects establish the framework for scope management (Backlogs, business prioritisation) and establish the structure for frequent reviews and revisions to manage project scope. This change in philosophy is worth spelling out in the Project Charter and communicating frequently at the early project kick-off meetings to make sure everyone understands and is on board.