A representative framework of agile development. With three roles, the Product Owner, the Scrum Master and the Developers, and the events held within Sprints of a fixed length of one month or less (Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective), a working product is built a little at a time.
Japanese name: スクラム
Scrum appears in 2 practice questions across 1 topic, including Software Development and Project Management.
Answer: B. Product Owner
A Scrum Team consists of three roles: the Product Owner, the Scrum Master and the Developers. The Product Owner manages the Product Backlog, the list of what should be built, decides which items are built first, and is accountable for maximizing the value of the product. The Scrum Master spreads the Scrum way of working through the team and organization and helps remove impediments. The Developers are the people who create a working Increment in each Sprint.
Answer: A. Sprint Review
In the Sprint Review, the outcome of the Sprint is inspected together with stakeholders, and what to do next is discussed in light of changes in the market and requirements. The Sprint Retrospective, held afterwards, is different in that it improves how the team works, including people, processes and tools, rather than the product. The Daily Scrum is a short meeting of 15 minutes or less held every day by the Developers to inspect progress toward the Sprint Goal and adjust the plan for the day. Sprints repeat with a fixed length of one month or less.
A Scrum Team consists of three roles: the Product Owner, the Scrum Master and the Developers.
In Scrum, which role is accountable for the content and ord…The Daily Scrum is a short meeting of 15 minutes or less held every day by the Developers to inspect progress toward the Sprint Goal and adjust the plan for the day.
In Scrum, which event takes place at the end of a Sprint to…As an Amazon Associate I earn from qualifying purchases.
Agile development Black-box testing Boundary value analysis Branch coverage CI/CD (continuous integration and continuous delivery) Critical path method (CPM) Earned value management (EVM) Equivalence partitioning SLA (service level agreement) Test-driven development (TDD)