VSTS, Visual Studio, VS2010,
prix plavix viagra pour les femmes acheter viagra doctissimo viagra combien ca coute paxil médicament cialis generique en france nolvadex sans ordonnance générique zovirax générique flagyl levitra indien plavix belgique cialis à vendre zovirax comprimés posologie acheter viagra 20mg acheter lioresal baclofen prix levitra pharmacie achat cialis sans ordonnance lasix médicament nolvadex 20mg acheter kamagra gel achat priligy cialis inde acheter cialis internet acheter cialis sans ordonnance viagra temoignage viagra generique en pharmacie plavix 150 mg pilule levitra prix levitra acheter cialis en espagne viagra le vrai acheter accutane cipro xl 1000mg achat cialis en france kamagra belgique cialis 10mg prix commander cialis generique prix priligy priligy dapoxetine strattera 80 mg kamagra oral jelly achat viagra pharmacie cialis 5 mg prix prix aciclovir priligy achat prix cialis 5 viagra pharmacie paris acheter baclofen aciclovir prix clomid sans prescription cialis tunisie acheter cipro kamagra livraison rapide acheter levitra pas chere cialis generique forum prix cialis 10 mg cialis generique 10mg viagra generique belgique kamagra paris achat cialis 5mg flagyl générique acheter clomid acheter zithromax médicaments cipralex viagra generique pharmacie procurer du cialis vente de cialis sur internet pilule cialis cialis luxembourg viagra en pharmacie proscar sans ordonnance plavix prescription plavix 75 mg accutane ligne viagra lyon viagra im internet bestellen strafbar clomid 150 mg achat kamagra oral jelly cialis generique pas cher proscar 5mg cipro 1000mg viagra ou acheter cialis 10 mg generique priligy en belgique accutane sans ordonnance cialis 5mg prix generique zithromax veritable viagra acheter strattera viagra chez la femme cialis bon prix cialis lilly prix kamagra apcalis achat cialis clomid en ligne generique cialis efficace acheter viagra canada viagra naturel pour femme commander cialis en france amoxicillin 500 mg kamagra suisse levitra france achat cialis suisse acheter du viagra achat viagra pas cher acheter acyclovir kamagra en france acheter cialis paypal acheter du kamagra cialis prix strattera 40 mg prix zovirax nolvadex prix clomid 100mg azithromycin 250 mg viagra generique suisse acheter cialis generic viagra effet secondaire cialis ne marche pas médicament baclofen acheter amoxicillin prix du viagra paxil 30mg clomid 50mg acheter sildenafil flagyl ordonnance clomid sans ordonnance forum achat cialis prix flagyl 500 clomid deux comprimés clomid 25mg impuissance sexuelle commander du viagra acheter clomid viagra professionnel acheter du levitra plavix 300 mg prix viagra andorre achete viagra cialis generique france cialis commande cialis 20mg pas cher viagra prix de vente prix sildenafil traitement impuissance cialis generique suisse viagra sans prescription cialis achat forum viagra remboursé par la sécu prix cialis 5mg levitra a vendre

Practical Process Improvement (Part 3)

By Jeff Levinson • on October 31, 2008

In the last post in this series I discussed the process involved around the first part of the ideal bug process. In this post I will finish up the rest of the process and metrics for handling bugs.

Fixed, unverified

This state indicates the bug has been fixed according to the developer.

This means that the developer has fixed the code, checked it in and associated it with the appropriate bug work item. They have run the test case provided by the analyst in the Under Investigation state. In addition, the time between the bug being in the Active state and the Fixed, unverified state is the time it took the developer to fix the bug. In other words, we now have an approximation of the developer effort to fix the bug. It doesn’t provide an exact time but it provides an overall throughput time.

Ready for Testing

This state indicates the bug has been assigned to a tester but the testing has not yet started.

There are a number of reasons for this state. The first is that your branching model is such that a tester does not have access immediately after the code has been finished (i.e. you are waiting to promote code to the QA branch). The second is that there is simply other work going on and that the tester just can’t get to it right now. The transition between Fixed, unverified and Ready for Testing should be made by a Test Manager to acknowledge that the bug has been assigned to a tester (or to the testing group in general) and that it is on the right code branch for testing. The transition to this state does not provide any other meaningful information.

In Testing

This state indicates that the bug is actively being tested.

The other important information provided by this state is the amount of time between the bug being ready for testing and when the testing started. This again shows waste.

Fixed, verified

This state indicates that the bug has been fixed according to independent testers.

The time between this state and the In Testing state provides the amount of time spent testing this bug and is considered work time.

Note: For those familiar with Lean theory, this work would be classified as waste. The reason is because work should never pass a station with defects – it means the process for building the code needs to be fixed. However, as I have mentioned before, I believe this is mostly impractical in software development.

Scheduled for Deployment

This state simply indicates that the fix is scheduled to be released.

An important piece of information to capture at this state is the release that the fix is being deployed in. This helps create a Release Notes document to provide the user explaining the changes in the upcoming release.

Closed

The bug is closed after the release that it is included in has been deployed.

The time between the bug report being Proposed and the bug being Closed provides the entire throughput for the bug being fixed. This information is a good metric of whether or not your process is improving (if reducing the amount of time to accept and fix bugs is one of your goals). While removing individual pieces of waste is important, you have to keep your eye on the overall goal.

A note about UAT

You may be wondering about the lack of inclusion of User Acceptance testing steps to track users’ acceptance of the bug. There are two reasons why this isn’t included. The first is, does it provide you any additional information? Sure, it lets you know the users accepted it, but you can do that as part of the QA process. Second, by doing UAT separately it means that you have to have separate UAT environments from QA which many organizations can’t afford. Is the cost worth it? This may be something you need to take into account as you think through your process.

This finished the process and description of each step in the process. The next post in this series will cover Roles & Responsibilities and Reports and how to track improvements in the process.

Related Entries

Recent Entries