|
5.3 Create WBS The process of subdividing deliverables into smaller, more manageable components. A WBS is a deliverable-oriented hierarchical decomposition of work Simple Version: Break the project down into simpler and simpler steps until a project can be discussed, and estimated at a granular level. |
|
|
PMI |
Agile PMBOK, Agile Difference, Comment |
|
Inputs Project scope statement Requirements documentation Organizational process assets Tools and Techniques Decomposition Outputs WBS WBS dictionary Scope baseline Project documentation updates |
Inputs Project scope statement / Story List / Backlog Requirements documentation Organizational process assets Tools and Techniques Decomposition Outputs WBS WBS dictionary Scope baseline Project documentation updates You can create a traditional style WBS for agile projects, but the backlog and release plans contain the same information in an easier to refactor format. Most WBS tools are difficult to refactor (make changes to) given agile projects accept that requirements are likely to change, using a tool that is quite difficult to make whole-scale changes to can lead to a lot of time being spent on updating deliverables that could be better used delivering business functionality. If you have a tool that easily allows WBS changes (I like WBSPro) then go ahead and create one, it may make interaction with some stakeholders easier. Be aware though that a Backlog is a very practical “deliverable-oriented decomposition of work”. If the backlog has too many items for people to visualise the project structure, Parking Lot diagrams are an excellent way of showing hierarchical structure and how things fit together. |
