Features and Capabilities

    There’s innovation in Linux. There are some really good technical features that I’m proud of. There are capabilities in Linux that aren’t in other operating systems.

    - Linus Torvalds, creator of Linux

    Definition: A Feature represents solution functionality that delivers business value, fulfills a stakeholder need, and is sized to be delivered by an Agile Release Train within a PI.

    Definition: A Capability represents large solution functionality whose implementation often spans multiple ARTs and is sized to be delivered within a PI.

    Summary

    Features and capabilities are critical to defining, planning, and implementing value. Each reflects the functionality the product or solution provides, fulfilling important stakeholder needs. Features are maintained in the ART Backlog and sized to fit in a PI so that each delivers new value. Features may originate from either the local context of the Agile Release Train (ART) or from splitting epics or capabilities. Capabilities behave the same way as features. However, they have a higher level of abstraction and support the definition and development of large solutions.

    Figure 1 provides a broader context for features and capabilities:

    diagram showing the broader context of features and capabilities in SAFe.
    Figure 1. Features and Capabilities in SAFe

    What is a feature?

    A feature describes a product or solution functionality that offers business value, meets a stakeholder requirement, and can be completed by an Agile Release Train within a PI, (generally under 2 months of total effort).

    Product Management and the System Architect define features and enablers, respectively. Nonfunctional requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. NFRs constrain or restrict the system’s design across the different backlogs. Using Weighted Shortest Job First (WSJF), features are reviewed and prioritized at PI boundaries. The teams then split features into stories to be implemented, integrated, tested, and demonstrated as the functionality becomes available.

    In this article

    What is a feature?
    What is a capability?
    How are features identified and defined?
    How are capabilities split into multiple features for implementation?

    Key Takeaways

    • Features and capabilities are vital to defining, planning, and implementing value.
    • Agile Teams employ design thinking techniques to create desirable features.
    • Product Management use WSJF to prioritize features; System Architects use it to prioritize enabler features.
    • Capabilities have the same characteristics as features but span multiple ARTs.

    Last Update: 24 February 2025