| Content Levels | |
| Register for free access to papers, case studies, and almost 50 templates. | |
| Subscribe for complete access: $14.95 monthly or $149/year | |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Quick Summary
This is the first of a series of six templates for project plan development.
What this is
This template lists the process steps for developing a work break down structure that identifies all the tasks in the project's work. Examples are provided to demonstrate the results.
Why it's useful
Breaking the work down into individual tasks without the detail of dates, dependencies, and named resources helps accomplish the following key objectives:
How to use it
Review the discussion below on the process steps, then begin identifying major work efforts. A key to successful project scheduling is to break down the project work goals into tasks BEFORE you consider delivery dates, resource constraints, or task dependencies. This helps you to objectively identify all of the work necessary without subconsciously leaving out real work in order to fit date constraints. These tradeoffs must be made consciously and with the proper consensus involved.
Break the major work efforts into lists of tasks ordered to match your organizational and internal work methodology. Apply top down and bottom up task lists and work for coherency. Begin by referencing the Project Mission Statement and Project Vision developed through other templates. Engage the project team to analyze and write up the tasks in a sequence of layered task definitions until the detail defines a manageable project. A simple indented list is a good starting point as it goes quickly and is usually translatable into graphical and project management tool formats.
The primary objective is to get all of the team participants to contribute to the definition of the work. In practice this usually is done in evolving layers until the tasks represent very specific work by the responsible individuals and of a duration of 1 to 2 weeks depending on the total time of the project. The task duration may have less detail and longer duration if it is clearly understood and represents well-known work in which the team is experienced and successful. The goal in breaking the work tasks down is to ensure that all of the work that is needed to meet the project's objectives is recognized and planned for from the beginning. The tasks need to be identified, assigned to one owner and given completion criteria that are clear and measurable.
The hierarchical and logical structuring of work can have many inputs, all of them reinforcing:Plan Development: Task Assignment and Deliverables ![]()
Track the assignment of project tasks to individual owners, along with the deliverable description and effort required.
Plan Development: Logical Relationships and Dependancies ![]()
Identify and capture task dependancies.
Plan Development: Task Duration ![]()
Process for estimating and assigning task durations.
Plan Development: Project Scheduling and Critical Path ![]()
Checklist of project scheduling activities.
Plan Development: Optimizing Tradeoffs ![]()
Optimize a project plan after the first pass base schedule has been developed.
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy