Variance Analysis

Variance Analysis technique is used to find the causes why we are deviating from the scope of the work by comparing the scope baseline which consists of Project Scope Statement, WBS and WBS dictionary with the actual performance. This variance analysis helps in recommending corrective and preventive actions.

Variance Analysis technique is used under the process Control Scope process.

Inspection

Inspection is a technique to whether the output of the project/deliverable is meeting requirements/expectation. It is also called as reviews, audit, testing, walkthrough, etc…

Inspection is used as technique under Control Quality and Validate Scope processes. Also it is used under Control Procurement process with technique name as Inspections and Audits. But in general Inspection to be carried out throughout the project as part of Monitoring and Controlling process group as per the plan.

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.