Wednesday, January 25, 2006

XP and no I don't mean the Microsoft product:

Extreme Programming(XP) is a programming strategy which involves the customer and lead to faster development times and shorter release cycles. Getting to market faster is key to success with the online world. Today's hot site is tomorrows boring has been.

XP needs the customer/business owner to available and involved in every aspect of the project. This is great for entrepreneurs who have a technical background or just a desire to see the progress of development before the final product is finalized. This allows the project to stay on course with the intended outcome.

In XP, there are many short term goals and the project is often broken into small tasks the similar to object based programming. The ability to test items before they are complete save time and energy that might be spend working on a project that is slightly off course. These projects are measured by how fast they are completed, velocity.

The key here is to get the entire team to understand the process, many teams use metaphors. Metaphors allow everyone to understand the project in their own terms.

Fixing the broken wheel is easy with XP since the total project is broken down into usable parts.

Good luck!

Mike

1 comment:

ryborg said...

XP sounds good from a business management perspective, but from a programming perspective the jury is out.

A few thoughts as to why I wont completely buy into XP.

First, just as with any friendship, there are those that work really well, and those that dont. Likewise for an XP tag-team. I don't want to be paired up with arrogant programmer constantly lurking over my shoulder.

Also, I feel that I am more creative when I am left in solitude, without distraction, and really let my mind sink into the code.

XP of course does have it's benefits. Two minds working on something generally means less time trying to work out solutions for complex problems. And, if the two XProgrammers are the type that complete each others sentences... then you truly have a dynamic duo.

I would suggest a hybrid approach however. One that utilizes frequent code reviews, and alternating XP sessions.