Can anyone explain to me what is "Quality gates" and most important gives some examples of the same. I have been asked to implement certain quality gates in a new project which already has functional requirements,architectuaral design, development estimates etc.. and development is in the initial stages. Please let me know which gate I need to implement at every stage. We are using the Agile process.
A Quality Gate is usually a milestone where certain quality levels must be passed before the code moves on to the next phase.
In the past, I have used Quality Gates to decide when we have achieved Beta level, or General Availability level, etc.
For example, some of the criteria that might be needed to achieve Beta level could include:
- all the features are present and complete
- all features have been tested
- all Regression Tests pass
- no Severity 1 bugs remain
In an agile process the 'gates' are tpyically more fluid. The team decides the following:
1. The stories (features) of the solution
2. Deciding the sprints (allocating 'features' to logical groupings within the agreed timebox (2-4 weeks)
3. The sprint activities within each feature (breaking each story into elements of Structure, Function, Data, Platform and Operations or some other 'elements' like quality attributes or Kano Modelling to gain a priority listing for each feature.
4. The documentation levels required
5. The definition of 'Done'
Each progression can be a 'gate' and may be in sequential, parallel or overlapping depending on the burndown chart and activities defined.
In my experience with agile...
Hope this is useful to you...
[ QUOTE ]
what if the quality gates are not passed?? what if it fails?
[/ QUOTE ]
The whole idea of traditional gates is that the product or project does not advance through the gate until the criteria is met. This means that you either met the grade or take the exam once again until you do.
In practice and depending if you are working on certified or un-certified environments, sometimes you may be somewhat flexible and decide to overwrite a specific criteria as a (risk-based) decision of all relevant stakeholders.
Coincidentally enough, in the December issue of Software Test & Performance magazine (which arrived today), there is an article "Quality Gates for the Five Phases of Automated Software Testing" - written by Elfriede Dustin.