Some project managers try to shorten their schedules by reducing the time spent on quality-assurance practices such as design and code reviews. Some shortchange the upstream activities of requirements analysis and design. Others--running late--try to make up time by compressing the testing schedule, which is vulnerable to reduction since it’s the critical-path item at the end of the schedule.
These are some of the worst decisions a person who wants to maximize development speed can make. In software, higher quality (in the form of lower defect rates) and reduced development time go hand in hand.

• Management is committed to a formalized Quality policy
• Form a management level Quality improvement team (QIT) with responsibility for Quality improvement process planning and administration
• Determine where current and potential Quality problems lie
• Evaluate the cost of Quality and explain its use as a management tool to measure waste
• Raise Quality awareness and personal concern for Quality amongst all employees
• Take corrective actions, using established formal systems to remove the root causes of problems
• Establish a zero defects committee and programs
• Train all employees in Quality improvement
  
• Hold a Zero Defects Day to broadcast the change and as a management recommitment and employee commitment
• Encourage individuals and groups to set improvement goals
• Encourage employees to communicate to management any obstacles they face in attaining their improvement goals
• Give formal recognition to all participants
• Establish Quality councils for Quality management information sharing
• Do it all over again – form a new Quality improvement team

At India-IT it's not enough to talk the talk by saying that software quality is important, you have to:

• explicitly define what is meant when you say 'software quality',
• create a set of activities that will help ensure that every software engineering work product exhibits high quality,
• perform quality assurance activities on every software project,
• use metrics to develop strategies for improving software process, and as a consequence, improving the quality of the end product.