Product Owner

A member of the Agile Team responsible for defining Stories and prioritizing the Team Backlog to
streamline the execution of program components for the team.

© Scaled Agile, Inc.

Include this copyright notice with the copied content.

Primary role of PO

Accept stories

Person responsible for the Program backlog

Product Manager

Person responsible for Solution backlog

Solution management

The PI cadence includes:

Planning, execution, demo, inspect and adapt (I&A)

SAFe Principle #1 is:

Take an economic view

SAFe Principle #2 is:

Apply systems thinking

SAFe Principle #3 is:

Assume variability; preserve options

SAFe Principle #4 is:

Build incrementally with fast, integrated learning cycles

SAFe Principle #5 is:

Base milestones on objective evaluation of working systems

SAFe Principle #6

Visualize and limit WIP, reduce batch sizes, and manage queue lengths

SAFe Principle #7 is:

Apply cadence, synchronize with cross-domain planning

SAFe Principle #8 is:

Unlock the intrinsic motivation of knowledge workers

SAFe Principle #9 is:

Decentralize decision-making
Set Based Design (SBD) or Set Based Concurrent Engineering (SBCE)

Consider design choices at the beginning. Continuously evaluate economic and technical trade-offs.
Eliminate weaker options.

Scaled Agile Framework Core Value #1

Built in-quality

Scaled Agile Framework Core Value #2

Program Execution

Scaled Agile Framework Core Value #3

Alignment

Scaled Agile Framework Core Value #4

Transparency

An Agile team is

Cross functional, self-organizing entities that can define, build, and test a thing of value.

An Agile team applies basic scientific practice:

Plan, do, check, adjust

An Agile team delivers value...

every two weeks

Test automation supports...

rapid regression testing

The real iteration progress indicators are...

Passing vs. not-yet-passing and broken automated tests

An Agile team aligns...

50-125 practitioners to a common mission

An Agile team applies...

cadence and synchronization, program increments every 8-12 weeks

Architectural Runway

Existing code, hardware components that technically enable near term business features

Enablers

Extend the architectural runway

Demo from...

the staging environment, or the nearest proxy

Integrated solution demo

Demonstrate the full system every two weeks

C in CALMR

Culture of shared responsibility

A in CALMR

Automation of Continuous Delivery Pipeline

L in CALMR

Lean flow accelerates delivery

M in CALMR

Measurement of everything

R in CALMR

Recovery enables low risk releases