Saturday, March 22, 2014

Work package vs Activities

Work packages & Activites

Work Package is the smallest level of deliverable in WBS.
    A Work Package cannot be broken down further (decomposed) into another smaller deliverable.
    A deliverable (and hence a Work Package) provides some tangible value.
    A Work Package is recognized, required and valued by a stakeholder(s).
    A Work Package gives some sense of achievement to project team and satisfies a stakeholder(s).
    Once a deliverable (and hence a Work Package) is created, it is handed over to the stakeholder(s).
    The stakeholder(s) derive some benefit from the deliverable (and hence Work Package). They use it for the purpose it was produced.

So what is an Activity?
A series of activities produces/creates a result or a deliverable (and hence a Work Package). An activity, in itself, will not produce any result but a series of activities will RESULT into a work package.

Practical Scenario
Work Package – Think about results, outcomes, deliverable while defining a Work Package. Use nouns (creation) for defining a Work Package.

Activity – Think about work to be done or to be performed or to be accomplished while defining Activities. Use verbs (to do) while defining an Activity.

Examples
1.    “Software module X” might be defined as a Work Package. Project Team will do series of Activities to create this Work Package. These Activities might include Algorithm writing, Coding, Testing, Integration etc. Project Team might have to repeat these activities till a working deliverable (Work Package) is created.

2.    “Floor N of Building X” might be defined as a Work Package. Project Team will do series of Activities to create this Work Package. These Activities might include Painting, Wiring, Floor laying, putting furniture, Decorating, Inspection etc. Project Team might have to repeat these activities till a working deliverable (Work Package) is created.