POPM Test, POPM Scaled Agile
Framework Sample Test
Team Kanban
method that helps teams facilitate the flow of
value by visualizing workflow, establishing
Work In Process (WIP) limits, measuring
throughput, and continuously improving their
process.
Team Level
contains the roles, activities, events, and
processes which Agile Teams build and deliver
value in the context of the Agile Release Train
(ART).
Team and Technical Agility Competency
describes the critical skills and Lean-Agile
principles and practices that are needed to
create high-performing Agile teams who create
high-quality, well designed technical solutions.
Value Stream Coordination
provides guidance to manage dependencies and
exploit the opportunities in a portfolio.
,Value Streams
represent the series of steps that an organization
uses to build Solutions that provide a
continuous flow of value to a customer. A SAFe
portfolio consists of a set of development value
streams, each of which builds and supports one
or more solutions.
Vision
description of the future state of the Solution
under development. It reflects Customer and
stakeholder needs, as well as the Feature and
Capabilities, proposed to meet those needs.
Weighted Shortest Job First (WSJF)
prioritization model used to sequence jobs (eg.,
Features, Capabilities, and Epics) to produce
maximum economic benefit. In SAFe, is
estimated as the Cost of Delay (CoD) divided
by job size.
Large Solution SAFe configuration
introduces the Business Solutions and Lean
Systems Engineering competency, which
supports those building the largest and most
complex solutions that require multiple Agile
Release Trains and Suppliers, but do not require
,portfolio-level considerations.
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: