Back to business after a few less-than-serious posts…. The latest ASAP for Implementation roadmap (overview page here, NOTE: requires registration to service.sap.com) was recently updated to include consistent alignment and presentation of WBS elements. The latest version of the roadmap is the culmination of several years of effort to harmonize the ASAP methodology’s treatment of outputs/deliverables (what to do) and methods (how to do things) with industry standards, especially the PMBOK Guide.
We also place much more emphasis, in the roadmap and in our training, on using the work breakdown structure as a communications tool. While the WBS should organize and define the total scope of the project — thereby forming the basis for schedules, budgets, and resource plans — it should be a tool to communicate to a wide variety of stakeholders. It is essential to have both graphical and list views available. In particular, the WBS should not be a way of overwhelming senior management with detail. It should make transparent to all what will delivered and the work required to do so.
Filed under: Communications, Complexity, Methodology, Paul Ritchie, Program Management, Project Management, SAP, Scope Management Tagged: | ASAP, ASAP for Implementation, WBS, Work breakdown structure