Aug 6, 2012

What is a "decomposition" technique in PMP?

In scope management, project deliverables are subdivided into smaller
and more manageable components until the work and deliverables are
defined to the work package level. This is called as decomposition.

Decomposition of project scope generally involves the following activities:

* Gather information on major project deliverables and analyze related tasks

* Start development of work breakdown structure(WBS) at the highest level

* Decompose the upper WBS levels into lower level detailed components

* Identify each work package & WBS components with unique code, and

* Verify if the degree of decomposition of the work is necessary and
sufficient

* No. of Levels of WBS need not be same for all deliverables

But excessive decomposition may lead to more work without much value for
the time spent. It can also leads to inefficient use of resources, and
decreased work efficiency. So, knowing few basics about work package
helps us in deciding the level of decomposition. Few of them are:

* Work package is the lowest level of WBS

* Usually, a work package is the quantum of work which is assigned to a
single resource as a whole and produces a verifiable outcome

* Project's cost and schedule estimation is done at work package level

* The accuracy of these estimations depends on the level of detailed
work package that is defined

* The level to which work packages need to be detailed vary from project
to project

In Time Management, each work package within the WBS is decomposed into
the activities required to produce the work package deliverables.

No comments: