Decomposition

Decomposition is a technique used to divide the scope and or the deliverable in to small components where one should be able to manage it. When we divide the scope, we arrive at the work package. Work package is the lowest level of work breakdown structure. Further this work package will be decomposed to activity level.

Now the question is what is the meaning of manage? Manage means one should be able to estimate for schedule, cost and track the same. So the level of decomposition differs from project to project based on complexity in terms of effort. Typically 8/80 rule is used in general. The meaning of this is no work package should be less than 8 hours and no work package should be greater than 80 hours. So divide the scope in such a way that the work package should be in the range of 8 hours to 80 hours.

Decomposition can be done using box type or using tools like MS Project. Engineering projects uses ISO standards for decomposition. It is organization specific.

Decomposition technique is used under two processes. One in Create WBS and the other is Define Activities.

Alternative Generations

This technique is used to identify how better we can produce the project objectives. Some of the techniques under this are brainstorming which leads to ideas, lateral thinking, out of box thinking. For example Automation is one of the ways to execute project in a better way which may save time.

Alternative Generations technique is used under process Define Scope.

Product Analysis

This technique is used whenever the project output is product. Product Analysis can be requirements analysis, Value analysis, value engineering, product breakdown structure which results in tangible output or deliverable.

Product Analysis technique is used under process Define Scope.

Document Analysis

By analyzing the existing documents one can extract lot of information or requirements. To mention a few documents business plans, drawings, issue log, policy docs, law, regulatory documents, technical documents, RFP’s, use cases, etc…

Document Analysis technique is used under process Collect Requirements.

Context Diagrams

This technique is a visual representation which shows the interaction between the business system and the user. The business system can be process, device or equipment. The person (user) who interacts with the system will be called as “Actor”. Actor provides the input to the system and the system throws the output. This output will become the information for the Actor for further analysis.

For example, as an user (Actor) I want to know my Body Mass Index (BMI). I will provide the input, to system which can be a simulator, the height and weight. The system throws the output which is BMI. Using this BMI, I will decide what action should be taken. Either increase weight or decrease weight.

Context Diagrams is used under the processes Collect Requirements.

Benchmarking

It is a technique to gather information by comparing with existing product. This will help in getting new ideas and how to improve the performance of the current product. The comparison can be internal or external.

Benchmarking technique is used under the processes Collect Requirements and Plan Quality Management.

Prototypes

It is a technique to gather the information or feedback of the product developed based on initial requirements. The product which is in the demo stage or prototype or proof of concept stage will be shown to the stakeholders. Stakeholders will provide the input for further improvements if any. These inputs can be the final requirements which can be used for design or build phase.

This technique is very much suitable in Agile environment in the software development industry.

Prototypes technique is used under the process Collect Requirements.