The Four Extreme Programming Variables at Work
Posted by Chris Hardie on August 14th, 2008Sometimes I have to remind myself that just because we want to try to be all things to our clients doesn’t mean that we can be. Of course, for any given project, the conversation about what’s possible, and on what timeline, and at what cost is never a simple one. The bigger the project, the more complex that conversation becomes. It can be easy to over-promise and under-deliver if you’re not extremely careful.
Several years ago, we began using parts of the “Extreme Programming (XP)” software engineering paradigm in our development process, with the goal of improving our time estimates, better understanding what we were able to deliver to our clients and when. I’ve not found any part of XP to be more useful than the way it describes the interactions between these four variables:
Read the rest of this entry »
The opinions expressed by individuals posting in the Summersault Blog are not necessarily those of Summersault, LLC. While we try to insure the quality and accuracy of the information presented here, we make no guarantees about its suitability for any particular purpose.

