Home > General Development > Selecting the Right Iteration Length for Your Development Process Selecting the Right Iteration Length for Your Development Process Eugenia Loli 2006-05-08 General Development 6 Comments A key consideration in adopting an iterative process is selecting how long your iterations will be. Mike Cohn discusses the issues to consider when determining whether your team’s iterations should last two weeks, three weeks, or longer. About The Author Eugenia Loli Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker. Follow me on Twitter @EugeniaLoli 6 Comments 2006-05-08 8:37 am Tuishimi …or has this been around forever? Yeah, they slap pretty new terms on it, but haven’t we all been developing this way for many years? I’ve been a developer for 20 years and none of this is new, except that every year or so old ideas get recycled with new buzzwords and someone makes a load of do-re-mi off it. Some if it is just plain common sense… you need to release changes to test and give them enough time to at least give it a solid once over, then tackle remaining issues or any new issues that come up with the design or bugs in general. Whatever, I guess. The article isn’t horrible or anything… 2006-05-08 11:44 am Reiky you are right but how many out there actually really work that way? 2006-05-08 3:18 pm Tuishimi True… our projects go like… VP: “We want our website to be able to atomize people through their screens” ME: “But m’am, the technology doesn’t even exist yet, the closest we can come is flash…” VP: “…and we need it in 3 months and it had better work! Oh, and we need everyone else on other impossible projects so you have to do it yourself.” 2006-05-09 4:57 pm rcsteiner Depends on the shop. At my old position at an airline we had the time to do things properly. If we ran into any problems from managerment, all we had to do is say that cutting corners could result in a safety issue. 🙂 (I worked in flight ops — sometimes it was actually true!) In my current position, it isn’t quite so clear, but so far sanity (and common-sense processes) have been the winner. That might be tested soon; film at 11. 2006-05-08 12:22 pm Soulbender Apparently not too many since “Extreme Programming” also got headlines. Common sense isnt all that common in this industry. Listen to the users? Work with them? Test your code a lot? Holy crap, that’s some crazy, new stuff, groundbreaking for sure. No wait, it’s exactly what we learned when I took System Analysis 10 years ago. Oh the Extremeness…. 2006-05-08 3:20 pm Tuishimi Yep. I still have my book from college. It was one of my favorite (most useful anyway) classes. That and my fiction writing class that met my English requirements.