Scribd
Upload
393 views2 pages

Scaled Agile Exam Study Guide

The document discusses key concepts in Scaled Agile Framework (SAFe) including continuous delivery, program Kanban, program events, iteration retrospectives, continuous exploration, DevOps, feature prioritization using cost of delay, shifting testing left, and innovation planning. It also provides guidance on breaking down features into user stories and using feature toggles to separate deployment from release.

Uploaded by

George Munteanu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
393 views2 pages

Scaled Agile Exam Study Guide

The document discusses key concepts in Scaled Agile Framework (SAFe) including continuous delivery, program Kanban, program events, iteration retrospectives, continuous exploration, DevOps, feature prioritization using cost of delay, shifting testing left, and innovation planning. It also provides guidance on breaking down features into user stories and using feature toggles to separate deployment from release.

Uploaded by

George Munteanu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 2

every incremental delivery has higher value, faster feedback

Continous delivery: Cont. deployment, release on demand, Continuous Integration

Prgram Kanban facilitates the FLOW of featres thru CDP

Program Event = Inspect & Adapt

Iteration Retro = team level (not program)

Go/No go = still a waterfall term

Program Sync = scrum of scrums and PO sync

system demo = program event, not sync!

iteration planning = team ceremony

CALMR = lean flow

Continuous exploration phase: Hyphothesize, Collaborate&Research, Synthesize(for backlog)

DevOps = bridge gap between New and stable solutions

end goal of DevOps = deliver value faster and more reliably

Gemba walks = when researching features, leave your desk and collaborate&research during
Continuous exploration(analyze phase, customer surveys, trade studies, talk to the customers, design
thinking)

WSJF is completed BEFORE PI planning (during analysis)....


WSJF = favors HIGHER cost of delay and shorter duration
WSJF is done using relative estimation (start with 1 as lowest)

features = benefit hyphothesis + acceptance criteria


(we break features into user stories)

prioritizing features: most important is Cost of Delay

Cost of Delay = time criticality

story must fit iteration


feature must fit 8-12 week PI.

Job size is a proxy for duration EXCEPT when you must consider Lead Times(because there could be
a wait before teams can start on the feature -> might want to relatively estimate using duration, as
long as you keep the same relative estimation for the column)

A feature leaves the CE(cont expl) phase at the PI planning(once you commit to it and break down in
stories and the 1st story is started)

Developer should integrate the code CONTINOUSLY


full system demo occurs when features complete every 2 weeks following iteration review

early validation provides early validation of a working system AND risk reduction

the traditional V-Model of testing delays feedback.


shifting testing left enables faster feedback

feature toggle enables the separation of deployment and release(Deployed on server vs released to
customer)

pi planning occurs during the IP innovation&planning (usually they line up once/quarter but not always
- can be 8-12 weeks)

IP (innovation planning) occurs as the last iteration

Without the IP iteration, there is no dedicated time to plan together, there is little innovation.
Inspect&Adapt: Problem solving & quantitative measurement & system demo

Stretch objectives are counted in the ACTUAL actual/achieved business value, but not in the planned
business value
Problem solving workshop steps:
1. decide on the problem to solve

2. apply root cause analysis(fishbone diagram)

3. brainstorm solution

If the question says “ART” that means they are referring to Program Level SAFe, else if they are
referring to “ARTS”, that means they are referring to Solution Level SAFe where roles would be
different. ART has RTE-Release Train Engg whereas ARTS has many RTEs managing their
respective train + one STE-Solution Train Engg
The text used in question SAFe means they are referring to Scaled Agile Framework and safe or Safe
means just a word and not Scaled Agile

You might also like