© mahindra satyam 2009 mahindra satyam’s quality guide

Download © Mahindra Satyam 2009 Mahindra Satyam’s Quality Guide

Post on 01-Jan-2016

223 views

Category:

Documents

4 download

Embed Size (px)

TRANSCRIPT

Mahindra Satyam Powerpoint Template*
*
Continue
Back
Quality
Management
System
Software Quality
Software Quality
variety of shoes ?
GOOD
BETTER
BEST
never having to say “I’m sorry”
doing it right the first time
being flexible and responsive to change
delivering on time and in full
tackling the source of the problem
improving your own performance
co-operating and not confronting
Best for the customer’s use and selling price - Feigenbaum
The (minimum) loss imparted by the product to society - Taguchi
*
*
*
*
Software Quality
Basis for the Turnaround of Japanese Manufacturing Industry
Shall be used Concurrently to make Quality happen
*
*
Work for Common Goals and Purposes
Define Organization Wide Procedures
Refine Organization’s Procedures
Personnel
With Fear to Enquire
Inadequate and Ineffective Supervision
To Know the Quality that is being Delivered
To Achieve Best Economy and Productivity
*
*
Choice of Vendors based on Statistical Evidence of Quality
*
*
Use Statistical Methods to Find Trouble Spots
Do Not Rely on Judgement
*
*
Statistical Methods shall be used
to identify Training Needs
*
*
Management shall provide help for the People on the Job
Statistical Methods shall be used to spot the Origin of Defects
*
*
Fear to Report Trouble
*
*
shall have an idea of the Overall Picture
shall understand Problems encountered in the Phases other than those they are working on
*
*
e.g.: “ZERO DEFECT”, “99.9% Quality”
do not contribute for better work
have a negative effect through frustration
*
*
100 wrong surgeries / week
1 cheque / day debited to wrong account
*
*
Do they take account of Quality, or only numbers?
Do they help anyone do a better job?
*
*
Train the employees in Simple but Powerful Statistical methods
*
*
Institute a Vigorous Program for Retraining People in New Skills
*
*
Principle 14
Create a Structure in Top Management that will Push Every Day on the 13 Points
*
*
Software Quality
User’s Requirements
Documented Standards (explicit)
Professional Characteristics (implicit)
*
*
Management isn’t clear about what they want
We can never find out when problems happen
They keep changing the standards
It is hard to get computer time when you need it
The salespeople wait until the last moment to send in the orders, then they want it immediately
The customers don’t know what they want
There never is enough time
*
*
What to Do to Achieve Software Quality ?
Have a program in which you can involve all the personnel for defect prevention
Find out the most difficult problems they face in doing the work
Ask them for solutions
Draw a road-map for implementing the solution
*
*
Software Quality
Set of Support Activities, such as, Planning, Training, Measurement, Analysis
needed to provide adequate confidence that processes are established and continuously improved in order to produce products that meet specifications, and are fit to use
The Theme is Be Proactive!!
*
*
Reviews of the Project Activities
Documentation of the deviations from Organization’s Standard Procedures
Project Metrics
developed during Project Planning
reviewed by trained personnel
Identifies
work products that shall be reviewed / audited
documents and records that shall be maintained
*
*
based on
Organizational Policy
*
*
consistency with the Customer’s Requirements
correctness of the Process implementation
A filter for the Software Process!
An important SQA Activity!!
Software Reviews
*
*
Software Reviews
Review Team
*
*
identification
acquirement of concessions, where feasible
*
*
Accurate Measurements are Important
Project Data is not Accounted for Individual Performance Appraisal
*
*
Quality
Software Quality
Process by which Product Quality is compared with applicable standards,
and the action taken when nonconformance is detected
The Theme is Be Corrective!!
*
*
Software Testing
Quality Compliance
Necessary Documentation
Review/Audit Reports with
description of noncompliance
proposed follow-up action