Organizing Multiple Related Projects Over Time
With multiple related projects over time, one of the hardest things to do is track which requirement is going into which release. Using an agile life cycle will make your life infinitely easier, because the product will be potentially releasable at the end of any iteration. Then it becomes a business decision about what to release when.
If you can’t use an agile life cycle, try release trains to deal with the actual releasing and a backlog of product requirements for managing the continual change of requirements in future releases.
OK, I’ll come clean. A release train is a three-month iteration. And this backlog is what agile life cycles use, except that they tend to have smaller chunks to consider ...
Get Manage It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
