SAFe (Scaled Agile Framework) Overview

Explore SAFe, the scaled agile framework, enabling lean, agile, and DevOps at enterprise scale, and learn its four configurations and practices that foster alignment and faster delivery.

Explore how SAFe organizes work across agile teams, agile release trains, and portfolios, detailing team roles, backlogs, blue business stories, red enabler stories, and planning interval.

Navigate the SAFe big picture and explore the free SAFe website, discovering product management, product owner roles, and customer centricity.

Explore SAFe core values alignment and transparency, the first two values at the framework's heart, and learn how aligned vision and open communication drive faster delivery and customer focus.

Explore SAFe core values—respect for people and relentless improvement—and how people-first cultures drive engagement, collaboration, and continuous system improvement.

Explore how leadership and culture, together with team and technical agility, form the foundation of SAFe adoption. Learn leadership behaviors and how cross-functional teams deliver value with built-in quality.

Explore Agile as a mindset grounded in four values and twelve principles, with self-organizing teams, definition of done, cadence, timeboxing, and retrospectives in Scrum and SAFe.

embrace the agile manifesto and its 12 principles to deliver valuable software early and continuously, welcome changes, and foster collaborative, sustainable, technically excellent teams.

Explore agile values that prioritize individuals and interactions over processes and tools and working software over comprehensive documentation, enabling collaboration and faster value delivery.

Explore how agile values prioritize customer collaboration over contract negotiation and responding to change over following a plan to help teams build the right product through close customer collaboration.

SAFe lean agile principles guide scalable delivery for large teams, emphasizing economic and systems thinking, incremental building, working software milestones, value flow, and cross-domain planning.

Compare waterfall and agile delivery, showing the six-month first release in waterfall versus one-month cycles in agile that deliver MVP increments and incorporate customer feedback to reduce risk.

Discover how a minimum viable product delivers usable value early and invites direct customer feedback to drive iterative, incremental improvements toward a faster, more capable solution.

Lead a cross-functional, self-organizing agile team of 5–11 members that defines, builds, tests, and delivers increments using Safe Scrum or Safe Kanban. Plan, receive feedback, and relentlessly improve together continually.

Learn how the Scrum framework is used at the team level in SAFe, including capacity and iteration planning, daily team sync, reviews, and retrospectives for enabler and business stories.

Identify the product owner's responsibilities in SAFe, including connecting with customers, articulating needs, prioritizing the team backlog, contributing to the vision and roadmap, and gathering feedback to deliver value.

Explore markets and user needs, and assess competitor and pricing strategies. Product management defines the product strategy and roadmaps, while product owners manage the ART backlog, delivering value to customers.

Meet the agile team, a cross-functional, self-organizing group of 5 to 11 people—including product owners, scrum masters, and developers—delivering software increments with Safe Scrum or Safe Team Kanban.

Guide pi planning, support iteration execution, and remove bottlenecks as a scrum master or team coach; coach teams in agile techniques to improve flow, performance, and inter-team dependencies.

Coordinate five to twelve agile teams into a cross-functional single value stream, creating an agile release train that continuously delivers value through synchronized PI planning and a shared backlog.

Understand how SAFe captures requirements from epics to features and stories, differentiates business and enabler epics, and defines features with benefit hypotheses and acceptance criteria, tied to PI and ART.

Explore SAFe iteration level events: plan capacity and select stories, hold team sync, conduct iteration review with stakeholders, refine backlog, and reflect in an iteration retrospective on ways of working.

Prepare features and the solution vision for the upcoming PI planning, then plan with the ART, including coach sync, PO sync, ART sync, system demo, and inspect and adapt.

Plan, build, validate a full system increment within a PI, a time box of 8–12 weeks with 4–6 two-week iterations plus one innovation and planning iteration, and demonstrate value.

Understand PI planning as a cadence-based heartbeat that aligns all teams on ART to a shared mission and vision, with product management prioritizing features and agile teams planning stories.

Learn the two-day SAFe PI planning agenda, from business context and product vision to capacity planning, team breakouts, risk review, and confidence voting, with plan adjustment and retrospective.

Explore WSJF in SAFe, prioritizing backlog items by cost of delay (user business value, time criticality, risk reduction or opportunity enablement) over job size to maximize economic value.

Explore the Tuckman model of team development, tracing forming, storming, norming, performing, and adjourning to improve collaboration and build highly effective teams.