Understanding Scrum Development Principles

Who decides what kind of software or product is to be built in Scrum?

• Scrum Master

• Product Owner

• Development Team

• Stakeholders

What approach does Scrum follow in software development?

• Waterfall

• Sequential

• Incremental

• Cyclical

What is the name of the prioritised list of features created by the Product Owner?

• Sprint Backlog

• Development List

• Feature List

• Product Backlog

What does the Development Team work on during a Sprint?

• Product Backlog

• Sprint Backlog

• Feature Request

• Feedback List

What is the role of the Scrum Master?

• To build the product

• To facilitate Scrum rituals and support the team

• To prioritise the Product Backlog

• To test the final product

Which of the following is a key event in Scrum where the team reflects on the past Sprint?

• Sprint Planning

• Daily Scrum

• Sprint Review

• Sprint Retrospective

How long is a typical Sprint in Scrum?

• 1 day

• 1 week

• 2-4 weeks

• 6 weeks

Who is responsible for maximising the value of the product resulting from the work of the Development Team?

• Scrum Master

• Product Owner

• Development Team

• Stakeholders

What is the purpose of the Daily Scrum?

• To review the Product Backlog

• To plan the next Sprint

• To synchronise activities and create a plan for the next 24 hours

• To demonstrate the product to stakeholders

Which artefact provides transparency about the work planned for the Sprint?

• Product Backlog

• Sprint Backlog

• Increment

• Burndown Chart