WBS template I developed is based on high level view of project management, mentioned in my earlier article: http://seema-sonkiya.blogspot.in/2012/05/seema-sonkiya-pmp-project-management.html
Note: WBS is deliverable oriented hierarchical decomposition of project work, so my template only shows deliverables.
1. Pre Initiation
1.1. Contract
1.1.1. Seller terms & conditions
1.1.2. Buyer terms & Conditions
1.2. Business Case
1.3. SOW
1.4. Project proposal
2. Project Initiation:
2.1. Project Phases identification report (i.e. Project Initiation, Project Environment Set up, Release Planning, Iteration Initiation, Iterations, Iteration Close, Project Close)
2.2. Understand SOW, Contract and Business case
2.2.1. Alternative analysis
2.2.1.1. High level requirement, usually refinement of provided SOW
2.3. High level Risks
2.4. Summary milestone activities
2.5. Project Budget
2.5.1. Analyze contract type
2.5.1.1. Summary Budget (+-50%, if contract type is not Fixed Price)
2.5.1.2. Assumption Log
2.6. Resource pre-assigned
2.7. Success criteria and Measurable Project Objectives, forms the basis of project & Product quality.
2.8. Project Approval requirements.
2.9. List of major deliverables
2.10.Project Manager authorities and responsibilities.
2.11.Stakeholder Analysis
2.11.1. Stakeholder Register
2.11.2. Stakeholder management strategy
2.12.Project Kick off meeting MOC
2.13.Register Project
3. Configuration Management
3.1. List of CI
3.2. Change Log report
3.2.1. List of CI in impact analysis
3.2.2. Relationship with incidents or blocks and problems
4. Project Environment Setup
4.1. Management Plans (tailored from organization process assets)
4.2. Communication Plan
4.3. Detailed Life cycle definition
4.4. Team directory of acquired team members.
5. Release Planning
5.1. Product Backlog
5.1.1.1. QFD
5.1.1.1.1. Core features
5.1.1.1.1.1. Modules
5.1.1.1.1.1.1. Sub Modules
5.1.1.1.1.1.1.1. Stories with estimates +10%, estimated in ideal days as these are discrete efforts (reference of Document) – fitness for Purpose
5.1.1.1.1.1.1.1.1. Acceptance criteria may be high level, refined in iterations. – Fitness for Use
5.1.1.1.2. Needed Features
5.1.1.1.2.1. Modules
5.1.1.1.2.1.1. Sub Modules
5.1.1.1.2.1.1.1. Stories with estimates +10%, estimated in ideal days as these are discrete efforts (reference of Document) – fitness for Purpose
5.1.1.1.2.1.1.1.1. Acceptance criteria may be high level, refined in iterations. – Fitness for Use
5.1.1.1.3. Luxury features
5.1.1.1.3.1. Modules
5.1.1.1.3.1.1. Sub Modules
5.1.1.1.3.1.1.1. Stories with estimates +10%, estimated in ideal days as these are discrete efforts (reference of Document) – fitness for Purpose
5.1.1.1.3.1.1.1.1. Acceptance criteria may be high level, refined in iterations. – Fitness for Use
5.1.1.2. Training need document
5.1.1.3. Process improvement activity log (updated anytime)
6. Iterations
6.1.1. Iteration Number
6.1.1.1. Meetings
6.1.1.1.1. Sprint Planning meeting
6.1.1.1.1.1. Sprint Backlog
6.1.1.1.1.1.1. Selected user stories
6.1.1.1.2. Daily Scrum
6.1.1.1.2.1. Block Lists (updated daily)
6.1.1.1.3. Sprint Cancellation (rare)
6.1.1.1.3.1. Detailed report
6.1.1.1.4. Sprint Review
6.1.1.1.4.1. Sprint retrospective
6.1.1.1.4.2. Verify Scope
6.1.1.1.4.2.1. Customer feedback
6.1.1.1.4.3. Lesson learned
6.1.1.1.5. Risk Management Planning meeting
6.1.1.1.5.1. Risk Management Plan
6.1.1.1.6. Risk Audit
6.1.1.1.6.1. Audit report
6.1.1.1.7. Risk assessment/ reassessment and Risk status meeting
6.1.1.1.7.1. Meeting ID
6.1.1.1.7.1.1. Risk register
6.1.1.1.7.1.2. Effectiveness of Risk response report
6.1.1.1.8. Quality Plan (for each iteration as scope refined with each iteration)
6.1.1.1.8.1. Quality metrics
6.1.1.1.8.2. Quality check lists
6.1.1.1.8.3. Quality Management Plan
6.1.1.1.9. Human Resource (human resource requirement may change with each iteration)
6.1.1.1.9.1. Project Organization chart
6.1.1.1.9.2. Team performance assessment
6.1.1.1.9.3. RACI Chart
6.1.1.1.9.4. Resource breakdown structure
6.1.1.1.9.5. Performance appraisal report
6.1.1.1.10. Communication Planning (may be updated with each iteration)
6.1.1.1.10.1. Communication Plan (updated)
6.1.1.2. Visual Feedbacks:
6.1.1.2.1. Burn down chart
6.1.1.2.1.1. Earn value report
6.1.1.2.1.2. Architecture Diagram
6.1.1.2.1.3. Database
6.1.1.3. Increments
6.1.1.3.1. Shippable functional tested
6.1.1.3.2. Story left out report and returned back to product backlog
6.1.1.4. Design & Construction (interleaved)
6.1.1.4.1. Detailed Design Doc(project scope statement, that is greater level of details for the selected stories and in high level for future iterations)
6.1.1.4.2. Estimates (-5 to 10%)
6.1.1.4.3. Unit tested deliverables
6.1.1.4.4. Quality Control measurements
6.1.1.4.5. Quality Audit report
6.1.1.5. Other deliverables
6.1.1.5.1. Activity list
6.1.1.5.2. Activity attributes
6.1.1.5.3. Assumption log
6.1.1.5.4. Work performance information (i.e. Cost incurred)
6.1.1.5.5. Performance reports including forecasts
7. Iteration Initiation
7.1. Stakeholder Analysis
7.1.1. Stakeholder register (updated)
7.1.2. Stakeholder management strategy (updated)
7.1.3. Analysis of whether project is on track to deliver business benefits
8. Close Project
8.1. Financial closure report
8.2. Feedback
8.3. Lesson learned
8.4. Project files achieved
8.5. Final performance reporting
8.6. Celebration!!
Seema Sonkiya
Excellent template.
ReplyDeleteThanks Aziz!
DeleteThis is very detailed template. Do you use this as a template in your projects ?
ReplyDeleteYes Ameet we use this as a template in our projects. WBS must show all of the project and product deliverables. It is communication tool and project team members can see their roles. It describe how lower level derive from upper level deliverables. It is very useful tool for a project.
DeleteI received following comment through linkedin:
ReplyDeleteLinkedIn Groups
Group: PMO
Discussion: WBS template based on high level view of project management- just earlier article: http://seema-sonkiya.blogspot.in/2012/05/seema-sonkiya-pmp-wbs-template.html
Its a great effort by you to produce and publish this WBS hierarchical structure of project's product and project scope in the form of deliverables. This definitely can be a good tool to understand work breakdown structure (WBS) for those interested in it.
Posted by Mazhar Lari, PMP
-------------
Thanks Mazhar!!
Job well done :) Thanks Seema.
ReplyDeleteThanks kyehia!!
Delete