Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Mission-Critical Development With XP & Agile Processes

 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Interesting Article in Dr. Dobb's Journal: http://www.ddj.com/documents/s=8988/ddj0401a/
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for posting that. I for one would've probably missed that since I practically never read DDJ.
 
HS Thomas
Ranch Hand
Posts: 3404
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's cool. It's nice to know it has been done with XP.
 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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 ]
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 350
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I read the article. It was good.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic