Key terms from the Scaled Agile Framework as used in Productivity Workbench. Enterprise
ART (Agile Release Train)A long-lived team of 50—125 people that plans, commits, and executes together. The ART is the primary delivery vehicle in SAFe. It consists of 5—12 Agile teams plus shared services (System Architect, System Team, Business Owners).Business OwnersKey stakeholders who have primary business and financial accountability for the solutions delivered by a given ART. They participate in PI Planning and Inspect & Adapt.Enabler Feature / StoryA technical or architectural work item that extends the Architectural Runway, enabling future business features. Enablers are first-class citizens in SAFe — they are planned and visible on the Programme Board alongside business features.IP Iteration (Innovation & Planning)The last iteration of a PI. Reserved for PI Planning preparation, innovation spikes, hackathons, and handling undone work. It is not used to take on new feature commitments.Inspect & Adapt (I&A)A quarterly ART-level retrospective event held at PI close. Teams demonstrate the integrated increment, review PI performance metrics (PPM score, velocity), and identify improvement items for the next PI.Lean Budget GuardrailsSAFe's replacement for project-level annual budgeting. Budgets are allocated to Value Streams rather than projects, giving teams autonomy while maintaining financial governance. Guardrails define spending policies for the portfolio.Milestones (Fixed vs. Learning)Fixed-date milestones are external commitments (release dates, regulatory deadlines). Learning milestones are hypothesis-based checkpoints used to validate whether a direction should continue. Productivity Workbench supports both types in the Milestones page.NFR (Non-Functional Requirement)A constraint on the solution rather than a feature — performance, security, scalability, accessibility, compliance. NFRs are managed on the NFRs page and linked to features and stories that must comply with them.PI (Programme Increment)A timebox of typically 8—12 weeks (4—6 sprints + 1 IP Iteration) in which an ART delivers a significant increment of the solution. Each PI has PI Objectives, a Programme Board, and concludes with an Inspect & Adapt event.PI ObjectivesA summary of each team's planned business outcomes for the PI. Teams commit to 3—5 objectives, each with a business value score and a committed/stretch designation. At PI close, actual business value achieved is compared to plan — this ratio is the PPM score.PI PlanningThe cadence-based, two-day event that aligns all teams in the ART to a shared mission and vision for the PI. All team members, product managers, system architects, and business owners attend in person (or virtually). The primary output is a set of committed PI Objectives and a loaded Programme Board.Portfolio KanbanA Kanban system for managing the flow of Epics from ideation through to delivery. Stages typically include: Funnel → Reviewing → Analysing → Portfolio Backlog → Implementing → Done. Each stage has a Work-in-Progress (WIP) limit.PPM (Programme Predictability Measure)The ratio of actual business value achieved vs. planned business value across PI Objectives. A healthy ART targets 80—100% PPM. Calculated automatically in Productivity Workbench at PI close.Programme BoardA visual display of cross-team Feature delivery across PI iterations, showing dependencies between teams as arrows. Used during PI Planning to identify and de-conflict dependencies before the PI starts.ROAMA framework for classifying risks identified during PI Planning: Resolved (risk is gone), Owned (a specific person takes responsibility), Accepted (risk is known and tolerated), Mitigated (action taken to reduce likelihood or impact).Set-Based DesignA lean engineering practice of exploring multiple design options in parallel before converging on one solution. Reduces the risk of committing too early to an approach that turns out to be wrong.Solution TrainThe next level above ART in large SAFe implementations. A Solution Train coordinates multiple ARTs delivering a single large solution. Productivity Workbench supports Solution Train artefacts (Solution Kanban, Solution Demo, etc.) for organisations operating at this scale.System DemoAn end-of-iteration event where all teams in the ART demonstrate the integrated, tested increment of the solution. Unlike team demos, the System Demo shows the fully integrated product — not individual team outputs.Team Self-SelectionA collaborative process for forming Agile teams before PI Planning. Team members self-organise into cross-functional teams, ensuring teams are balanced, motivated, and co-designed by the people doing the work.Value StreamThe sequence of activities an organisation undertakes to deliver a continuous flow of value to a customer. In SAFe, Lean Budgets are allocated to Value Streams, not projects. 