Project Management

Please login or join to subscribe to this thread

Rework % ad Quality

linkedin twitter facebook   Estimating   Work Breakdown Structures (WBS)  
avatar
Pravin Kumar Shrivastava Associate Vice President| Aithent Technologies Pvt Ltd Gurgaon, Haryana, India
For IT projects - How would you assess the quality of the work being produced. We want to do it using efforts required in rework in compare to efforts required in producing the work. Do you see any better mechanism ?
Sort By:
avatar
saurabh mahajan PMP, ITIL, PRINCE2| vodafone Pune, Maharashtra, India
quality is expectation from the product and so best is to have baseline developed about expected output from the customer itself.... if he says he wants 1+1=2 then your quality target should be to get 2 as outcome of the project.
For efforts required to produce the work best is to use WBS. it will give you estimated efforts plus track the effort variance to get actual efforts.
For rework I would suggest to replan with the WBS and at the end you can calculate the original efforts + rework efforts.
Also, rework can be part of your cost of quality.
avatar
Pravin Kumar Shrivastava Associate Vice President| Aithent Technologies Pvt Ltd Gurgaon, Haryana, India
Thanks Saurabh, At cases, rework always indicate the quality associated with the deliverable. So suggested to use this as the mechanism to assess the quality.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
I will talked from an experience point of view (I can talk from an academic point of view but I think is not what you are looking for). After working in lot of quit different industries I can say this: You have to avoid rework. As you know, you have two phases in quality: assurance and control. If you put focus in assurance you will minimize the rework. The problem is that the hard thing to sell is quality assurance. But to sell it you can collect a lot of data and transform it into information. The data is about the amount of money and other tangible things you are lost because do not implement quality assurance which is key to avoid rework.
avatar
Dominic Law Product Manager| PCCW Global Happy Valley, Hong Kong
Agree with Sergio that rework is not a good measure. I believe it's best to have a clear product specification of the IT project, and good quality means that you have achieved the required specification. The amount of work, including resources, money and time, to achieve that specification is of course important, but that can be measured by other means such as your budget.
avatar
Seema Sonkiya Head Business Analysis Practices, PMI-PBA trainer| iZenBridge Consultancy Private Limited Jaipur, Rajasthan, India

Pravin, if we talk about rework, then our focus is on inspection. PMI gives more emphasis on "Build Quality In" rather on inspection. Quality Assurance ensure that team follows the quality management plan and produces the quality output. And the focus quality control is to verify the output of Direct and manage project work (deliverable) for its adherence to project management plan (baselines) 
avatar
Seema Sonkiya Head Business Analysis Practices, PMI-PBA trainer| iZenBridge Consultancy Private Limited Jaipur, Rajasthan, India

Pravin, if we talk about rework, then our focus is on inspection. PMI gives more emphasis on "Build Quality In" rather on inspection. Quality Assurance ensure that team follows the quality management plan and produces the quality output. And the focus of quality control is to verify the output of Direct and manage project work (deliverable)adhere to project management plan (baselines) 

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If opportunity doesn't knock, build a door."

- Milton Berle

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters