This link has been bookmarked by 60 people . It was first bookmarked on 02 Mar 2006, by someone privately.
-
29 Dec 10
-
19 Mar 10
-
17 Apr 09
-
09 Mar 09
-
21 Jan 09
-
19 Dec 08
-
06 Dec 08
-
16 Nov 08
-
13 Aug 08
-
12 Jul 08
-
29 Apr 08
-
01 Feb 08
RussGreat explanation of Extreme Programming and all its elements (like pair programming).
xprogramming extreme programming pair unit tests explanation Code
-
02 Jan 08
-
06 Nov 07
-
30 Oct 07
-
08 Oct 07
-
02 Sep 07
-
01 Aug 07
-
21 Jun 07
-
12 Jun 07
-
14 Feb 07
-
11 Feb 07
-
Second, XP teams release to their end users frequently as well. XP Web projects release as often as daily, in house projects monthly or more frequently. Even shrink-wrapped products are shipped as often as quarterly.
-
XP planning addresses two key questions in software development: predicting what will be accomplished by the due date, and determining what to do next. The emphasis is on steering the project -- which is quite straightforward -- rather than on exact prediction of what will be needed and how long it will take -- which is quite difficult. There are two key planning steps in XP, addressing these two questions:
Release Planning is a practice where the Customer presents the desired features to the programmers, and the programmers estimate their difficulty. With the cost estimates in hand, and with knowledge of the importance of the features, the Customer lays out a plan for the project. Initial release plans are necessarily imprecise: neither the priorities nor the estimates are truly solid, and until the team begins to work, we won't know just how fast they will go. Even the first release plan is accurate enough for decision making, however, and XP teams revise the release plan regularly.
Iteration Planning is the practice whereby the team is given direction every couple of weeks. XP teams build software in two-week "iterations", delivering running useful software at the end of each iteration. During Iteration Planning, the Customer presents the features desired for the next two weeks. The programmers break them down into tasks, and estimate their cost (at a finer level of detail than in Release Planning). Based on the amount of work accomplished in the previous iteration, the team signs up for what will be undertaken in the current iteration.
These planning steps are very simple, yet they provide very good information and excellent steering control in the hands of the Customer. Every couple of weeks, the amount of progress is entirely visible. There is no "ninety percent done" in XP: a feature story was completed, or it was not. This focus on visibility results in a nice little paradox: on the one hand, with so much visibility, the Customer is in a position to cancel the project if progress is not sufficient. On the other hand, progress is so visible, and the ability to decide what will be done next is so complete, that XP projects tend to deliver more of what is needed, with less pressure and stress.
-
-
08 Feb 07
-
10 Jan 07
-
28 Dec 06
-
31 Oct 06
Art istExtreme Programming is a discipline of software development based on values of simplicity, communication, feedback, and courage. Every contributor to the project is an integral part of the "Whole Team".
-
12 Oct 06
Michael NitschkeExtreme programming practices, discussion, and support, from Ron Jeffries.
java programming xp agile development extreme design education howto management principles process research tools work xtremeprogramming Reference
-
24 Aug 06
-
19 Aug 06
-
09 Aug 06
-
09 May 06
-
15 Mar 06
-
24 Feb 06
-
15 Feb 06
-
01 Dec 05
auxonne auxonneExtreme Programming is a discipline of software development based on values of simplicity, communication, feedback, and courage
-
05 Aug 05
-
20 May 05
-
13 Feb 05
Miska LahtiExtreme Programming is a discipline of software development based on values of simplicity, communication, feedback, and courage.
-
12 Feb 05
-
07 Dec 04
-
29 Apr 04
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.