Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
61 Cards in this Set
- Front
- Back
|
Safe Framework: What is it? |
Framework to structure agile orgs based on agile manifesto |
|
|
What are the Basic values of Safe? |
Transperency Program execution Building quality Alignment |
|
|
What is meant by essentials? |
10 key principles of Safe that must be applied to implement Safe |
|
|
What is the Max number of participants? |
125 otherwise social interaction is unmanageable |
|
|
What is the Sprint lenght in Safe? |
2 Weeks for all Teams, every two weeks teams present results to each other in System demo |
|
|
What is meant by release train? |
?? |
|
|
What is the release train Engineer doing? |
Scrum Masters of Scrum Masters Secures alignment of scrum teams |
|
|
How many product owners should be there? |
3 to 4 |
|
|
What is the System demo? |
All teams coming together to Show each other Sprint results |
|
|
What is a Feature? |
Bucket of user Stories equalling epic |
|
|
What is the System Team? |
Responsible for Software environment and System Integration |
|
|
Name the Safe lean agile principles! |
- take an economic view - apply systems thinking - assume variability, preserve options - build incrementally with fast, integrated learning cycles - base milestones on objective evaluation of working Systems - visualize and limit WIP, reduce batch sizes and manage queue length - apply cadence, synchronize wirh cross domain planning - unlock the intrinsic motivation of knowledge workers - decentralize decision-making - organize around values |
|
|
What are enablers pointing to? |
Architectural runway |
|
|
What is the architectural runway? |
?? |
|
|
On which 3 approaches is SAFe based? |
Agile dev Lean product dev System thinking |
|
|
Essential level roles of SAFe |
Business owner RT Engineer |
|
|
How many teams per release train? |
5 to 12 |
|
|
What happens during PI planning event? |
2 days Most important event Teams commit to objectives Planning per quarter |
|
|
ART Sync event |
1 hour Train team sync regarding PI progress |
|
|
Inspect and adapt event |
Half day Train reviews and improves processes before next PI each quarter |
|
|
What is the intention of SCRUM of SCRUMS event? |
= meeting of SCRUM masters and RTE to gain insights into team progress and program impediments continuous coordination on dependencies RTE synchronizes and keeps the train on track Held twice a week Time-boxed, but followed by meetings for problem solving |
|
|
DSU = |
Daily Standup |
|
|
What are the highest prios of the Scrum master? |
Preserve team autonomy Remove impediments |
|
|
What are the no gos for scrum master? |
Do teams work Push work to team members |
|
|
Whom does scrum master work wirh on essential level? |
RT Engineer Other agile teams |
|
|
What is the role of Scrum master in SAFe? |
Ensure train meets objectives with RT engineer Coordinate other scrum masters, system team and shared services in PI planning Work with teams throughout each iteration Participate in SCRUM of SCRUMS Foster normalized estimating Help team to operate under architectural and portfolio governance, system integration and system demo |
|
|
What is meant by shared services? |
Ressources supporting all teams e.g. consulting on social partner |
|
|
Which roles are servant leaders in SAFe? |
SM RTE |
|
|
What is servant leader behaviour? |
Understand the team Use persuasion to convince Listen and support the team |
|
|
Attributes of high performibg teams |
Self organized Mutual trust |
|
|
What are Scrum masters key behaviours? |
Facilitate team to find own answers Set the focus on business value delivery |
|
|
What should scrum master intention be when working with team issure? |
Coach team through team stages of Tuckman (forming, storming, norming, performing, adjourning) |
|
|
How to colloborate with other teams? |
Integrate work often with other teams multiple time during iterations Work with system team on automated system level tests Join other teams dailys, standups, demos Manage dependencies with system architect |
|
|
Key problem leading to team dysfunctions |
Absence of trust |
|
|
How to handle Fear of conflict |
Create save environment for conflict Encourage discussions on disagreements |
|
|
PI planning |
Product manager presents product / solution / vision and prioritized features Epics on the wall, tea.s could take any epic Team breakouts: develop draft plans, identify impediments Architects and product managers circulate through teams After breakout follows team presentation and management review 2 days = 2 cycles 2nd breakout includes business owner circulating and assigning business value to team objectives
|
|
|
Program wall |
During PI teams put features on timeline to highlight dependencies |
|
|
PI planning fundamentals |
2 days every 8 to 12 weeks Everyone attends in person PM with owns feature prio Agile teams own story planning and estimating Architect and UX as intermediaries for governance, interfaces, dependencies |
|
|
Pi planning Input and output |
Input vision and top 10 features Output program objectives and program board |
|
|
PIP = |
Program Increment Planning |
|
|
What is a feature? |
Fits in one program increment (hence, can be delivered in a quarter) Includes acceptance criteria Describes larger system behaviours that fullfils users needs Expressed in plain language |
|
|
Enabler stories |
Include Refactoring and spikes (research activities to reduce risk) Building or improving infrastructure Verification of system qualities |
|
|
SM role when estimating user stories |
Encourage to oarticipate Ensure relative estimates are used |
|
|
What prevents team from estimating |
Description to short Lacks acceptance criteria |
|
|
Anti patterns during PI planning that should be avoided |
Put pressure on team Focus on detailed plan instead of alignment |
|
|
What does it mean if a feature is placed in strings on the program board? |
It can only be completed if multiple teams deliver their parts |
|
|
What does limiting WIP work in progress mean? |
WIP limits the max stories in progress per worklow step: Ready stories 4 to 7 Development 5 Test 3 Goal is that every team member works only on one story |
|
|
SM role in tracking iterations |
Facilitate mid PI replanning Help team to reach PI objectives |
|
|
Who defines features in scope? |
Product manager |
|
|
Essential outcomes of iteration planning |
Iteration goals Iteration backlog |
|
|
SM role at systen demo |
Ensure that team is ready and coordinates with system team |
|
|
Relentless improvement is done by ... |
Iteration retrospective Inspect and adapt workshop |
|
|
SM helps team to improve in ... |
Quality Predictability Flow Relentless improvement |
|
|
Iteration retrospective |
1 to 1.5 hrs Agile team Identify 1 to 2 improvements Add to backlog |
|
|
Five dev ops focus area |
CALMR |
|
|
What is IP iteration? |
Innovation and planning iteration No work is planned for IP |
|
|
What does it mean if a feature is accepted by PM? |
Feature hypothesis was fully evaluated meaning acceptance criteria met |
|
|
Who defines objectives? |
Team for itself RTE for overall iteration |
|
|
What are steps in root cause analysis? |
Agree on problem |
|
|
Who writes enablers? |
System architect |
|
|
What is thenoptimal ratio between user stories and enablers? |
20 to 80 |
