Agile is based on empirical process control — things are verifiable by observation or experimentation; transparency, Inspection and adaptation are the 3 pillars of empiricism. Show
Application: the famous Plan, Do, Check, Adjust/Adapt (PDCA) is a learning cycle…things are inspected and adaptation follows based on what has been learned and observed. This cycle occurs at every level be it team level, program level, or solution level… hence the mantra ‘Inspect and Adapt’ for relentless and continuous improvement. At the program Level of SAFe, there is a program event called ‘Inspect and Adapt (I&A)’. No surprise there. The purpose of which is exactly that, to pursue relentless and continuous improvement. It comes in three parts: 1) the system demo; 2) the quantitative measurement; 3) retrospective and problem solving workshop. The system demo: This is the time for product manager and or product owner to demo the features — representing the business objectives — that were completed and accepted during the program increment, with the development teams and/or system team setting up the staging environment for the demo. The quantitative measurement: during the system demo, business owners, customers and other vital stakeholders collaborate with the Agile team to rate the actual business value of the objectives. The planned and actual business values are input to the program predictability measure calculation….a measure of the predictability of delivery of value by the ART. As you can see in the image below, the sweet spot is between 80% and 100% predictability… otherwise, address and improve. Retrospective and Problem solving workshop: in the retrospective part, the main idea is to identify significant problems for the teams to solve and the program to solve. It’s open season — anybody can nominate a problem to solve be that be at the team level or program level … self-selection of problem to solve is encouraged. This self-selection encourages cross-functional and multi-dimensional view of problems … and seeds the problem solving workshop with those who are most impacted and most voracious to solve the problem. For program-level problem solving workshop, a structured approach is used … the six-step is illustrated in the image below. Follow the six steps from left to right top row first.Remember relentless and continuous improvement? Yeah…make sure that you put the improvement items to the team/program improvement backlog and roadmap… and address / act upon these… otherwise, what’s the point of having this ‘Inspect and Adapt’?
What is the name of the event where all team members determine how much of the team's backlog they can commit to delivering during an upcoming Iteration?Solution PlanningSolution DemoIteration PlanningBacklog Refinement
Why do teams have an Iteration Retrospective?To iterate on storiesTo identify acceptance criteriaTo adjust and identify ways to improveTo evaluate metrics
To adjust and identify ways to improve
What is the recommended frequency range for PI Planning in SAFe?Every 6 to 8 weeksEvery 12 to 16 weeksEvery 4 to 6 weeksEvery 8 to 12 weeks
Which demo is performed in the IP Iteration?The demo from the team's final IterationsThe PI System DemoThe Integrated Demo from the Agile Release Train's final IterationThe demo from all the Agile Release Trains' Iterations
The Integrated Demo from the Agile Release Train's final Iteration
The program board highlights feature delivery dates, milestones, and what else for Agile Release Train teams?DependenciesTimeboxesRequirementsObjectives (adsbygoogle = window.adsbygoogle || []).push({});
Who commits to the plan at the end of Iteration Planning?The Solution OwnerThe TeamThe Product OwnerThe Scrum Master
The business must depend on the team for what in order for the business to do any meaningful planning?Team capabilitiesCommitment to the planA cross-functional skill setMeasurements
During PI Planning, who owns the planning of stories into Iterations?System ArchitectScrum MasterProduct ManagementAgile Teams
Each PI Planning meeting evolves over time, and ending PI Planning with a Retrospective will help to do what?Continuously improveLengthen the Architectural RunwayFine tune the Economic FrameworkMeet compliance more rapidly
Which type of enabler does a System Architect review during a System Demo?Enabler FeaturesEnabler CapabilitiesEnabler Portfolio EpicsEnabler Stories
Scrum Masters are effective by using Scrum methods, supporting SAFe principles and practices, and what else?Delivering through Agile practicesWriting stories and enablersManaging Architectural RunwayServing as a customer proxy (adsbygoogle = window.adsbygoogle || []).push({});
Delivering through Agile practices
What is an anti-pattern for the IP Iteration? (Choose two.)To wait for the IP Iteration to fix defectsTo ensure all stories and teams' PI plans are completed prior to the IP IterationTo plan work for the IP Iteration during PI PlanningTo minimize lost capacity when people are on vacation or holidaysTo allow for sufficient capacity in the program roadmap
To ensure all stories and teams' PI plans are completed prior to the IP IterationTo plan work for the IP Iteration during PI Planning ??
Features lend themselves to the Lean UX process model. They include a description, a benefit hypothesis, and what else?Content readinessScope and contextAcceptance criteriaIP outcomes
What is the main reason why some teams never reach stage 4 (Performing) in the stages of high performing teams?Because leadership is spontaneousBecause no one guides themBecause there is too much conflictBecause the team is not structured correctly
Because leadership is spontaneous ??
There are two primary aspects of a Lean-Agile mindset -- Lean Thinking and what else?Lean SystemsEmbracing AgilitySystems EngineeringFeature Enablement
Which statement is true about Scrum?It is a software technical practiceIt is based on empirical process control theoryIt is an ideal method for static design requirementsIt is a Lean System Engineering technique
It is a Lean System Engineering technique??
What is the purpose of the Plan-Do-Check-Adjust cycle?To provide a regular, predictable development cadence to produce an increment of valueTo give the Agile Release Train team members a process tool to keep the train on the tracksTo create a continuous flow of work to support the delivery pipelineTo allow the team to perform some final backlog refinement for upcoming Iteration Planning
To provide a regular, predictable development cadence to produce an increment of value
The skills of a good SAFe Scrum Master include which three attributes?Self-organize, self-manage, self-directRepresent, direct, governShare, pair, communicateCommunicate, coordinate, cooperate
Communicate, coordinate, cooperate??
An effective SAFe Scrum Master is a team-based servant leader who helps the team do what?Understand and operate within Lean BudgetsEmbrace relentless improvement through Iteration RetrospectivesDevelop better and more specialized skill setsManage the team's own backlog
Embrace relentless improvement through Iteration Retrospectives |