Managing ART and Solution Train Backlogs

A Kanban system used to organize and manage features and enablers for a solution.

A backlog that defines the features, capabilities, and non-functional requirements (NFRs) for the entire solution.

Features or capabilities that are derived from the Portfolio Epics and are prioritized for development.

Features or capabilities defined specifically for the Solution Train's unique needs.

Features or capabilities defined specifically for the Agile Release Train's needs.

Constraints or limitations that impact the design and performance of the solution.

The process of refining the ART and Solution Train backlogs to ensure features and capabilities are ready for implementation.

Product and Solution Management teams work together to prioritize the ART and Solution Train backlogs.

The phase in Agile where Subject Matter Experts (SMEs) and stakeholders perform detailed analysis of epics. This includes refining size estimates, exploring solution alternatives, identifying Minimum Marketable Features (MMF) or Minimum Viable Products (MVPs), and forecasting costs.

A method of prioritizing work items based on their value, effort, and risk. It helps teams focus on the most important and impactful work by considering the business value, the time it takes to complete, and the uncertainty associated with it.

A Minimum Marketable Feature (MMF) is the smallest, independent piece of functionality that can be delivered to customers and provide value. An MMF can be used to test customer interest and gather feedback.

A Minimum Viable Product (MVP) is the simplest version of a product that can be released to gather user feedback and validate the product/service idea. It is often used to quickly test hypotheses and learn about user needs.

The process of allocating capacity for different types of work within a team or organization. This includes balancing the delivery of business features with necessary investments in enablers like infrastructure, technology, and architectural improvements.

Tasks that support the overall architecture and infrastructure of a system. They involve activities like updating dependencies, improving technical infrastructure, or resolving technical debt. These tasks often do not directly deliver business features but are essential for the long-term health of a system.

The period of time during which a team plans and executes work. Usually, it's a fixed length of time, like 8 weeks.

The process of regularly reviewing and adjusting capacity allocation and backlog priorities to ensure alignment with changing business needs and priorities.

A prioritized list of Features and Capabilities that are ready for implementation.

A step in the Kanban flow where features are implemented throughout the PI by the Agile Teams.

A state where features are integrated and tested in a staging environment, ensuring they work well with the rest of the system.

Features that are approved and ready for immediate deployment.

A state where features are moved into production, either through automated Continuous Delivery or manual deployment.

A buffer in the Deploying to Production state where features are awaiting release.

Features are released to customers to evaluate their benefit hypothesis.

A state where features have been released and evaluated, and their feedback is assessed.

Initiatives that are too large to be completed in a single PI, typically tracked in a separate Kanban system.

A Kanban system used to analyze and approve ART or Solution Train epics, splitting them into features or capabilities for implementation.

A state where big ideas or initiatives are initially captured, typically as Features or Capabilities.

Initial assessment of epics by Subject Matter Experts (SMEs) and stakeholders, prioritized using WSJF.

A state where epics are analyzed and prioritized using WSJF and other criteria to determine if they should proceed to further exploration.