Scrum Test

Question 1

What are the values of Scrum?

Answer 1

commitment
courage
focus
openness
respect

Question 2

What are the 3 pillars of Scrum?

Answer 2

• transparency
• inspection
• adaptation

Question 3

When doe the new sprint start?

Answer 3

A new Sprint starts immediately after the conclusion of the previous sprint.
Each Sprint typically begins with Sprint Planning and ends with Sprint Review & Sprint Retrospective.

Question 4

Who does the sprint planning?

How long is the sprint planning?

Answer 4

The entire Scrum team.

8 hours for a month-long sprint, shorter timeboxes for shorter sprints.

Question 5

Who does the daily scrum?

Answer 5

The Devs.

If PO or Scrum master are working on items, they can participate as Developers (source: Scrum Alliance)

Question 6

Who does the sprint review?

Answer 6

The entire Scrum Team + stakeholders

Max. of 4 hours

Question 7

What are the three accountabilities/ roles in Scrum?

Answer 7

Devs, Product Owner, Scrum Master

Question 8

What are the scrum artifacts?

Answer 8

Scrum artifacts help manage the work. They are:

Product Backlog
Sprint Backlog
Increment

Question 9

What are the Scrum commitments?

Answer 9

Each artifact has an associated commitment that ensures quality and keeps the team focused on delivering value to its users.

• Definition of Done
• Sprint Goal
• Product goal

Question 10

When does refinement happen?

Answer 10

Some teams prefer a recurring meeting, usually done once per sprint or per week; other teams find making refinements continuously as needed is sufficient.

Question 11

What are the 4 pillars in the agile manifesto?

Answer 11

1. Individuals and interactions over processes and tools
2. Working [products] over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

That is, while there is value in the items on the right,
we value the items on the left more.

Question 12

What is “empirical process control”?

Answer 12

Empirical process control is a core Scrum principle, and distinguishes it from other agile frameworks. The Scrum Guide puts it well: Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.

The 3 main aspects are:

• transparency
• inspection
• adaption

Question 13

What does the scrum value “commitment” mean?

Answer 13

Commitment Allows Scrum Teams to Be Agile
The scrum value of commitment is essential for building an agile culture. Scrum teams work together as a unit. This means that scrum and agile teams trust each other to follow through on what they say they are going to do. When team members aren’t sure how work is going, they ask. Agile teams only agree to take on tasks they believe they can complete, so they are careful not to overcommit.

Question 14

What does the scrum value “courage” mean?

Answer 14

Courage Allows Scrum Teams to Be Agile
The Scrum value of courage is critical to an agile team’s success. Scrum teams must feel safe enough to say no, to ask for help, and to try new things. Agile teams must be brave enough to question the status quo when it hampers their ability to succeed.

Question 15

What does the scrum value “focus” mean?

Answer 15

Focus Allows Scrum Teams to Be Agile
The scrum value of focus is one of the best skills scrum teams can develop. Focus means that whatever scrum teams start they finish–so agile teams are relentless about limiting the amount of work in process (limit WIP).

Question 16

What does the scrum value “openness” mean?

Answer 16

Scrum teams consistently seek out new ideas and opportunities to learn. Agile teams are also honest when they need help.

Question 17

What does the srcum value “respect” mean?

Answer 17

Scrum team members demonstrate respect to one another, to the product owner, to stakeholders, and to the Scrum Master. Agile teams know that their strength lies in how well they collaborate and that everyone has a distinct contribution to make toward completing the work of the sprint. They respect each other’s ideas, give each other permission to have a bad day once in a while, and recognize each other’s accomplishments.

Question 18

What is a sprint?

Answer 18

(scrum alliance)
Scrum teams work in short timeframes called sprints. Sprints can be as short as one week or as long as one month. Sprints happen one right after the other, with no breaks, to maintain a steady project cadence.

Question 19

What Happens in Sprint Planning?

Answer 19

During sprint planning, the entire scrum team collaborates and discusses the desired high-priority work for the sprint and defines the sprint goal. The scrum master’s role is primarily to facilitate the meeting. The product owner describes the product goal and also answers questions from the development team about execution and acceptance criteria/criteria of satisfaction. The developers have the final say in how much of the high-priority work it can accomplish during the sprint.

Question 20

How Long Should Sprint Planning Last?

Answer 20

Sprint planning is limited to a maximum of eight hours.

The general rule of thumb is to allow two hours of sprint planning for every one week of sprint length. That means teams should timebox sprint planning to four hours for a two-week sprint and eight hours for a one-month sprint.

Question 21

What Happens in a Sprint Review?

Answer 21

Sprint reviews focus on the product being developed, specifically on the potentially shippable product increment created during the sprint. During a sprint review, the scrum team invites stakeholders to discuss what was completed during the sprint. They adapt the product backlog as needed based on this feedback. The product owner has the option to release any of the completed functionality.

Though a demo might be part of this meeting, the primary purpose of the sprint review is the inspect and adapt capability provided by the discussion.

Question 22

Who Attends a Sprint Review?

Answer 22

The entire scrum team attends the sprint review. The team invites users, customers, stakeholders, senior managers, and affected departments (e.g., marketing, customer support) to attend and give feedback. Scrum teams are encouraged to invite as many people as the room can hold–diverse feedback is essential for creating excellent products.

Question 23

The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.