File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Agile and Other Processes and the fly likes Mission-Critical Development With XP & Agile Processes Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Mission-Critical Development With XP & Agile Processes" Watch "Mission-Critical Development With XP & Agile Processes" New topic
Author

Mission-Critical Development With XP & Agile Processes

Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Interesting Article in Dr. Dobb's Journal: http://www.ddj.com/documents/s=8988/ddj0401a/


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Thanks for posting that. I for one would've probably missed that since I practically never read DDJ.


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
HS Thomas
Ranch Hand

Joined: May 15, 2002
Posts: 3404
That's cool. It's nice to know it has been done with XP.
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
But what about that sounded like XP except the author mentioning XP? Some good iterative practices came out in the code phase, but four weeks requirements phase, four weeks design phase, then code phase? CODE PHASE?
[ December 17, 2003: Message edited by: Stan James ]

A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Originally posted by Stan James:
CODE PHASE?
They did practice refactoring, which implies that they did not freeze the design when entering the "code phase". Also, the "code phase" seems to have been a set of iterations starting with the customer giving objectives for that iteration. Of course, nobody can really tell how mercilessly they refactored...
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
I emphasized the wrong words. I was more concerned about the nine weeks with no code at the front. The description sounds purely phasist with the code phase (very nicely) broken into iterations.
I may have gotten this from a Kent Beck paper ...

Requirements are often "frozen" in phasist methods, but usually thaw out in the heat of development (cringe) ... or maybe they break into shards of ice first.
I worked (exactly) one project that was the furthest possible opposite of iterative. The manager refused to show the customer any work in process, wanted to wait until everything was absolutely finished, perfected and polished. Those requirements stayed in the deep freeze for sure. Of course the customer hated it. Made me a believer!
[ December 18, 2003: Message edited by: Stan James ]
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Originally posted by Stan James:
I emphasized the wrong words. I was more concerned about the nine weeks with no code at the front. The description sounds purely phasist with the code phase (very nicely) broken into iterations.

XP *does* have an Exploration Phase, where initial requirements are gathered, a system methaphor is thought up, architectural spikes are implemented and a first rough release plan is formulated.
It sounds like they used a little bit too much design without feedback from code and spent a little bit long on the requirements. The author even seems to see it in a similar way. Nevertheless it doesn't sound *too* bad, in my humble opinion...
Requirements are often "frozen" in phasist methods, but usually thaw out in the heat of development (cringe) ... or maybe they break into shards of ice first.

Yeah - but from the text it doesn't sound like it happened to that team. Seems they accepted and implemented new feature requests every iteration.
I worked (exactly) one project that was the furthest possible opposite of iterative. The manager refused to show the customer any work in process, wanted to wait until everything was absolutely finished, perfected and polished. Those requirements stayed in the deep freeze for sure. Of course the customer hated it. Made me a believer!

I can believe that...
But, again, it doesn't sound much like the project from the article. Seems they *did* do frequent, early releases to the users and accepted feedback.
Am I reading something different from the article than you?
Rick Hightower
Author
Ranch Hand

Joined: Feb 20, 2002
Posts: 350
I read the article. It was good.


Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Mission-Critical Development With XP & Agile Processes