This week's book giveaway is in the OCPJP forum.
We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line!
See this thread for details.
The moose likes Agile and Other Processes and the fly likes Project --->  Iterations Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Project --->  Iterations " Watch "Project --->  Iterations " New topic
Author

Project ---> Iterations

kri shan
Ranch Hand

Joined: Apr 08, 2004
Posts: 1381
I segreagated my whole project into many iterations. Can i proceed one by one iteration (like iter2 start when iter1 is over) (or) parallel development of all iterations ? Which way is better ?
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30789
    
157

Kri,
We've done "pure" iterations where one starts after the previous one ends. We've also done overlapping iterations where the coding overlaps, but the completion of each iteration is set appart by a few weeks. If all the iterations start/end the same, it isn't really iterative.

The more "pure" iterative model lets you focus on the features for that iteration. It also lets the users provide feedback on what should be in future iterations. The overlapping iteration model works better if the functionality for the iteration is determined in advance. For example, when the users are following waterfall and the developers are following iterative. It works better if the users are open to at least some change in the iterations.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Scott Ambler
author
Ranch Hand

Joined: Dec 12, 2003
Posts: 608
Exactly. At Agile Requirements Change Management I overview an approach which enables your stakeholders to change the upcoming requirements as much as they see appropriate.

- Scott


<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Project ---> Iterations