Implementing Scrum in Azure DevOps Review

Workshop Day 1 Quiz

SCRUM Overview

Multiple Choice

What are the three pillars of Scrum?

• Iterations, User Stories, Sprints

• Transparency, Inspection, Adaptation

• Planning, Execution, Review

• Design, Develop, Test

Multiple Choice

Which of these is NOT a Scrum ceremony?

• Sprint Planning

• Daily Scrum

• User Story Mapping

• Sprint Review

Multiple Choice

What is the Definition of Done?

• A set of acceptance criteria

• A list of completed tasks

• A list of product features

• A complete codebase

Multiple Choice

True or False: A Product Backlog Item (PBI) must always be completed within one sprint.

• True

• False

Multiple Choice

Which of the following is NOT a consideration when choosing your Sprint Duration?

• Stakeholder availability

• Complexity of the project

• Team preference

• Lunar cycles

Planning & Managing a Product Backlog

Multiple Choice

What is the primary purpose of a product backlog?

• To store completed work

• To list all the desired features and changes for a product

• • To act as a calendar

• To keep meeting notes

Multiple Choice

What makes a good product backlog?

• Detailed and fixed

• Long and exhaustive

• Dynamic and prioritized

• Static and comprehensive

Multiple Choice

What does velocity measure?

• Speed of coding

• Time spent in meetings

• Amount of work completed in a Sprint

• Number of tasks assigned

Multiple Choice

What is the Portfolio Backlog?

• A backlog for a specific sprint

• A high-level backlog that aligns with organizational objectives

• A list of bugs and issues

• A list of team member tasks

Multiple Choice

Why might tags be useful in a product backlog?

• To color-code items

• To identify the team responsible

• To help in categorizing and filtering items

• To indicate priority

Sprint Planning (Scrum Ceremony)

Multiple Choice

What is the primary outcome of Sprint Planning?

• Assigning tasks to team members

• Creating a list of features for the next product release

• Forming a Sprint Backlog and establishing a Sprint Goal

• Setting up the physical Scrum board

Multiple Choice

What is the 'What' and 'How' of Sprint Planning?

• What will be done this Sprint, and how will it be reviewed?

• What will be done this Sprint, and how will the work get done?

• What is the definition of done, and how will it be met?

• What tasks are important, and how are they prioritized?

Multiple Choice

Why is task assignment during Sprint Planning considered dangerous?

• It reduces team flexibility

• It lengthens the planning meeting

• It is contrary to the Agile Manifesto

• It can demoralize team members

Multiple Choice

What is the Sprint Goal?

• A financial target for the Sprint

• A specific set of features to complete

• An objective to be achieved within the Sprint

• The amount of work assigned to each team member

Multiple Choice

Who primarily drives the Sprint Planning meeting?

• Scrum Master

• Product Owner

• Development Team

• Stakeholders

Daily Scrum (Scrum Ceremony)

Multiple Choice

What is the primary purpose of the Daily Scrum?

• To report to the Product Owner

• To update the Scrum board

• To inspect progress and adapt the plan for the next 24 hours

• To assign new tasks

Multiple Choice

What's a common cause of boredom in Daily Scrums?

• Lack of progress

• Inconsistent attendance

• Going off-topic

• Lengthy meetings

Multiple Choice

How can Azure DevOps assist with the Daily Scrum?

• By automatically updating the Sprint Backlog

• By providing real-time dashboards and metrics

• By setting up meetings

• By writing user stories

Multiple Choice

What is the main benefit of version control's traceability feature in Azure DevOps?

• It provides an extra layer of security

• It allows tracking changes back to their source

• It helps in automating builds

• It simplifies the branching strategy

Multiple Choice

What is an Impediment in Scrum?

• A high-priority task

• A hurdle or obstacle that impacts productivity

• An optional task

• A technical debt

Workshop Day 2 Quiz

Sprint Review and Restrospective (Scrum Ceremony)

Multiple Choice

What is the primary goal of a Sprint Review?

• To demonstrate what was accomplished in the Sprint

• To review the team's performance metrics

• To plan for the next Sprint

• To resolve any conflicts within the team

Multiple Choice

What is the purpose of a Sprint Retrospective?

• To focus on improving team dynamics

• To assess what went well and what needs improvement

• To re-prioritize the backlog

• To celebrate the team's achievements

Multiple Choice

How can Azure DevOps assist during Sprint Review and Sprint Retrospective?

• By sending automated emails to stakeholders

• By providing metrics and dashboards for review

• By managing customer feedback

• By creating PowerPoint presentations

Multiple Choice

What is a danger associated with 'Undone' work at the end of a Sprint?

• Increase in velocity

• Scrum framework collapse

• Accumulation of technical debt

• Better team morale

Multiple Choice

What could be a strategy in Azure DevOps for handling 'Undone' work?

• Delete all 'Undone' tasks

• Move them to the next Sprint automatically

• Re-assess and prioritize 'Undone' tasks in the backlog

• Archive them for future reference

Product Backlog Refinement

Multiple Choice

What is Backlog Refinement?

• Adding more user stories to the backlog

• Grooming and prioritizing the product backlog

• Removing items from the backlog

• Assigning tasks to team members

Multiple Choice

What is one benefit of Backlog Refinement?

• Shorter Sprint Planning meetings

• Faster coding

• Less documentation

• More vacations

Multiple Choice

Why do some consider estimation a waste of time?

• It's always 100% accurate

• It can lead to lengthy discussions with little value

• It replaces the need for a product backlog

• It makes the team work harder

Multiple Choice

What is 'Planning Poker'?

• A game to decide the product owner

• A method for team-based estimation

• A tool for risk assessment

• A technique for sprint planning

Multiple Choice

How can Azure DevOps assist in Backlog Refinement?

• By allowing online Planning Poker

• By auto-generating user stories

• By automatically refining the backlog

• By offering features for backlog organization and prioritization

Multi-Scrum Teams

Multiple Choice

How many Team Projects do you generally need in Azure DevOps for multi-scrum teams?

• One per team

• One per organization

• One per feature

• One per sprint

Multiple Choice

What is the maximum recommended team size in Scrum?

• 5

• 10

• 20

• No Limit

Multiple Choice

What is a drawback of multitasking in Scrum?

• Increased focus

• Lower quality

• Faster delivery

• Greater adaptability

Multiple Choice

According to the Scrum Guide, who is responsible for the product backlog?

• Scrum Master

• Product Owner

• The Development Team

• The Stakeholders

Multiple Choice

What is a common strategy for organizing multiple Scrum teams?

• Each team works in isolation

• Teams are organized around features or components

• Each team has its own Scrum Master, but they never communicate

• Teams are organized based on the seniority of their members

Metrics & Dashboard

Multiple Choice

What is a common myth about metrics?

• They always reflect the truth

• They are only for managers

• They can't be manipulated

• They are universally understood

Multiple Choice

What makes a metric "good"?

• High numbers

• Actionable insights

• Complexity

• Alignment with other metrics

Multiple Choice

Why might a team be cautious about introducing new metrics?

• Fear of accountability

• Metrics are always beneficial

• Possible unintended behavior

• They like the status quo

Multiple Choice

What is "Predicting the Future with Velocity" about?

• Estimating the number of Sprints required to complete the remaining work

• Calculating the speed of code compilation

• Measuring individual performance

• • Quantifying the technical debt

Multiple Choice

How is "Throughput" different from "Velocity"?

• Throughput is about quality, Velocity is about quantity

• Throughput measures items completed irrespective of size, Velocity considers size

• Throughput is for Scrum, Velocity is for Kanban

• Throughput is a measure of individual performance, Velocity is a team metric