--- title: "Scaled Agile Software with Essential SAFe | Orangescrum" description: "Run Essential SAFe with Agile Release Trains, Program Increments, PI planning, a program board, WSJF prioritisation, ROAM risks, and flow metrics." canonical: https://www.orangescrum.com/scale-agile-project-management --- # Scaled Agile Software with Essential SAFe | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Features](/features) / Scaled Agile Scaled Agile # Scaled Agile for _Many Teams at Once_ Agile works for one team out of the box. Orangescrum supports Essential SAFe so several teams can plan together, commit to a shared increment, and stay aligned. Available in[Cloud](/pricing "Cloud - included")[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=scale-agile-project-management)[Book a Demo](https://calendly.com/orangescrum) Free forever plan · No credit card required · Set up in minutes ## What is scaled agile? Scaled agile is how an organisation runs agile across several teams that have to deliver something together. Instead of each team planning alone, teams are grouped into an Agile Release Train and plan a Program Increment together. Orangescrum supports Essential SAFe with release trains, PI planning, a program board, WSJF prioritisation, ROAM risk handling, and flow metrics. The problem ## Why agile _breaks at scale_ Teams plan in isolation Each team runs its own sprint and nobody sees the dependencies between them. ✓ PI planning brings teams into one shared planning event. Priority is argued, not calculated Everyone believes their work is the most important. ✓ WSJF scores the backlog so priority is based on numbers. Risks have no owner Cross team risks get raised and then float, belonging to nobody. ✓ ROAM makes every risk resolved, owned, accepted, or mitigated. What you get ## Essential SAFe, _built in_ Grouped the way SAFe runs: the train, the increment, the planning event, the backlog, the boards, and the measures. 01Train - ### Agile Release Trains A train carries a name, a code, its PI length, its iteration length, and whether it runs an Innovation and Planning iteration. - ### Teams on the train Attach and detach teams with the dates they joined and left, so the history of the train stays accurate. - ### The four SAFe roles Assign Release Train Engineer, Product Manager, System Architect, and Business Owner, each with assigned and revoked dates. - ### Projects on the train Attach projects so their epics, features, and stories become the train's backlog rather than a separate list. - ### A health view Current increment and how far through it you are, objective value delivered, open risks, dependency count, and who the RTE is. - ### Duplicate, archive, export Copy a train to start the next one, archive a finished one, and export the train list as CSV or PDF. 02Increment - ### Program Increments Each increment carries a theme, its business context, its dates, and its status. - ### Iterations made for you The increment is sliced into iterations of the train's length and named automatically, so the cadence is never typed twice. - ### The IP iteration When the train uses one, the last iteration is marked as the Innovation and Planning iteration. - ### Lock and close An increment moves from planning to executing to closed in one direction only, and the lock records who did it and when. - ### A guided planning event PI planning runs as four steps: objectives, ROAM risks, confidence vote, then a summary. 03Planning - ### PI objectives Committed or uncommitted, owned by a team, with planned business value and, later, the actual value delivered. - ### The program board Teams across, iterations down, with features placed in cells and a committed load percentage on each placement. - ### Dependencies Link backlog items as blocks, related, duplicates, or parent of, and see the cross team ones drawn on the program board. - ### ROAM risks Every programme risk is resolved, owned, accepted, or mitigated, with an owner and the date it was identified. - ### Confidence vote A fist of five vote per person, optionally per team, over as many rounds as the event needs, with the average shown. 04Backlog - ### WSJF prioritisation Score business value, time criticality, risk reduction, and job size, and the ranking is calculated and kept as history. - ### Three levels Epics, features, and stories overlay your existing work items rather than creating a second backlog to keep in step. - ### Enabler stories Mark a story as an enabler and say which kind: architecture, exploration, infrastructure, or compliance. - ### Six filters Narrow by text, level, programme, train, increment, and team, then clear the lot in one click. 05Boards - ### One per level Epic, feature, and story each get their own Kanban with the states you define, starting from a Funnel to Done default. - ### A WIP limit per state Cap how much sits in any state, set which state is the entry point, and mark which ones mean done. - ### Audited transitions Define which moves are allowed, attach a required permission to a move, and every move is written to an audit row. 06Measures - ### Flow velocity Items completed per week, computed from real state transitions, with a recompute button and CSV export. - ### PI predictability Actual business value against planned, per team and for the train, counting committed objectives only. - ### Inspect and Adapt Record the session, the date it was held, the system demo notes, and the predictability it produced. - ### Improvement items Each one carries the problem, the root cause, the countermeasure, an owner, and the increment it is aimed at. 07Running it - ### A dashboard you arrange Eight cards covering progress, objectives, train health, features, dependencies, risks, roadmap, and the next ceremonies, in the order you drag them. - ### 44 permissions Nine groups covering train management, backlog, WSJF, PI planning, the program board, objectives, risks, Inspect and Adapt, and metrics. How it works ## How a _Program Increment_ runs 1 Form the train Group the teams that deliver a shared outcome into an Agile Release Train. 2 Prioritise Score the backlog with WSJF so the train works on the highest value items first. 3 Plan the increment Run PI planning, agree the objectives, and map dependencies on the program board. 4 Inspect and adapt Track flow metrics through the increment, then review and improve at programme level. Who it's for ## For organisations _past one team_ Enterprise delivery Several teams delivering one product or platform who need a shared plan. [Learn more →](/program-management-software) Regulated programmes Programmes that must show risk was owned and decisions were recorded. [Learn more →](/self-hosted) Growing engineering orgs Teams that outgrew single team Scrum and need structure without losing agility. [Learn more →](/agile-project-management) Availability ## Which edition includes _what_ Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes. Scaled Agile is on the Premium plan and in the Self-Hosted edition. Both editions ship the same feature set. | Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition | | Agile Release Trains | Premium | ✓ | ✗ | | Teams and SAFe roles on a train | Premium | ✓ | ✗ | | Program Increments and generated iterations | Premium | ✓ | ✗ | | PI planning wizard | Premium | ✓ | ✗ | | PI objectives with business value | Premium | ✓ | ✗ | | Program board with committed load | Premium | ✓ | ✗ | | Cross team dependencies | Premium | ✓ | ✗ | | ROAM risk handling | Premium | ✓ | ✗ | | Confidence vote | Premium | ✓ | ✗ | | WSJF prioritisation with history | Premium | ✓ | ✗ | | Kanban per level with WIP limits | Premium | ✓ | ✗ | | Flow velocity and CSV export | Premium | ✓ | ✗ | | PI predictability | Premium | ✓ | ✗ | | Inspect and Adapt with improvement items | Premium | ✓ | ✗ | | Scaled Agile permission matrix | Premium | ✓ | ✗ | | Scrum and sprints | Pro | ✓ | ✗ | Frequently asked questions ## Scaled Agile _FAQ_ ### Does Orangescrum support scaled agile? Yes. Orangescrum supports Essential SAFe with Agile Release Trains, Program Increments and PI planning, a program board, WSJF prioritisation, ROAM risk handling, confidence voting, Inspect and Adapt, and flow metrics. ### Which edition and plan includes it? Scaled Agile is part of the Premium plan in the Cloud edition and is included in the Self-Hosted edition. Both editions ship the same feature set. ### What is an Agile Release Train? An Agile Release Train is a group of teams that plan and deliver together on the same cadence. In Orangescrum a train carries its own PI length, iteration length, teams, roles, and projects, so the increments it runs are generated from its own settings. ### Do I have to set up every iteration by hand? No. When you create a Program Increment, Orangescrum slices it into iterations of the train's length and names them for you. If the train runs an Innovation and Planning iteration, the last one is marked as the IP iteration. ### What is WSJF? Weighted shortest job first is a way of scoring backlog items by value and effort so sequencing is calculated rather than argued. Orangescrum scores business value, time criticality, risk reduction, and job size, and keeps every score as history so you can see how a ranking changed. ### What does ROAM mean? ROAM is how SAFe handles programme risks. Each risk is marked resolved, owned, accepted, or mitigated, so no risk is left without a decision and an owner. ### Can we run a confidence vote? Yes. PI planning includes a fist of five vote, per person and optionally per team, over as many rounds as the event needs, with the average and the per team breakdown shown as people vote. ### How do we measure a Program Increment? PI predictability compares actual business value against planned for each team and for the train as a whole, counting committed objectives only. Flow velocity shows how many items the train actually completes per week. ### Does it use a separate backlog? No. The scaled agile levels sit on top of your existing epics, features, and stories, so the train's backlog and the teams' backlogs are the same work. ### Can we run Scrum and SAFe together? Yes. Individual teams keep running Scrum with their own sprints and backlogs, while the release train coordinates them across a Program Increment. ### Can we control who does what? Yes. Scaled Agile ships 44 permissions in nine groups, covering train management, backlog, WSJF, PI planning, the program board, objectives, risks, Inspect and Adapt, metrics, and administration. ### Do we need a separate SAFe tool? No. The scaled agile structures sit in the same tool as your teams' sprints, boards, and reports, so programme level planning uses the same data as team level delivery. ### Is scaled agile in the open source edition? No. The Community Edition covers core project and task management. Scaled Agile is available in the Cloud Premium plan and the Self-Hosted edition. ## Run agile across every team Scaled Agile is included in the Premium plan and the Self-Hosted edition. [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=scale-agile-project-management_cta)[Book a Demo](https://calendly.com/orangescrum) ## Related capabilities [Agile project managementScrum, Kanban, and sprints](/agile-project-management)[Program managementCoordinate multiple projects](/program-management-software)[Risk managementFull project risk register](/risk-management)[Advanced reportingPortfolio level reporting](/advanced-reporting)