CIOZone.com - Professional Network for CIOs and IT Professionals

Over my professional career, I've had the benefit of working through a number of different frameworks and methodologies to deliver software. For each one I've had to deal with enthusiastic idealists pushing the current approach as the epitome of successful delivery while another camp of equally enthusiastic skeptics point out the issues they see or are experiencing with the process.

The trouble is that both sides are entirely right in the pieces of the puzzle that they see.

How can this be? From early in our SDLC education, different proponents have told us that there is really only one way to deliver software because to be successful there needs to be requirements, design, development, testing and deployment. So how is it that we can be fighting over the same building blocks in the methodology wars?

The trouble is that in selecting and implementing a methodology, most groups will choose to try to create an environment in which they will be most comfortable. Naturally enough there are a lot of factors going into a decision to change the status quo ranging from dissatisfaction with failures or overhead or the political controls of the existing regime, to the political realities of one group or another being able to impose a mandate. However, the choice of methodology is, when approached correctly, a reaction to some existing problem.

Start with the reality: No methodologies or frameworks is a silver bullet.

Methodologies and frameworks exist to address specific problems in the process of delivering a product. In my experience, none address all possible problems and some seem to only address a problem created by another method. Following these approaches is intended to produce consistent results by providing a space in which part of the puzzle can be handled prescriptively.

Each approach will have gaps, but if those gaps happen to exist in the same places your team falls down you can't expect to see improvements. If you've picked a framework that supports the weaker aspects of your team, then overall you will see improvement.

So if what you're doing isn't working for the organization and someone comes to you with the latest-and-greatest method which will solve all your problems, take a step back and ask how it fills the gaps.

Comments (1)

	1. 02-08-2010 17:14
	I did always find it funny when going through the numerous theoretical classes on models of development how different instructors taught each model. One would be gung ho and the next would teach it like a history lesson. I agree when it comes down to it the model that works is the one that works in a specific situation, and as every environment is different one must be developed based on the vision of that specific company.    -sean Registered

This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Only registered users can write comments.
Please login or register.