Several product development teams use Q-Gate milestones to track, communicate, and move forward at various stages of development. Each milestone, identified by a number (for example, M260), indicates the progress of all related processes/projects, including technical documentation.
So, what is Q-Gate?
Here’s an extract from a 3-page White Paper by Ron Younack, Director, RCG Information Technology:
One of the techniques employed within quality assurance is a quality gate (Q-gate) concept. A Q-gate process, when used in conjunction with project management, helps manage the balance between software cost, functionality, and quality. A Q-gate marks the formal end to a particular process within the software development lifecycle, a “gate” through which the project proceeds when moving from one phase to another.
Each Q-gate process results in the certification that all appropriate work products required to move forward to subsequent project activities have been completed and reviewed, and meet quality expectations. Using a set of pre-determined exit criteria established for each phase or milestone
being certified, a Q-gate results in a pass/fail decision for moving forward.The benefits of the Q-gate concept are:
- Project stakeholders share responsibility with the project manager for the project’s quality outcome.
- Q-gates provide a mechanism for the project team to readily assess the quality of their work products throughout the project life cycle and improve quality at the source.
- Q-gates ensure that intermediate work products meet the needs of downstream activities through a formal, disciplined process. Problems, their resolution, and opportunities for improvement are identified; and risk assessment or escalation procedures are invoked, if appropriate.
- Q-gates enhance project communications, thereby resulting in improved management of the expectations of key stakeholders through their participation in Q-gate certifications.
No related posts.
