Synopsis
Overview
- The WBS is a product-oriented family tree that defines all project deliverables and work to be performed. It provides a framework for planning and managing project scope, cost, schedule, risk, etc.
- There is only one WBS per project encompassing NASA in-house work as well as contracted and international partner work.
- The top 2 levels of the WBS follow NASA standard templates. Lower levels are defined by the project and contractors.
Development Guidelines
- Develop a preliminary WBS early, iterate as needed during project formulation. Baseline the WBS during implementation.
- Involve all stakeholders like systems engineering, project management, business ops. Ensure alignment.
- Extend the WBS hierarchy down to the level needed for planning, budgeting, scheduling, charging costs.
- Correlate WBS to requirements, specs, etc. Use tools like cross reference matrices.
- Control changes to baseline via configuration management processes.
Uses
- Integrates technical, schedule, cost management processes via the WBS dictionary, control accounts, work packages, etc.
- Provides common reference for all project communication and reporting up to Agency level.
Key Challenges
- Compatibility between contractor and NASA WBS structures and systems.
- Correct WBS numbering and mapping to NASA financial systems.
- Appropriate subdivision for management insight without going over 7 levels.
