Agile Software Requirements Model

In Agile Software Requirements , we introduced an extensive, agile requirements artifact meta-model—a model that defines the requirements artifacts used by agile teams, as well as the relationships among these artifacts. As an aid to understanding, we introduced it incrementally there, in the context of the discussions of each section.

This model serves as an important part of the semantic backplane for SAFe as a system. But as the Scaled Agile Framework evolves, the models evolve along with it, and this model is no exception. Figure 1 provides an overview of the current Agile Software Requirements Model.

Figure 1. Overview of the Agile Software Requirements Model. This view highlights the backlog items that deliver value across the organization, as well as the Nonfunctional Requirements that constrain them.

However, if you want to understand how test and test automation is applied in SAFe, you need a broader view. Figure 2 illustrates the fully elaborated model.

Figure 2. Full, detailed view of Agile Software Requirements Model in SAFe

This full view also highlights the application of use cases for optionally elaborating system behavior, and also illustrates how many teams use Tasking  as a work breakdown structure to manage story implementation.

Note: If the full model appears complex, that’s because contemporary software development at scale is complex, even with Agile methods. If you don’t need it all, don’t use it all. But if your teams and programs are building world-class enterprise software with the highest possible quality, you likely do.

© 2010-2013 Leffingwell, LLC.