SAFE AGILIST (ACTUAL / ) EXAM/ QUESTIONS WITH
ANSWERS / ALREADY GRADED A+/
acceptance critera - --Ansswers---Acceptance criteria are used to determine whether the implementation of a feature is correct and delivers the business benefits
ex:
Feature - Multi-factor authentication
- USB tokens as a first layer
- password authentication
- multiple tokens on single device
shared committment - --Ansswers---what does estimation create?
estimation - --Ansswers----increases accuracy by including all perspectives -builds understanding -*creates shared commitment*
*only people who are doing the work can estimate, it is a whole team excercise*
- / 4
Cost of Delay components - --Ansswers---1. User Business Value
- Time Criticality
- Risk Reduction and Opportunity Enablement
cost of delay - --Ansswers---"if you quantity one thing, quantify the ____ __ ______"
prioritization of features - --Ansswers---Flow based system
requires knowing two things:
- Cost of Delay of delivering value
- Duration to implement the value
Weighted, Shortest Job First (WSJF) - --Ansswers---an economic model for prioritizing "jobs" based on product development flow.
= Cost of Delay / Job Duration (job size)
Program Increment Planning - --Ansswers---a cadence based, face to face vent that serves as the heartbeat of the ART, aligning all the teams on the ART to a shared mission and Vision
*takes place over 2 days every 8-12 weeks* 2 / 4
*everyone attends in person* - including customer and c-suite
uncommitted objectives - --Ansswers----they are planned and aren't extra things teams do "in case they have time" -are not included in the commitment, thereby making the commitment more reliable -becomes this when teams have low confidence in meeting a PI objective -*they DO count in velocity/capacity*
Iteration capacity - --Ansswers----for every full time Agile team member contributing to solution development, give the team 8 points -subtract 1 point for each team member vacation day -find a small Story that would ttake about a half day to develop and a half day to test and validate. call it a 1.-estimate every other story relative to that one
management review and problem solving - --Ansswers--- what takes place at the end of PI planning day 1?
Program Board - --Ansswers---where feature *delivery*, *dependencies*, and *milestones* are displayed
ROAMing risks - --Ansswers---after all plans have been presented, remaining program risks and impediments are discussed and categorized 3 / 4
Resolved - has been addressed. no longer a concern Owned - someone has taken responsibility Accepted - nothing more can be done.Mitigated - team has plan to adjust as necessary
confidence vote - --Ansswers---after dependencies are resolved and risks are addressed in PI planning, this is taken by the team and program
1-5 (1 being least, 5 being most)
program events - --Ansswers---what drives the train?
these create a closed loop system to keep the train on the tracks
Scrum of Scrums PO Sync System Demo Preparing for PI planning Inspect and Adapt PI Planning
ART Sync - --Ansswers---Scrum of Scrums and PO Sync
- / 4