This regular rhythm is the heartbeat that drives backlog readiness as well. Exploded view of Program Backlog, with story point size estimates Refining the BacklogĪgile Release Trains and Solution Trains run a steady 8-12 week Program Increment (PI) cadence of planning, execution, demo, and Inspect and Adapt (I&A). Backlog items are estimated in story points, as Figure 1 illustrates. The backlogs are a short-term holding area for features and capabilities that have gone through their respective Kanban systems and have been approved for implementation.

Product and Solution Management develop, maintain, and prioritize the program and solution backlogs respectively. The program and solution backlogs are the repositories for all the upcoming work that affects the behavior of the Solution. Since the backlog contains both new business functionality and the enablement work necessary to extend the Architectural Runway, a ‘capacity allocation’ is used to help ensure immediate and long-term value delivery, with velocity and quality. Then they’re prioritized relative to the rest of the backlog to await implementation.Įffectively identifying, refining, prioritizing, and sequencing backlog items using Weighted Shortest Job First (WSJF) is the key to the economic success of the solution. The work travels through the states of ‘funnel’ and ‘analyzing’ and the highest-priority features and capabilities that were sufficiently elaborated and approved, move to the ‘backlog’ state. The backlog items are managed through their respective Program and Solution Kanban systems. The items in these backlogs result from research activities and active collaboration with various stakeholders- Customers, Business Owners, Product Management, Product Owners, System and Solution Architects/Engineering, and more, that are part of the Continuous Exploration process. Product Management has responsibility for the Program Backlog, while Solution Management is responsible for the Solution Backlog. The Solution Backlog is the holding area for upcoming Capabilities and Enablers, each of which can span multiple ARTs and is intended to advance the Solution and build its architectural runway.

It also contains the enabler features necessary to build the Architectural Runway. The Program Backlog is the holding area for upcoming Features, which are intended to address user needs and deliver business benefits for a single Agile Release Train (ART). Edwards Deming Program and Solution Backlogs The emphasis should be on why we do a job.

Queue software