|
5.5 Control Scope The process of monitoring the status of the project, the product scope and managing changes to the scope baseline. Simple Version: Balancing changes requests against project delivery to maximize business value. | |
|
PMI |
Agile PMBOK, Agile Difference, Comment |
|
Inputs Project management plan Work performance information Requirements documentation Requirements traceability matrix Organizational process assets Tools and Techniques Variance analysis Outputs Work performance measurements Organizational process assets updates Change requests Project management plan updates Project document updates |
Inputs Project management plan / iteration and release plans Work performance information / e.g. Velocity metrics Requirements documentation / backlog Requirements traceability matrix Organizational process assets Tools and Techniques Variance analysis / e.g. Velocity analysis Outputs Work performance measurements Organizational process assets updates Change requests Project management plan updates Project document updates The PMBOK acknowledges that “change is inevitable” (p125 in PMBOK v4 Guide), agile projects emphasise processes to actively manage scope against the backlog of required functionality. Changes are not necessarily bad (they may bring competitive advantage) nor are they usually free (there is a cost of even analysing change requests). The process is a Benefit vs. Cost trade-off exercise, we must maximise responsiveness and value delivery to the business while maintaining enough stability to allow sustainable development. Approved change requests are added to the backlog for prioritisation within the list of remaining work. |
5.5 Control Scope