Agile Scrum Master Certification (Answered) Verified Solution

Agile Scrum Master Certification (Answered) Verified Solution Manifesto for Agile Software Development // individuals and interactions ———————- Over processes and tools Manifesto for Agile Software Development // contract negotiation Customer collaboration Over ————— Manifesto for Agile Software Development // comprehensive documentation Working software Over —————————- Manifesto for Agile Software Development responding to change ——— Over following a plan Our highest —- is to satisfy the —- through early and ——- delivery of valuable software Priority, customer, continuous // principles Welcome ———- requirements, even ——— In development. Agile processes harness ———- For the customers's competitive advantage. Changing, late, change // principles Deliver ———- software frequently, from a ——- weeks to a couple ———-, with a preference for the shorter timescale Working, couple of, months // principles Business people and ——— must work ——— daily throughout the ————. Developers, work, project // principles Build projects around ——- individuals. ——— the environment and ——- they need, and trust them to get the job done. Motivated, give, support // principles The most ———- and ———— method of conveying information to and within a development team is ————— conversation. Efficient, effective, face-to-face —————- is the primary measure of progress. Working software // principles Agile processes promote ———- development. The ————, developers, and users should be able to maintain a constant pace ———. Sustainable, sponsors, indefinitely // principles Continuous attention to technical ———— and good design enhances ————-. Excellence, agility // principles Simplicity — the ——— of maximizing the ———- of work not done — is ————. Art, amount, essential // principles The best ————, ————, and ————-, emerge from self-organizing teams. Architectures, requirements, designs Iteration Single development cycle where each Agile team defines, builds, integrates and tests the stories from their iteration backlog Program Increment (PI) Timebox in which an agile release train (ART) delivers incremental value In the form of working, tested software and systems. Typically 8-12 weeks long Acceptance Criteria Formalized list of requirements that enaure that all user stories are completed and all scenarios are taken Into account. Acceptance criteria specify conditions in which a user story is fulfilled Waterfall Model You will context switch // increased overhead // delivery of value is at the end Agile Model You do not context switch which leads to more progress // reduce and visualize WIP // incremental development // increased value delivery What are the three pillars of scrum? The process // the workflow // progress report What are the 5 scrum values Courage // commitment // focus // respect // openness Scrum Guide Sprint planning // sprint review // sprint retrospective // sprint Goals // sprint backlog // daily scrum // increment // the scrum team SAFe Iteration planning // iteration review // iteration retrospective // iteration Goals // iteration backlog // daily stand-up (DSU) // team increment // Agile team cycle of an iteration Plan-do-check-adjust Avoid adding ——- once the iteration has begun Scope What does the teams backlog do Organizes the team's work The team's backlog is: Created by the Agile team // owned and prioritized By the PO // represents opportunities, not commitments // contains user and enabler stories Inspect & Adapt (I&A) Iteration Execution Iteration Goals Iteration Planning Iteration Retrospective Iteration Review SAFE SAFE for Lean Enterprises is a knowledge base of proven, integrated principles, practices, and competencies for Lean, Agile, and DevOps SAFE Lean-Agile principles 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