Visualizing and Measuring the Flow of Work
Quality and DevOps
Communication and Synchronization + Iteration Review
Improving with the Iteration Retrospective
BONUS
100

Improve the flow of work

What are WIP limits?

100

Agile testing, behavior-driven development, test-driven development, refactoring, code quality, and Agile architecture

What are Built-in Quality practices for software teams?

100

What did I do yesterday to advance the Iteration Goals?

What will I do today to advance the Iteration Goals?

Are there any impediments that will prevent the team from meeting the Iteration Goals?

Basic daily stand-Up (DSU) agenda?

100

Enter the improvement items in the Team Backlog

What is the outcome of the Iteration Retrospective?

100

Full, Large Solution, Portfolio, Essential

What are the four configurations of SAFe?

200

Ensures teams deliver value in the shortest possible time

What is flow time?

200

Existing code, hardware components, marketing branding guidelines, etc., that enable near-term business Features.

What is the architectural runway?

200

► Provides the true

measure of progress by showing

working software functionality,

hardware components, etc.

► Preparation starts with planning

► Teams demonstrate every Story,

spike, refactor, and non-functional

requirement (NFR)

► Attendees are the team and its

stakeholders

What is the Iteration Review?

200

An Agile Team discusses what went well, what didn't go well, what can we do better next time during this part of the Iteration Retrospective

What is the qualitative part of the team retrospective?

200

• Apply Lean system engineering to build really b19 systems

• Coordinate and align the full supply chain

• Continually evolve live systems

What it Enterprise Solution Delivery?

300

How much of the overall flow time is spent in value-added work activities vs. waiting between steps.

What is flow efficiency?

300

Culture, Automation, Lean Flow, Measurement, Recovery

What is CALMR approach to DevOps?

300

1. Review business context and

Iteration Goals

2. Demo and solicit feedback of each Story, spike, refactor, and NFR

3. Discuss Stories not completed and why

4. Identify risks, impediments

5. Revise team backlog and Team PI Objectives as needed

What is an Iteration Review Agenda?

300

Pick one or two items that can be improved upon for the next Iteration

What is the purpose of the Iteration Retrospective

300

VALUE

Respect for people and culture

Flow

Innovation

Relentless Improvement

Leadership

What is the Lean House of Value?

400

A leading indicator of excess work in process (WIP)

What is flow load?

400

Represents the workflows, activities, and automation needed to deliver new functionality more frequently.

What is the Continuous Delivery Pipeline (CDP)

400

Team Increment, System Increment, Solution Increment, Release

What is a scalable definition of done?

400

An Agile Team collects the Iteration metrics they have agreed upon during this part of the team retrospective

What is the quantitative part of the team retrospective?

400

The ability to compete and thrive in the digital age by quickly responding to market changes and emerging opportunities with innovative, digitally-enabled business solutions

What is Business Agility?

500

Flow Distribution

Flow Velocity

Flow Time

Flow Load

Flow Efficiency

Flow Predictability


What are SAFe's six flow metrics?

500

Teams continuously integrate assets (leaving as little as possible to the System Team).

Trunk-based development

500

Stories satisfy acceptance criteria

Acceptance tests passed (automated where practical)

Unit and component tests coded, passed, and included in the BVT

Cumulative unit tests passed

Assets are under version control

Engineering standards followed

NFRs met

No must-fix defects

Stories accepted by Product Owner

What is the Definition of Done for the Team Increment
500

► Periodically measure the progress

being made toward the three TTA dimensions

► Identify specific practices for potential

improvement

► Reassess periodically to observe

trends

What is a Team and Technical Agility (TTA) competency assessment?

500

Alignment, built-in quality, transparency, and program execution represent the fundamental beliefs that are key to SAFe’s effectiveness. These guiding principles help dictate behavior and action for everyone who participates in a SAFe portfolio.

What are the four Core Values?