“Would you remember to assist me print out this Function Breakdown Framework? It will not likely in shape to just one page, and I have a project standing assembly with the project sponsor in a few minutes!” A colleague of mine approached me and asked. “This is a project program in the form of a hierarchical framework.” I replied sarcastically when I saw her drawing on the display screen. She had listed all project deliverables then decomposed each individual just one into appropriate jobs. This is not what a Function Breakdown Framework (WBS) is supposed to be utilised for. Does the project sponsor or the consumer want to know how you are heading to total each individual deliverable? Do you genuinely want to current scores of deliverables and jobs to get your sponsor to concur on your project scope? Completely, you want not.
The Function Breakdown Framework is a deliverable-oriented, hierarchical decomposition of the function to be completed by the project staff. It is a Tree Diagram in which the project is broken down into deliverables and sub-deliverables wanted to carry out the project targets. It appears to be like the organizational framework of a enterprise or a loved ones tree.
This project management device defines the project’s scope, and it have to be straightforward in purchase to reap the supposed added benefits. To start with, it depicts the boundaries of the project scope. If it is properly-structured and features nothing at all but the project deliverables, the consumer or the sponsor can easily sign it off. Secondly, it makes certain that energy is not wasted on unwanted or out-of-scope deliverables. That is, if redundant components are listed, excess methods, time and charge will be expected for that reason. Eventually, it can be utilised as a dashboard to talk scope alterations, hence helps prevent scope creep. The much more difficult the Function Breakdown Framework is, the considerably less likely you will achieve these targets.
The supposed use of this device tends to make it different from the project program. The Breakdown Framework does not include things like activities it only lists deliverables down to the Function Deal level, whereas the project program lists all jobs expected to total the deliverables.
From yet another point of view, the hierarchical decomposition of function depicts the everyday living cycle via which the project evolves from inception to completion. In a program progress project, for instance, the project everyday living cycle may consist of the next major phases:
1.two Design and style
Every single just one of the phases can be broken down into its major deliverables. For case in point, the Analysis stage may be decomposed into ‘Glossary’ and ‘Requirements Specifications’. Every single deliverable is then decomposed into sub-deliverables, and so on. The Analysis stage can be broken down as shown in the next framework:
1.1.two Prerequisites Requirements
1.1.two.1 Use Situations
1.1.two.two Supplementary Requirements
1.1.two.3 Reporting Prerequisites
The decomposition process should really end when you attain the smallest manageable components of the project function, known as Function Offers. A Function Deal is the cheapest-level part whose charge and time can be reliably estimated. For case in point, ‘Reporting Requirements’ sub-deliverable can be broken down into two function deals: ‘Financial Reports’ and ‘Operational Reports’, each individual of which can be estimated in terms of charge and time expected to total their progress.
It is well worth mentioning that the project management deliverables are element of the project function, as a result, they should really be listed in the framework as properly. Just one way to incorporate these deliverables is by creating a individual stage, named Project Management, and decomposing it into its components. Examples of deliverables that can be listed less than this stage are Project Management Strategy, Risk Strategy, Scope Assertion and Project Plan.
Whilst the Function Breakdown Framework is progressively elaborated, i.e. developed in increments as the project progresses, the project manager should really make guaranteed that it is total. Completeness is accomplished when a hundred% of the agreed scope is covered. You can test completeness bottom-up that is, sub-deliverables make up a hundred% of their parent deliverable, deliverables make up a hundred% of their parent stage, and phases constitute a hundred% of the project scope.
Only immediately after the decomposition process has been completed and approved, the project program is made. For each individual function package, the project staff members listing the jobs expected to total the package. Then, time, dependencies, methods and charge are allocated to each individual task. When all particulars have been estimated, the project program is approved and the program baseline is established.
In conclusion, the Function Breakdown Framework is an vital device to established the project scope. It kinds the settlement among you and your consumer on what is included and what is not included in your finish deliverable. Nevertheless, to be effective, it have to be straightforward and, much more importantly, have to not be confused with the project program that serves a different goal in your project management approach.