Browse > Home / Managing Product Development, Project Management News / Using Multiple Life Cycles in Combination on a Project, Part 1

Using Multiple Life Cycles in Combination on a Project, Part 1

November 25, 2007 @ Managing Product Development from johanna

Vote This Post DownVote This Post Up (No Ratings Yet)
Loading ... Loading ...


I’m not a purist. I use whatever tools make sense for the context I’m in, and when it comes to organizing projects, I use whatever life cycles–in whatever combination–make sense to me. In response to a mailing list query, here are ways I’ve used life cycles for a few projects.

Let’s assume you’re collaborating with another organization. You would like to define an architecture sooner rather than later. You’re nervous about an architecture that emerges from implementing some features–you want a little more planning than that.

So you decide to prototype the architecture for a little while in the project (an iterative life cycle), and then move into implementing by feature (incremental life cycle). I’ve used this combination life cycle with and without timeboxes.

Combination of iterative and incremental life cycle

Is this a perfect life cycle? Nope. But it beats the uncertainty of a waterfall.


This article is syndicated from Managing Product Development . The original article is available here. Read more in Managing Product Development, Project Management News .

No tag for this post.
Reminder : PMToolbox has ZERO tolerance to copyright violation and agrees to follow strictly PMI's Professional Responsibility. That's why each post on this site includes a link to the original version at its source site.

Related Posts

Comments

Got something to say?