Features, Capabilities, Enablers
When working with the Scaled Agile Framework (SAFe), features, capabilities, and enablers are terms that you need to be familiar with. A good grasp of these is critical for an efficient development process. We examine what these terms mean and their relevance.
What Are Features, Capabilities, and Enablers?
Feature — A feature is a service or function that meets the need of a stakeholder. Features may also be described as parts of a product that provide notable value to the user. They add some substance to the vision when sharing this with teams and stakeholders. They are suitably split to enable delivery by a single Agile Release Train (ART) in just one Program Increment (PI).
Capability — A capability is the superset ‘feature set’ of the product, that a feature is part of. Capabilities may be described as abilities or qualities that can be created or used to achieve desired outcomes. They often cut across multiple ARTs and are split into several features for seamless execution in one PI.
Enabler — An enabler is a technical ability of the platform, that supports the expansion of business and crucial for driving business features. It brings attention to the work needed to drive efficient future business requirements and development.
These are not new concepts but the Scaled Agile Framework (SAFe) has created a vocabulary for these concepts to streamline communication, with everyone speaking the same language — on this and other terminology.
Defining and Managing Features
When defining features, a template known as the Features and Benefit (FAB) Matrix is commonly used. This comprises the feature and a benefit hypothesis. The feature, usually a short phrase, provides a name and context while the benefit hypothesis defines a quantifiable benefit to the stakeholder.
Product management, along with other stakeholders such as Product Owners (POs), defines features based on the local context of the Agile release train. Features can also be defined by splitting Epics or capabilities.
While PMs and POs create business features, system architects are responsible for creating enabler features in most cases. These may also originate locally from the ART or epics.
Prioritization is involved when working with features and capabilities. The weighted shortest job first (WSJF) model is used to order the sequence of jobs to derive the maximum benefit. Product management usually prioritizes features while system architects or engineering prioritize enabler features.
Features come with acceptance criteria that are used to assess whether jobs are properly implemented and deliver favorable outcomes. The criteria enable prompt confirmation of the benefit hypothesis and the reduction of implementation risk. Product managers perform the function of accepting features.
Capabilities are similar to features in several regards. For instance, they include short phrases describing them, benefit hypotheses, and acceptance criteria.
Enablers in the Agile Framework
Enablers can be found at all levels of SAFe. They are depicted in multiple backlogs existing in the Framework. They are associated with epics, features, capabilities, and stories and are created and prioritized according to the rules applying to these.
Enabler epics — These are enablers found at the portfolio level. They extend across PIs and Value Streams and are tracked using the Portfolio Kanban system. Enabler epics use the epic hypothesis statement format and include a “Lean Business Case,” according to Scaled Agile.
Enabler features — These are a kind of features that are defined by ARTs. They are sized to fit into a single PI. They include a short phrase along with a benefit hypothesis and acceptance criteria.
Enabler capabilities — These share similar attributes as capabilities that they correspond to. Like enabler features, they include a short phrase, benefit hypothesis, and acceptance criteria. They are also sized for a single PI.
Enabler stories — Existing at the team level, these enablers guide the work of the teams. The stories assist in carrying out iterations, with acceptance criteria informing requirements and aiding testing.
In SAFe, engineering or system/solution architects are typically in charge of creating enablers. They see to their analyses, estimation, and implementation in Kanban systems.
Types of Enablers
There are four main types of enablers in the Scaled Agile Framework. These are:
Exploration enablers — Given the importance of properly knowing the customer, these enablers aid activities, including research and prototyping, geared toward this. They assist in exploring possible solutions and evaluating alternative approaches.
Architectural enablers — These are enablers that help to develop the Architectural Runway, or existing technical infrastructure. They are backlog items that sustain and expand the Runway. They help to support faster and seamless development in an organization. Architectural enablers should ideally be implemented gradually by splitting them into smaller stories fitting into an iteration.
Infrastructure enablers — These exist to support development, testing, and deployment in organizations. They are backlog items that support the building and use of the Agile development infrastructure. Enablers improve the quality of testing and aid faster development and growth.
Compliance enablers — In SAFe, these help for ensuring compliance. Organizations use them to direct activities related to compliance, including documentation, Verification and Validation, and regulatory submissions. Validation can involve POs along with customers and users.
