A group of dedicated individuals whe are empowered, self-organizing, self-managing, and deliver value

A large group of individuals who all work together to create value for the client

A small group of tipically 5-11 dedicated individuals who have the skills necessary to define, build, test, and deploy incréments of value

A stand-alone unit of individuals who do not require input from other teams to complete their tasks

A group of dedicated individuals that work in phase-gate steps to complete their PI objectives

Organizations that need to have system demos after each iteration

organizations that need to scale agile across the enterprise

organizations that operate in an environment that requires compliance for complex, high assurance systems

every large enterprise that uses SAFe

to facilitate the pi planning session

to define the tasks and assign owners

to priotirize the team's backlog

to remove impediments in order to help protect the team

Increases work in process

Increases visibility

Increases throughtput

Decreases stress on the system

The self-assessment information for the teams

The cycle time system information which starts the implementation

The data for the team to identify current bottlenecks

The derived predictability data for the team

Visibility into analysis, approval, and feature readiness for implementation

Visibility into scope and priority ajustments

Visibility intop programs Epics and features

Visibility into backlog items

Refining the program backlog

a demo for the integrated system

Planning the next PI

a retrospective for the iteration

It is required for speed of value delivery and Solution intent

it is required for implementation speed and maturity

it is required for backlog speed and designed refinement

it is required for speed of development and maintenability

Program level analysis of a problem using root cause analysis techniques

Estimation of stories

gathering feedback from the stakeholders

Team Discussion around opportunities for continuous improvment

They verify that teams are working at their fuull capacity

They are used to measure business value achieved for each iteration

They align team to a common vision of work in the iteration

They are used to track scope changes over time

Ten weeks

Four weeks

Eight weeks

Two weeks

By having the product owner verbally communicate to the stakeholders

by representing status sllides

By showing the actual working product

By showing screen shots of the product

It identifies possible constraints for solution completion

It captures where all new "big" ideas come from

it helps analyse, approve, and track Portfolio Epics and Enablers

It encourages collaboration and enables flow

Time to complete a Feature

Work in process across the team

team capacity

the number of defects that escape to production

To help the team bond and work more efficiently together

To increase the quality and reliability of the next PI

To evaluate better implementation steps

To enhance ans improve the innovation and planning practices

Number of days it will take

Complexity

Priority

Team size

Dependencies between teams

Program-level risks

Work breakdowns

Each teams tasks

It is the main way in SAFe for achevieng relentless improvement

It provides time to identify dependencies and issues that could impact the next iteration

It serves a variety of purposes, including a dedicated time for planning, retrospecting, exploring, and innovating

It allows th eteam to state the problemeand think about what, where, when and the impact

Choose a problem to solve--agreement not required

Identify the biggest root cause using the Pareto analysis

Brainstorm possible failures

Apply root solution analysis

It is to analyse, approve, and ready Features for implementation

It is to break Stories into tasks that are achievable in the team's capacity

It is to organize the work and define a realistic scope for the iteration

It is to explore and implement program Epics and split them into features to be further explored

key stakeHolders

PI Planning

Program backlog

Customers

Implement the simplest variant of the functionality first and the implement the rest as an enhancement

Develop the functionality first and then test it on a second pass

Implement the database structure first and then implement the business logic and user interface

Develop the User interface (UI) with sample business logic and database access and then add the actual functionality behind the UI

Development and test environments should be separate from production

Automate testing Features and nonfunctional requirements

Deploy to staging every third iteration

Maintain manual deployment

Maintain a staging environment that emulates production

Continuous integration

Pair programming

Deployment automation

intentional architecture

Test-driven development

Identifies market needs

Leads by example

Establishes Feature accceptance criteria

Listen and supports teams in problem identification and decision-making

Owns vision and Roadmaps, Program Backlog and ROI

When the System Team is ready

Each week

Only when all stakeholders are available

At the end of every iteration

20 minutes

5 minutes

10 minutes

15 minutes

it is for developers only

It comes from pair programming in Extreme Programming (XP)

It occurs during iteration planning

it is a best practice that team members should spend 50 % to 100% of the time in pair work

Autonomy

Options

Innovation

Predictability

Product Management

Continuous Delivery Pipeline

Lean Portfolio management

Release Governance

The PO does not need to attend

Items are assigned to the eteam members

It occurs on the last day of the iteration

It is required for every iteration to enable fast Learning cycles

Each team member can do all activities to define, build and test a solution

Each team member can define and build, with a system team testing the solution

Each team can deliver Features across multiple domains

Each team member can define, build, and test a component feature

40

48

32

52

They are ignoring nonfunctional requirements within the iteration

They are applying the agile development Practice of "separation of concerns"

They are waterfailing the iteration

They are abusing the practice of hardening

Definition of done

What

Why

How

Who

A routine method of deploying deliverables to operations

A methodology used to deliver usable and reliable solutions to the end user

A lightweight process for cross-functional, self organizing teams

A process for continuosly maintaining deployment readiness

To guarantee no changes are made to the scope during an iteration

Facilitate more than two teams

Facilitate the PI planning session

To act as a servant leader and xhibit Lean-agile leadership

To facilitate the team's progress toward the iteration goals

A story is written in full detailed spécifications so that the work is ready to be implemented immediately

No further conversation is required after the story is identified because it contains all necessary details

story acceptance criteria must be finalized before beginning iteration planning

A story provides just enough information for the intent to be understood by both business and technical people

It identifies when too much work is in the system which result in multitasking and frequent context switching

It is a long-lived, self organizing, virtual organization of 5-12 agile teams tha plan, commit, and execute together

It is the primary value delivery construct in the Scaled Agile Framework

It is used to describe large system behaviors that fulfill Custome needs

It shows the deliverables for the currently commited PI and offers visibility into the next two PIs

Cadence

Culture

Cycle-Time

Continuous integration