Scaled Agile Framework - SAFE
Comprehensive Questions (Frequently
Tested) with Verified Answers Graded
A+
4 SAFE core values (BAPT) - Answer: BuildIn Quality, Alignment, Program Execution,
Transparency
House of Lean Säulen (RIFR) - Answer: Respect for individuals, Innovation, Flow, Relentless
(unerbittlich) improvement
Agile Manifesto (12 Points) - Answer: satisfy the customer -
Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.
Welcome changing requirements -
Welcome changing requirements, even late in development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently -
Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business & Dev work together -
Business people and developers must work together daily throughout the project.
,projects around motivated individuals -
Build projects around motivated individuals. Give them the environment and support they
need, and trust them to get the job done.
face-to-face conversation -
The most efficient and effective method of conveying information to and within a development
team is face-to-face conversation.
Working software metric -
Working software is the primary measure of progress.
sustainable development -
Agile processes promote sustainable development. The sponsors, developers, and users should
be able to maintain a constant pace indefinitely.
attention technical excellence -
Continuous attention to technical excellence and good design enhances agility.
Simplicity —
the art of maximizing the amount of work not done — is essential.
arch self-organizing teams -
The best architectures, requirements, and designs emerge from self-organizing teams.
reflect about effectiveness -
,At regular intervals, the team reflects on how to become more effective, then tunes and adjusts
its behavior accordingly.
Agile Manifesto (the "over" rules) - Answer: Individuals and interactions OVER processes and
tools
Working software OVER comprehensive documentation
Customer collaboration OVER contract negotiation
Responding to change OVER following a plan
ValueStream - Answer: Modelliert einen Kreativen KundenProzess, CashFlow generiet, oder
CashFlow generierung unterstützt,
Operational ValueStream
Development ValueStream
ValueStream Engineer - Answer: Escalates impediments,
manages risks,
helps ensure value delivery,
improves ValueStream
Was ist ein ART - Answer: Agile Release Train -
Wer ist RTE - Answer: Release Train Engineer
Enabler - Answer: Enabler sind technische Sachen, die man zur Implementierung on fachlichen
Aufgaben braucht.
, z.B. refactoring eines Software Paketes, before man ein neues fachliches Modul implementiert.
Was sind functional / technical spikes? - Answer: Spikes sind Aufgaben,
die mit einer max. Zeit bewertet sind. Sie sind fertig, wenn die Zeit abgelaufen ist.
Im Gegensatz zu Stories, die mit Punkten bewertet sind und fertig sind, wenn sie fertig sind.
Spikes nimmt man, um Ungewisse Aufgaben schon einmal anzuengen, ohne die Planung
durcheinander zu schmeissen.
Ist eine Aufgabe ungewiss, so sondiert man diese im vorherigen PI mit Spikes vor.
Functional / Technical sagt nur was ueber das Thema. Func. also fachlich. Technical, also
ENabler.
Was sind Stretch Objects? - Answer: Ungewisse Aufgaben, auf die auch Zeit eingeplant wird,
auf die sich das Team aber nicht kommittet. (man verspricht sie noh niemandem). Sowas
bereitet man mit Spikes vor.
I & A ? - Answer: Inspect & Adopt
Welche EPICS gibt es? - Answer: Portfolio EPICS
Enabler EPIC
Business EPIC
ValueStream EPICS
Comprehensive Questions (Frequently
Tested) with Verified Answers Graded
A+
4 SAFE core values (BAPT) - Answer: BuildIn Quality, Alignment, Program Execution,
Transparency
House of Lean Säulen (RIFR) - Answer: Respect for individuals, Innovation, Flow, Relentless
(unerbittlich) improvement
Agile Manifesto (12 Points) - Answer: satisfy the customer -
Our highest priority is to satisfy the customer through early and continuous delivery of valuable
software.
Welcome changing requirements -
Welcome changing requirements, even late in development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently -
Deliver working software frequently, from a couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business & Dev work together -
Business people and developers must work together daily throughout the project.
,projects around motivated individuals -
Build projects around motivated individuals. Give them the environment and support they
need, and trust them to get the job done.
face-to-face conversation -
The most efficient and effective method of conveying information to and within a development
team is face-to-face conversation.
Working software metric -
Working software is the primary measure of progress.
sustainable development -
Agile processes promote sustainable development. The sponsors, developers, and users should
be able to maintain a constant pace indefinitely.
attention technical excellence -
Continuous attention to technical excellence and good design enhances agility.
Simplicity —
the art of maximizing the amount of work not done — is essential.
arch self-organizing teams -
The best architectures, requirements, and designs emerge from self-organizing teams.
reflect about effectiveness -
,At regular intervals, the team reflects on how to become more effective, then tunes and adjusts
its behavior accordingly.
Agile Manifesto (the "over" rules) - Answer: Individuals and interactions OVER processes and
tools
Working software OVER comprehensive documentation
Customer collaboration OVER contract negotiation
Responding to change OVER following a plan
ValueStream - Answer: Modelliert einen Kreativen KundenProzess, CashFlow generiet, oder
CashFlow generierung unterstützt,
Operational ValueStream
Development ValueStream
ValueStream Engineer - Answer: Escalates impediments,
manages risks,
helps ensure value delivery,
improves ValueStream
Was ist ein ART - Answer: Agile Release Train -
Wer ist RTE - Answer: Release Train Engineer
Enabler - Answer: Enabler sind technische Sachen, die man zur Implementierung on fachlichen
Aufgaben braucht.
, z.B. refactoring eines Software Paketes, before man ein neues fachliches Modul implementiert.
Was sind functional / technical spikes? - Answer: Spikes sind Aufgaben,
die mit einer max. Zeit bewertet sind. Sie sind fertig, wenn die Zeit abgelaufen ist.
Im Gegensatz zu Stories, die mit Punkten bewertet sind und fertig sind, wenn sie fertig sind.
Spikes nimmt man, um Ungewisse Aufgaben schon einmal anzuengen, ohne die Planung
durcheinander zu schmeissen.
Ist eine Aufgabe ungewiss, so sondiert man diese im vorherigen PI mit Spikes vor.
Functional / Technical sagt nur was ueber das Thema. Func. also fachlich. Technical, also
ENabler.
Was sind Stretch Objects? - Answer: Ungewisse Aufgaben, auf die auch Zeit eingeplant wird,
auf die sich das Team aber nicht kommittet. (man verspricht sie noh niemandem). Sowas
bereitet man mit Spikes vor.
I & A ? - Answer: Inspect & Adopt
Welche EPICS gibt es? - Answer: Portfolio EPICS
Enabler EPIC
Business EPIC
ValueStream EPICS
