An Introduction to Extreme Programming
Subject:   Extreme
Date:   2001-06-28 11:21:11
From:   mvr707
Response to: Extreme

There is something called "Spiral Delta Model"
This is waterfall folded in the middle and spiralled (Iterated).

RS: Requirements Spec
FS: Functional Spec
D: Design
C: Coding
UT(P): Unit Test (Plan)
IT(P): Integration Test (Plan)
ST(P): System Test (Plan)
AT (P): Acceptance Test (Plan)


Convert that to a Delta shape with iterations


This is a tight Delta Spiral. And after a few
cycles, we hopefully hit the bulls eye!:)

As we know, different models are appropriate for
different stuations. So what are the salient differences of Extreme Prog and when is is appropriate?

The article makes good reading but leave hugh and dry

Main Topics Oldest First

Showing messages 1 through 1 of 1.

  • Extreme
    2001-07-14 18:08:33  chromatic | O'Reilly AuthorO'Reilly Blogger [View]

    The biggest visible differences are that iterations are very short in XP, and that programmers can often go through most of the different stages multiple times in a week. (There may be one relatively large story and task planning session and one acceptance test session per iteration, but most of the rest of the stages are done at least once per day.)

    The best way to look at XP is as something that keeps the cost of change very low. There's not a lot explicitly invested in the future. This fits in jobs where the specs can change quickly, or where a job can be delivered in stages, one every six weeks or so.

    It's probably not a good fit for defense contractors, and large shrink-wrap software houses might have a hard time adopting it. For situations that require a lot of flexibility with short notice, it can be very useful.