Chapter 5. Agile Requirements for the Portfolio
At enterprise scale, things get a little more complicated.
Introduction to the Portfolio Level
For many software enterprises, including those of modest scope of 100 or so practitioners and those that develop and manage only one or two products, the team model (with its user stories, tasks, and acceptance tests) plus the program model (adding features and nonfunctional requirements) may be all that the teams need to manage system requirements in an agile manner. In this context, driving releases with a feature-based vision and driving iterations with stories created by the teams may be all that is required.
However, there is another class of enterprises—enterprises employing hundreds to thousands ...