Cost Benefit

November 25, 2009
By
Cost Benefit

You need a range of tool and techniques to arrive at an effective as well as efficient quality management plan. Cost benefit analysis is one such tool used. It is well known that meeting quality requirements leads to less rework, higher productivity and less costs. All of that lead to stakeholder satisfaction. To judge...

Read more »

Quality Planning – Enterprise Environmental factors

November 23, 2009
By
Quality Planning – Enterprise Environmental factors

Several factors related to the environment of the enterprise where the project is being implemented have an impact of the quality management plan being drawn. These factors are specific to the organization and the context in which it does its business. For example, these would include things like governmental regulations that apply to the...

Read more »

Quality Planning – Stakeholder Register & Cost Performance

November 21, 2009
By
Quality Planning – Stakeholder Register & Cost Performance

Though the scope baseline is one of the most important inputs for the quality planning process, there are several other inputs that need to be considered to do an efficient and effective quality management plan. Stakeholder register, cost performance baseline and schedule baselines as well as the risk register are some more important inputs...

Read more »

Quality Planning: Scope Baseline

November 20, 2009
By
Quality Planning: Scope Baseline

Quality is a dependent requirement. Quality indicates how well the deliverables defined in the scope is being delivered. If scope definition is incomplete or captured the requirements wrongly, the project/ product will be deficient in quality in the eyes of the internal (sponsor) or the external customer. The scope baseline defines the complete scope...

Read more »

Project Quality Management in PMBOK

November 19, 2009
By
Project Quality Management in PMBOK

One of the first things one needs to remember about quality of a project or product is that in can only be obtained by conscious design. Thus like any other feature or deliverable it needs to be carefully managed such that the quality level is as designed. A complementary part of that statement is...

Read more »

Keeping Scope in control

November 9, 2009
By
Keeping Scope in control

This is a critical process in any project management. Possibly this is the most critical one. On the one hand you have to plan to a very high precision to increase the probability of success as also to have minimum and predictable costs associated with it. On the other, change is a constant. Changes...

Read more »

Scope Verification: How to – Part II

November 8, 2009
By
Scope Verification: How to – Part II

Inspection is always about checking a product or output against some specifications that these product(s)/ outputs are supposed to meet. As an example for a bolt manufactured through a manufacturing process the inspection would probably include measurements of the dimensions as per the applicable BS/ANSI or some national standard. Inspections carried out would use...

Read more »

Scope Verification: How to – Part I

November 7, 2009
By
Scope Verification: How to – Part I

There is whole set of documents you need to look at to be able to verify the scope of deliverables. The common thread that ties these documents together is that they help define the deliverables and the project context in the form of the project management plan. What do you need for Scope Verification...

Read more »

Scope Verification

November 6, 2009
By
Scope Verification

At the end of a project or a particular phase of a project one needs to verify that the scope of the project as defined by the deliverables has actually been completed. When a deliverable is completed quality control activities ensure that the completion has maintained the quality of the deliverable. But the question...

Read more »

Scope Baseline

November 5, 2009
By
Scope Baseline

Scope baseline is a part of the project management plan and acts as the reference point through the project life. It has several components. These include project scope document, the WBS itself and the WBS dictionary. Scope Baseline Document The project scope document describes the product scope descriptions, project deliverables and acceptance criteria. The...

Read more »

WBS – Dictionary

November 4, 2009
By
WBS – Dictionary

When finalized, a WBS will have several control accounts associated to work packages. More than one work package may be associated with a control account but any one work package is associated with one unique control account. Control accounts are management control points where scope, cost and schedule are integrated. These are used to...

Read more »

Decomposition

November 3, 2009
By
Decomposition

Decomposition is the activity of breaking down project deliverables iteratively. This is continued until the lowest level is reached, this level is the work package level. Work packages are set of activities that are so well defined that cost estimates and time estimates of these sets of activities can be done reliably and accurately....

Read more »

WBS: Work Breakdown Structure

November 3, 2009
By
WBS: Work Breakdown Structure

Once the project scope document and the scope document are ready, detailed planning for the project needs to start. To do that effectively the project activities need to be defined in terms of clear tasks that can be estimated well in terms of effort and time. Break down of deliverables into well defined tasks...

Read more »

Scope Statement

November 2, 2009
By
Scope Statement

The project scope statement needs to describe in detail the deliverables. The work required to create those deliverables are also to be included. The scope statement can also include specific exclusions, work that need not be done. Scope Statement The deliverables definitions as well as the exclusions help manage the expectations of the stakeholders....

Read more »

Scope Definition – Alternatives Identification

November 1, 2009
By
Scope Definition – Alternatives Identification

Tools help in defining scope well, include product analysis and alternatives identification techniques. Product analysis techniques apply to projects that have a product, not a service or a result, to be delivered at the end of the project. Alternatives identification is mainly for identifying alternate methods of achieving same results. Product Analysis Product analysis...

Read more »

Scope Definition

October 31, 2009
By
Scope Definition

Detailed description of the project and or product is what defines the scope. The project scope statement really defines what exactly needs to be done and what need not be part of the activities. The project charter is obviously the primary source for the scope definition. The major deliverables, assumptions and constraints as indicated...

Read more »

Scope: Understanding refined

October 30, 2009
By
Scope: Understanding refined

Deriving the detailed requirements from the project charter takes a lot of doing. There is a set of techniques you would need to apply to elicit the requirements from relevant people. These involve formal and informal methods of stimulating the ideas that can define breakdown of the charter requirements into detailed requirements. These individuals...

Read more »