![]() ![]() Together, they offer a rich context to better understand features and their potential benefits.įeatures are defined using a features and benefits format: Design thinking tools, including personas, empathy maps, and customer journey maps, provide empathy towards and a deeper understanding of customers and users. ![]() Discovering and Describing Featuresĭesign Thinking takes a Customer-Centric approach to creating 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 system’s design across the different backlogs. Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. Product Management and System Architect define the features and enablers, respectively. This process provides reasoned economic analysis, technical impact, and strategy for incremental implementation. The ART and Solution Train Kanban systems support the flow of features and capabilities, where they progress through the funnel, analyzing, backlog, implementing, validating, deploying, and releasing states. Features can originate from either the Agile Release Train (ART)’s local context or from splitting Epics or capabilities. They are maintained in the ART Backlog and sized to fit in a PI so that each delivers new value. Each reflects a service provided by the system that fulfills some important stakeholder needs. Features and Capabilities 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. Detailsįeatures and capabilities are critical to defining, planning, and implementing Solution value. 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. 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 PI.Ī Capability represents large solution functionality whose implementation often spans multiple ARTs and is sized to be delivered within a 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. Linus Torvalds, creator of Linux Features and CapabilitiesĪ 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. There are capabilities in Linux that aren’t in other operating systems. There are some really good technical features that I’m proud of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |