Together, they provide a rich context to better understand features and their potential benefits.įeatures are defined using a Features and Benefits (FAB) Matrix: Design thinking tools including personas, empathy maps, and customer journey maps provide empathy towards and deeper understanding of customers and users. Discovering and Describing Featuresĭesign Thinking takes a Customer-Centric approach to create desirable and sustainable products. They are split into Stories, and are implemented, integrated, tested, and demonstrated as the functionality becomes available. Features are prioritized using Weighted Shortest Job First (WSJF) and are planned and reviewed at PI boundaries. NFRs serve as constraints or restrictions on the design of the system across the different backlogs. Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. Product Management and System Architect/Engineering own the features and enablers, respectively. This process provides reasoned economic analysis, technical impact, and strategy for incremental implementation. The Program and Solution Kanban systems support the flow of features and capabilities, where they progress through the funnel, analyzing, backlog, implementing, validating, deployment, and release states.

Features can originate from either the local context of the Agile Release Train (ART) or they may result from splitting Epics or capabilities. They are maintained in the Program Backlog and are sized to fit in a Program Increment (PI) so that each delivers new value. Each reflects a service provided by the system that fulfills some important stakeholder needs. Features in the SAFe contextįigure 1 shows that solutions are developed using features. Figure 1 provides a broader context for these work items: Figure 1. They are critical to defining, planning, and implementing Solution value. Detailsįeatures and capabilities are central to the SAFe Requirements Model. However, they are at a higher level of abstraction and support the definition and development of large Solutions. Capabilities behave the same way as features. The MMF helps limit the scope and investment, enhances agility, and provides fast feedback. Capabilities are sized and split into multiple features to facilitate their implementation in a single PI.įeatures also lend themselves to the Lean UX process model, which includes a definition of the Minimum Marketable Feature (MMF), a benefit hypothesis, and acceptance criteria. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI).Ī Capability is a higher-level solution behavior that typically spans multiple ARTs. Linus Torvalds, creator of Linux Features and CapabilitiesĪ Feature is a service that fulfills a stakeholder need. There are capabilities in Linux that aren’t in other operating systems. There are some really good technical features that I’m proud of.

Hstracker features