Agile Development 2.0 provides the flexibility to maintain a unified backlog that can be
used for both release-based or project-based types of delivery. You can maintain all your
backlog in one place and associate the stories to a product,project, or both. You can also
select stories from the backlog and execute them as a project, as a standalone project
development.
The following example shows how Agile Development 2.0 supports a unified backlog for
both project-based and release-based type of deliveries.Figure 1. Agile development work flow use cases
We use cookies on this site to improve your browsing experience, analyze individualized usage and website traffic, tailor content to your preferences, and make your interactions with our website more meaningful. To learn more about the cookies we use and how you can change your preferences, please read our Cookie Policy and visit our Cookie Preference Manager. By clicking “Accept and Proceed,” closing this banner or continuing to browse this site, you consent to the use of cookies.