Enabling ExplorationĮxploration enablers provide work items teams can use to discover requirements and design details. The following examples illustrate how Agile teams and architects create and manage each of the four enabler types. Agile Teams also use enablers enabler stories emerge locally from their needs and are carried in the Team Backlog. Architects steer enablers through the appropriate Kanban system and backlog, guiding implementation from concept to delivery. They might be Enterprise Architects supporting the portfolio, System Architects supporting ARTs, or Solution Architects supporting Solution Trains. ![]() Although they may not require the user voice format, their acceptance criteria clarify the requirements and support testing.Īrchitects often define and guide enabler epics, features, and capabilities. Enabler Stories – Must fit within Iterations like any story.They must be sized to fit within a single PI. Enabler Features and Capabilities – These are defined by ARTs and Solution Trains and include a short phrase, benefit hypothesis, and acceptance criteria.Enabler epics can span multiple Agile Release Trains (ARTs) and PIs and are managed via the Portfolio Backlog and associated Kanban system. Enabler Epics – These are written using the ‘epic hypothesis statement’ format, in the same way as business epics.Compliance – facilitate managing specific compliance activities, including Verification and Validation (V&V), audits and approvals, and policy automationĮnablers exist throughout SAFe and are written and prioritized according to the same rules as their corresponding epics, features, capabilities, and stories.Infrastructure – support the creation and optimization of the development and runtime environments that host the systems used to build, validate, deploy, and operate solutions.Architectural – used to build Architectural Runway, which allows smoother and faster development through the Continuous Delivery Pipeline (CDP).Exploration – support research, prototyping, and other activities needed to develop an understanding of customer needs, including the exploration of prospective Solutions and evaluation of alternatives.These activities generally fall into one of four categories: Types of EnablersĮnablers can be used to define any activity that improves the value stream in support of foreseeable business needs. ![]() They are treated like all other backlog items-subject to visibility, prioritization, incremental delivery, measurement, and feedback. ![]() Since enablers result in the production of tangible outputs, they must be visible. Enablers are used to explore ideas, improve architecture, strengthen infrastructure, and manage compliance. DetailsĮnablers bring visibility to all the work necessary to support the efficient development and delivery of future business requirements. While their type is unique, they are managed similarly to customer-facing backlog items. They are used primarily for exploration, architecture implementation, refactoring, building infrastructure, and addressing compliance. Widely attributed to Seneca, Roman philosopher and playwright EnablersĮnablers are backlog items that extend the architectural runway of the solution under development or improve the performance of the development value stream.Įnablers are captured in backlogs as a type of Epic, Capability, Feature, or Story. Luck is what happens when preparation meets opportunity.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |