• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Mission-Critical Development With XP & Agile Processes

 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Interesting Article in Dr. Dobb's Journal: http://www.ddj.com/documents/s=8988/ddj0401a/
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for posting that. I for one would've probably missed that since I practically never read DDJ.
 
Ranch Hand
Posts: 3404
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That's cool. It's nice to know it has been done with XP.
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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?
 
Author
Posts: 350
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I read the article. It was good.
 
reply
    Bookmark Topic Watch Topic
  • New Topic