Lesson 1
Lesson 2
Lesson 3
Lesson 4
Lesson 5
100

.....is the primary measure of progress.

Working software

100

►Features fit in one .... and Stories fit in one......

PI, Iteration

100

......... are business summaries of what each team intends to deliver in the upcoming PI.

PI Objectives

100

workshop is a preview and elaboration of upcoming Stories.

Backlog Refinement

100

In this meeting, Participants are Product Managers, Product Owners, other stakeholders, and SMEs, as necessary

PO Sync

200

a virtual organization of 5 to 12 teams (50 to 125 individuals)

Agile Release Train (ART)

200

A cadence-based event that serves as the heartbeat of the ART creating an alignment

PI Planning

200

The categories of ROAMing Risks are Resolved, Owned, ......... and Mitigated

Accepted

200

All team members participate but Product Owners and Scrum Masters do not participate (only active observers)

Poker Planning, Daily Standup

200

One of the three parts of I & A ( Inspect & Adapt) Event

PI System Demo

Quantitative & Qualitative Measurement

Problem-Solving Workshop

300

knowledge base of proven, integrated principles, practices, and competencies for achieving Business Agility

SAFe (Scaled Agile Framework)

300

WSJF = (........+.......+.........)/Job Size

Business Value, Time Criticality, RR & OE

300

Product Management communicates this at the beginning on Day 1 of PI Planning 

Vision and Top X Features

300

The elements of a good User Story can be found in the this model, developed by Bill Wake (Hint: has got 6 parts to it :-)

INVEST Model

300

A common anti-pattern for System Demo

A lot of time is spent preparing for the demo/Demo is mainly talk or slides as opposed to working software and/or hardware/POs and PMs see things for the first time in the System Demo/System Demo is not done because “the Team Demo is enough”/Team members are not invited to the System Demo to save time/Demos are not interesting or relevant to Program-level stakeholders/Using test data

400

Provides processes and tools to integrate, and evaluates assets early and often

System Team

400

Market ........ and ......... influence solution and PI Roadmaps.  

Rhythms and Events

400

During the Final Plan Review, ........... are asked whether they accept the plan or not

Business Owners

400

........provide clarity, commitment, and management information and align team members to a common purpose

Iteration Goal

400

Program Predictability Measure (PPM) recommended range (in %)

80%-100%

500

The sequence of activities needed to deliver a product or service to a Customer

Operational Value Stream

500

Helps balance functionality(features) with Architectural Runway(enablers)

Capacity Allocation

500

The Program Board visualizes the delivery targets of the Features, the main dependencies between the teams and ............

Milestones

500

Continuous Delivery Pipeline has Continuous Exploration, Continuous Integration, ......... and ...........

Continuous Deployment, Release on Demand

500

This provides sufficient capacity margin to enable cadence and help teams focus on innovation

IP (Innovation & Planning) Iteration

M
e
n
u