Showing posts with label decomposition. Show all posts
Showing posts with label decomposition. Show all posts

Wednesday, December 5, 2007

Project Decomposition and Templates

To complete any task, you need to know what tools are at your disposal. Project managers who are engaged in defining project activities use two main tools to accomplish this task: decomposition and templates.

Decomposition
Decomposition means breaking a project deliverable down into a list of achievable activities.

Telecom Corp. is a telecommunications company. One service that it provides to its clients is the virtual private network (VPN). VPN project deliverables include a firewall, routers, encryptors, Internet service, IP backbone, and secure remote access.

The last deliverable could be decomposed into the following three activities:
  1. provide remote access
  2. provide encryption key
  3. authenticate users
After dividing a deliverable into potential activities, the team must evaluate each activity using the following six criteria.
  1. Status is measurable.
  2. Sign of completion is visible.
  3. Start and end conditions are clearly defined.
  4. Time and cost are easily estimated.
  5. Duration has acceptable limits.
  6. Work assignments are independent.
The first criterion to consider is whether the activity's status is measurable. For example, one deliverable in a Telecom Corp. VPN project is secure remote access. One activity defined for this deliverable is authenticating users, and it is measurable. When half the users have working login IDs and passwords, the activity is fifty percent complete.
Whether there is a visible sign that the activity is complete is the second criterion. This sign could be the delivery of a document or product, or it could be the manager's signature. In the Telecom Corp. example, the visible sign that users have been authenticated to the network is when all users can access the network with a functional user password.

The third criterion to use is whether an activity has clearly defined start and end conditions. Once the beginning event has occurred, work may begin on the activity and continue to a visible sign of completion. For Telecom Corp., the authentication activity should only begin when the network is in place. The authentication activity is clearly finished only when the users are able to use their login IDs and passwords to access the VPN.

Whether activity time and cost can be easily estimated is the fourth criterion to consider. This is accomplished by estimating the time and cost of a project's activities. In the Telecom Corp. example of authenticating users to the VPN, time can be estimated at a few days.

The fifth criterion to examine is whether an activity's duration is within acceptable limits. Although there is no set rule on this, projects should avoid activities with long durations. Delays in such activities can create serious scheduling problems. In evaluating Telecom Corp.'s authentication activity, duration can be estimated at a few days. Delays here would not create huge project delays or large-scale scheduling problems. The authentication activity then meets this fifth criterion.

The final criterion is an activity's level of independence from other project activities. Independence in an activity means that once work has begun on the activity, it may continue without interruption. For example, once Telecom Corp.'s authentication activity begins, it is not dependent upon any other project activities for completion.

Templates
The second tool a project manager and team uses to define project activities is a template. A partial or total activity list, or WBS from a previous project, can be used as a template for a current project. Using templates simplifies project activity definition and reduces project costs by improving team efficiency.

To define project activities, project managers use decomposition and templates. Decomposition means breaking project deliverables into achievable activities. A template is a partial or total WBS, or activity list defined in a previous project, which can be used in a current project.

Friday, August 17, 2007

The Process of Project Decomposition

In most instances, it is much easier to solve a problem once it has been broken down into smaller, more manageable parts. How do project managers do this? The answer lies in decomposition.

Decomposition involves subdividing the major project deliverables into smaller, more manageable components until the deliverables are defined in sufficient detail to support development of the project activities involved in planning, executing, controlling, and closing the project. These smaller constituent components then become the basis for creating a project's Work Breakdown Structure (WBS).

The process of project decomposition entails three major steps. These steps will enable you to divide all work, regardless of complexity, into manageable elements. Once you have completed these steps, you will have a workable WBS.

1. Identify the phases and deliverables of the project.
The names of the phases are usually such things as project management, design, development, testing, and integration. The project phases form the basic outline for how the project will unfold. They become the first level of the project's WBS.

A deliverable is any measurable, tangible, verifiable outcome, result, or item that must be produced to complete a phase. You should divide each project phase into its deliverables. These deliverables become the second level of the project's WBS.

2. Determine if deliverables require further decomposition.
A deliverable requires further decomposition if cost and duration estimates cannot be developed at this level of detail. How do you determine whether you can develop adequate estimates of cost and duration? Project managers must answer two questions to determine if they can develop adequate cost and duration estimates for each deliverable.
  • First, can the project manager state the approximation of the cost of the resources needed to complete the deliverable?
  • Second, can the project manager define the number of work periods required to complete the deliverable? A work period is usually expressed in workdays or workweeks, not including holidays or other nonworking periods.
If the project manager can answer "yes" to both questions, the decomposition process is complete for that deliverable. If the answer is "no" to either question, the project manager will have to proceed to the third step to further decompose the deliverable. Remember, this step is repeated for each deliverable.

3. Identify constituent components of deliverables.
The third step in the decomposition process is identifying the constituent components of the deliverables. The constituent components are referred to as activities. They become the third level of the WBS. As with deliverables, you should define the activities in terms of how the project work will be organized and accomplished.
  • Activities should be results-based. You should describe activities in terms of tangible, verifiable results to facilitate performance measurement.
  • Activities can be products or services. Activities can include services as well as products. For example, "weekly status reporting" is a service, while "writing software code" is a product.
Once you've identified the activities, you need to do more cost and duration estimating, just as you did for the deliverables. If the component is too broad to develop an accurate estimate, continue to break the constituent components down further.
Constituent components of activities are referred to as tasks or work packages. These components become the fourth level of the WBS. Once you can determine cost and duration estimates, you have finished the decomposing process for that task.

If you apply the three steps of the decomposition process, you can create a WBS that will make your project more manageable and increase the chance of its success.