Scaled Agile Framework / SAFe Scrum Master Certification Prep (SSM)

3 keys to inspect and adapt are... - answer-the PI system demo quantitative measurement the problem-solving workshop 3 Pillars of Scrum - answer-transparency, inspection, adaptation 4 core values of SAFe - answer-built-in quality, program execution, alignment, transparency 4 program events - answer-PI planning ART sync System Demo Inspect and Adapt event 5 parts of every team increment - answer-plan, build, test, integrate, review 9 SAFe Lean-Agile principles - answer-1. take an economic view 2. apply systems thinking 3. assume variability; preserve options 4. build incrementally with fast, integrated learning cycles 5. base milestones on objective evaluation of working systems 6. visualize and limit WIP, reduce batch sizes, and manage queue lengths 7. apply cadence, synchronize with cross domain planning 8. unlock the intrinsic motivation of knowledge workers 9. decentralize decision making A good scrum coach moves toward - answer-* coaching the team to collaborate * being a facilitator * being invested in the team's overall performance * asking the team for the answer * letting the team find their own way * guiding * focusing on business value delivery * doing the right thing for the business right now * facilitating team problem-solving Adding new team members - answer-moves a team back to the forming stage Agile Release Train - answer-a virtual organization of 5-12 teams (50-125+) that plans, commits, and executes together agile teams are not just committed to the work, they are committed to (3)... - answer-other teams the program the stakeholders agile teams commit to iteration ____ not stories - answer-goals architectural runway - answer-existing code, hardware components, etc., that technically enable near-term business features art sync timebox - answer-1 hour assumptions - answer-many arguments are anchored in unexamined ___. At the conclusion of PI planning teams should have - answer-Velocity (capacity) and load for each iteration draft PI objectives program risks and impediments attendees for inspect and adapt - answer-teams and stakeholders automation - answer-dev ops response to continuous delivery pipeline backlog refinement timebox - answer-1 - 2 hours weekly benefit hypothesis - answer-justifies feature implementation cost and provides business perspective when making scope decisions business owners - answer-key stakeholders on the agile release train BVIR - answer-big visible information radiator CALMR approach to dev ops - answer-Culture Automation Lean flow Measurement Recovery capability - answer-dev ops is a ___ of every agile release train CFD - answer-cumulative flow diagram Common Anti-Patterns for Iteration Planning - answer-* delving too deep into technical discussions * commitment is unrealistic * velocity and load are exactly the same * SM is more focused on technical hat than facilitator hat * team under-commits due to fear of failure * no time reserved for support activities Common Anti-Patterns for PI Planning - answer-* pressure is put on the team to overcommit * team under-commits due to fear of failure * over-planning ahead of time to make it more efficient loses the essence of PI planning * the plan, rather than the alignment, become the goal Common Anti-Patterns for System Demos - answer-* too much time spent preparing the demo * demo is mainly talk/slides as opposed to working software/hardware * meeting doesn't happen if PO is unavailable * PO sees things for the first time in the team demo * System Demo is not doe because the team demo is enough * team members are not invited to the system demo to save time demos that are not interesting/relevant to program level stakeholders Common Anti-Patterns for team breakout #1 - answer-* No plan or partial plan at the end of the timebox. * Too much time is spent analyzing each story * Shared Scrum Masters and Product owners are not available enough *