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

Thoughts on your software engineering process

By Jeff Levinson • on October 20, 2007

In the time I have spent lecturing, teaching and working with Team System I have heard the following statement more times than I care to count, “Yeah, we know we have a problem, but we can’t get anyone to do anything about it.” This is a problem that isn’t so readily solved. A lot of people would just say, “Well, why don’t YOU do something about it? Start writing unit tests. Start doing nightly builds. Start using tools x, y and z.” The problem is that this doesn’t really solve the problem 90% of the time.

Why not? Well, most developers (especially those using TFS) work for organizations. The only way some things get done in large organizations is for executives to champion a cause and actively implement a plan for improvement. But this takes some type of ROI calculation – most executives will not plow money into an initiative with no benefit. Okay, seems reasonable you say but how do you actually convince them? This is where the catch-22 comes in. In order to prove the benefit of changing a methodology or using a new tool or even changing a single process you need to have gathered some kind of metrics. How many of you do that today?

The reality is that most organizations today do not effectively gather or evaluate metrics. I’ll give you my favorite example – do you track bugs and change requests? Mostly people track them in some way, but don’t consolidate them and don’t try to understand the root cause because that takes time. For example, a user comes to you and says I found a bug with feature X, it doesn’t do this (whatever this is) and it should. Is it a bug? Is it an enhancement? Maybe it’s a requirement that was missed? Try telling an executive that you need to institute a method for gathering requirements consistently or that the analysts need training without knowing anything about the changes that are being requested of you…

This is a personal crusade of mine so I’ll follow up with other thoughts and some easy (read inexpensive) methods for starting to gather this information.

Leave a Comment

You must be logged in to post a comment.