Epics are used to get a bigger picture of user stories, but we need another level of abstraction. We need to bring together the various Epics that describe how our solution will evolve to its final endpoint, and how different functional teams and specialists will interact.
Uncertainty in the Product Backlog is a big risk for the schedule of a Scrum project. The problem is that the full scope of the release can be quite hard to estimate because the requirements are not well-know early on. Confounding this problem is that frequently the release date is a hard deadline. This means that an Agile team must perform an unknown about of work in a fixed amount of time. The “Cone of Uncertainty” describes the reduction of the uncertainty about scope after each iteration. At the uncertainty is eliminated and the exact amount of scope is known.
This article describes a Lean and Scalable Requirements Information Model that extends the basic team‐based agile requirements practices to the needs of the largest, lean‐thinking software enterprise. While fully scalable to all levels of the project, program and portfolio levels, the foundation of the model is a quintessentially lean and agile subset in support of the agile project teams that write and test all the code.
Fast turnaround in agile projects requires the specifications and testing processes to fit into to short iterations, which is a challenge for many teams when they start out with agile development.
This article describes an emerging enterprise pattern for the successful implementation of software agility at the project team, program and portfolio level. It describes the new software development and delivery process mechanics, the new teams and organizational units, and some of the roles key individuals play in the new agile paradigm. In addition, the Big Picture highlights the requirements practices of the enterprise agile model, because they uniquely carry the value stream to the customer.
This article explores some of the principles of agile interactions of Scrum teams. More specifically, it focuses on those interactions necessary to discovering and elaborating requirements within the context of the Scrum framework.
The article “Agile, Multidisciplinary Teamwork” by Gautam Ghosh presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.