Product Backlogs, Projects, Sprints, and Releases: Taking Agile to the Enterprise Level
As the product manager of an Agile ALM tool, I am trying to fine-tune the product to handle agile at the enterprise Level. So, I have a number of questions that I hope the agile project management community has answers for. I am not even sure if these questions are answered in the SaFe framework. My apology if you see this posted in multiple groups as I am seeking some consensuses. Here are the question, please feel free to provide your insight. I have a feel that the answers to all questions are YES, but I would like to get the consensuses of the agile community.
1. If an agile project has a number of Sprints, can a Sprint deliver features that will be included in different releases or all features delivered by a Sprint must be included in one release?
2. Can a release include features delivered by different sprints in different projects, or a Reease can include only features that were delivered by sprints within the same project?
3. If the answer to question 2 is yes, can those projects delivering features to be included in the release be either agile or non-agile projects. The assumption is that for a large enterprise system, some features might be implemented in agile projects and some other features might be implemented in non-agile projects.
4. Although the concept of product backlog has been known only for agile projects, I am assuming for a large enterprise system, a product owner and/or a released manager or a product manager can select features from the backlog to be implemented in agile projects or none agile project, is this a valid assumption?
5. Assuming there a release will have features from different products (systems and sub-systems), then features assigned to sprints, projects, and releases can come from different product backlogs, right?
Thanks for your insight.
Agile Coach |Agile Mindset | Generative AI| ML| CI CD Pipeline |Digital Transformation | Scrum Master| Test Manager |
7 年Hi Madgy ,A Release can be planned to have multiple sprints. If you would like to have two or more releases in sprints then planning need to be done for sprint(s) to have overlap over two releases. But this require proper controlling as well
International Institute for Software Testing
7 年Thank you John
Problem Solver
7 年Do not assume that every story that a feature decomposes into has to all be implemented in the same sprint or even delivered in the same release. Some "bell-and-whistle" stories of a feature might never get released depending on feedback and other competing priorities.
Program Manager Automotive Connected Car, Telematics and Infotainment
7 年Agile plan can include Requirements,Design,code and release approach.
International Institute for Software Testing
7 年Thank you, Rahul. I realize that those question are not answered by the Scrum process and even by any other framework I am aware of. That is why I had to post them. I like your idea of the dependency matrix. However, I think it should show dependencies between features not between projects. It would help the product own select dependent features to be completed either in the same project or in simultaneous projects.