SAFe 5 Scrum Master Exam Study Guide Questions and Answers Already Passed

SAFe 5 Scrum Master Exam Study Guide Questions and Answers Already Passed Waterfall Development - Too much WIP - Frequent context switching - Increased overhead - Delivery of value at the end Agile Development - Reduced and visualized WIP - Incremental development - Early and continuous value delivery The Agile Manifesto 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan The 3 pillars of Scrum transparency, inspection, and adaptation Scrum values Focus, Courage, Openness, Commitment, Respect PDCA Plan, Do, Check, Adjust -Occurs throughout the entire iteration Iteration a single development cycle where each Agile Team defines, builds, integrates and tests the stories from their Iteration Backlog What should you avoid during iteration process? -avoiding adding scope once the iteration has begun Who creates the team backlog? The agile team Who owns and prioritizes the team backlog? The product owner What does the team backlog represent? Opportunities, not commitments What does the team backlog contain user and enabler stories Incremental development - stories are implemented in vertical slices -enables a short feedback cycle -allows for refinement of understanding of functionality -facilitates more frequent integration of working systems What is one of the most important (1 of 7) SAFe Lean-Agile Principles? - apply cadence, synchronize with cross-domain planning What is an agile team? -a cross-functional, self-organizing entity that can define, build, test, and where applicable deploy increments of value How are agile teams optimized? -for communication and delivery of value Responsible for creating and refining stories and acceptance criteria the agile team Responsible for defining, building, testing and delivering user stories the agile team Responsible for developing and committing to team PI objectives and iteration plans the agile team Coaches the agile team and facilitates team meetings scrum master Removes impediments and protects the team from outside influence scrum master Attends scrum of scum meetings scrum master Creates, prioritizes and accepts stories product owner Owns backlog product owner Acts as the customer product owner Works with product management to plan PI product owner What does the team use for Team Agility? Kanban and scrum Behavior Driven Development (BDD) -a test-first, Agile testing practice that provides Built-In quality that creates a shared understanding of requirements between the business and the agile team Built-In Quality ensures the each solution element, at every increment, meets the appropriate quality standards throughout development Agile team common principles: -deliver working, tested, full-system increments every two weeks -have common iteration lengths and start/end dates -plan their work at periodic, largely face-to-face PI planning events -develop on cadence and release on demand Agile Release Train (ART) -A virtual organization of 5 to 12 teams that plan, commit, develop and deploy together -align teams to a common business and technology mission to deliver a continuous flow of value What are the four ART events? - PI Planning, -ART synce - System Demo - Inspect and Adapt event PI planning event-duration and value 2 days, team commits to a set of objectives to be delivered in the PI (commit to the next 10 weeks) ART sync-duration and value 1 hour, the team on the ART sync regarding the progress of the PI System demo-duration and value 1 hour, deliverables are reviewed with stakeholders who provide feedback (learn what you didn't see) Inspect and Adapt event-duration and value 1/2 day, the ART reviews and improves its process before the next PI Scrum Master Responsibilities -facilitates team events -is a servant leaders -protects the team (scope outside of work) -Assists the PO in preparing and refining the backlog for PI and iteration planning exhibits lean-agile leadership -supports the teams rules -continuously engages in challenging the old noms of development -leads team efforts in relentless improvement -facilitates meetings -supports the product owner -eliminates impediments so that the team can remain focused on the objectives of the Iteration -promotes SAFe quality practices -represents at the Scrum of scrums Release Train Engineer (RTE) -head of all scrum masters -a fervent leader and coach for the Agile Release Train (ART) -communicate with stakeholders, escalate impediments, help manage risk, and drive relentless improvement The Scrum Master in a SAFe Enterprise -works with the RTE to ensure the train meets its overall PI objectives -coordinates with other scrum masters, the system team and shared services in the ART PI planning events -works with the teams throughout each iteration and PI -participates in the scrum of scrums -fosters normalized estimating within the team -helps teams operate under architectural and portfolio gover