Phases and Tasks in the Work Breakdown Structure
When you plan your work breakdown structure, you can decide whether or not to use phases and tasks. A phase is a defined and managed segment of a project. A task is a defined and managed segment of a phase.
Depending on your business goals, you may want to subdivide a project using delimiters, in addition to using phases or phases and tasks, or instead of using multiple WBS levels.
Phase numbers can be up to seven characters, including one user-defined delimiter. Most firms are satisfied with a simple three-character code. As long as you use the same number of characters from project to project, your phase numbers do not need to be consistent. For example, one project can have phase numbers 100, 200, and 300 while another has phases 001, 002, and 003. However, it may be helpful to determine a numbering method before you begin to create phases.
Task numbers can be up to seven characters, including one user-defined delimiter. Most firms are satisfied with a simple three-character code. As long as you use the same number of characters from project to project and phase to phase, your task numbers do not need to be consistent. For example, one phase can have task numbers 001, 002, and 003 while another has tasks A01, A02, and A03. However, it may be helpful to determine a numbering method before you begin to create tasks.
Reasons to Use Phases and Tasks
| Business Goal | How to Use Phases or Tasks |
|---|---|
| Project manager wants two levels of detail | If a project manager wants to see two levels of detail within a project, you can use phases and tasks. The main segments would be represented by phases, and tasks would represent the specific services within each segment. |
| Marketing professional wants to market a segment of a contract | If a marketing professional wants to market a segment of a project such as the parking garage of a larger building, you can set up phases to represent parts of the building. This allows the marketing professional to create proposals using the information on the specific segment that he or she wants to showcase. |
| Track project data for internal reporting only | Projects are usually created for external reporting purposes. If you have a need for internal reporting in addition to external reporting, you could create phases, or phases and tasks.
For example, if you want to track how much work a particular team does on a project, but you don't want this information to appear on the client's reports, you can create phases to represent teams. If you have no internal need to divide a project into parts, but do have an external need, you can use delimiters to divide the project into sub-projects. |
| Flexible reporting | Project-related reports can show each project broken out by phase or phase and task.
Phase number — The phase number fits between the contract number and the task number in the standard sorting hierarchy of Ajera CRM reports. Task number — The task number is below the phase number in the standard sorting hierarchy of Ajera CRM reports. |