Requirements in Scrum Flashcards

1
Q

What is the suggested team size for Scrum?

A

10 or fewer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

In Scrum, __________ technique is not specified. Rather, it focuses on what?

A

development

Focuses on how team members should function in order to work flexibly in a constantly changing environment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the 3 roles in scrum?

A

Product owner
Scrum master
Developers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the definition of done?

A

A formal description of the state of the increment when it meets the quality measures required fro the product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is an increment?

A

A concrete stepping stone toward the product goal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the relationships between increments, sprint backlogs, and product backlogs?

A

The product backlogs contains items that need to be done. The sprint backlog is a subset of the product backlog. An increment is any item in the product backlog that meets the definition of done

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

When can increments be presented?

A

At the Sprint Review or any time prior to the end of sprint (basically any time)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What do developers do?

A

They create any aspect of a usable increment in each sprint. The also:

  • Create a sprint backlog/plan
  • Adhere to the DoD
  • Adapt their plan each day toward the sprint goal
  • Hold each other accountable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is a product backlog?

A

An evolving, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is a product goal?

A

Describes a future state of the product which can serve as a target for the Scrum Team to plan against

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What do the product owners do?

A
  • Represent users and communicates with them for clarifications
  • Create, clarify, accepts/rejects, and orders the items in the product backlog
  • Develops the Product Goal
  • Can cancel the sprint if it’s going badly
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What does the Scrum Master do?

A
  • Makes sure Scrum and Agile is being followed
  • Helps everyone understand Scrum theory and practice
  • Serves the scrum team (coaching in self-management, help team create high value increments, remove impediments, makes sure all scrum events take place)
  • Serves the product owner (Help find techniques for effective product backlog management, Establish empirical product planning, facilitate stakeholder collaboration)
  • Serves the org (Coach in scrum adoption, plan scrum implementations, help employees and stakeholders understand empirical work approach)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is the Scrum Master not?

A

Project manager

Decision maker

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the 5 scrum events?

A
Sprint
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is the pregame phase? (No longer defined in 202 Scrum Guide)

A

Planning (create product backlog and prioritise/estimate) Estimates are facts at the time and will change. Could use planning poker
Create the architecture (with maybe a design review meeting)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a sprint?

A

A fixed length event of one month or less to create consistency
All 4 events happen within a sprint

17
Q

What can occur during the sprint relating to product backlog?

A

It can be refined as needed and the scope may be clarified and renegotiated with the product owner as more is learned

18
Q

What is sprint planning?

A

A typically 1 day event with 2 parts: Scope and Plan

19
Q

What happens in the Scope part of sprint planning?

A
  • Define the Sprint Goal
  • The team picks up enough items from the product backlog to be done in 1 sprint -> Sprint backlog (These are items that can be finished in one sprint ONLY)
  • DoD is written for Sprint Backlog items
20
Q

What happens in the Plan part of sprint planning?

A
  • Determine details of how items will be worked on
  • Work dependency is determined here
  • Each sprint backlog item is broken down into tasks and put into a to do coloumn
  • These tasks should not take longer than a day
21
Q

What is Product Backlog Refinement?

A

The act of breaking down and further refining product backlog items into smaller more precise items

22
Q

What is the daily scrum. What happens in it?

A

A 15 minute max meeting to inspect progress toward the sprint goal and adapt the sprint backlog as necessary

It should be held at the same place and time every day

Not the only time devs are allowed to adjust their plan

It should focus on progress towad the sprint goal and produce an actionable plan for the next day of work. You should go through backlog items, not people

23
Q

How is project tracking performed in Scrum?

A

The team assigns themselves tasks and can adjust the way work is done as they discover new facts during the sprint
The product owner must make sure that everyone knows about the changes, however
The daily scrum is an opportunity for the team to continuously plan and manage change

24
Q

What is the Sprint review?

A

A session of maximum 4 hours for a 1 month sprint, where the team presents the results of their work to key stakeholders
It is reviewed, and then the attendees collaborate on what to do next

25
Q

What is the Sprint Retrospective?

A

A session of max 3 hours per 1 month, where the main focus is to increase the quality and effectiveness of the process

26
Q

Review the Scrum cycle diagram

A

Slide 3-19

Vision -> Product Backlog -> Sprint Backlog -> Sprint (with daily scrum) -> Sprint Review -> Update Product Backlog

27
Q

What is a burn down chart?

A

It shows the amount of work remaining across the days. In early sprint, this can increase as new facts are uncovered, but it rapidly declines as work gets underway

28
Q

What are some tips when doing Scrum?

A

Large team sizes dont work well
Adjust sprint duration according to feature complexity and scale
Sprints run smoother if initial research, planning, and overall design are done upfront before starting sprints
Dedicated testers in sprints are very important

29
Q

What are benefits of scrum?

A
  • No heavy process
  • More work done
  • No dumb meetings
  • Team bonding
  • Sense of urgency
  • Early stakeholder feedback
30
Q

Describe how each of the following requirement concepts are met in Scrum:

  • Requirements elicitation
  • Requirements analysis
  • Requirements specification
  • Requirements validation
  • Requirements change management
  • Architecture
A
  • Requirements elicitation
    Product owner speaks with stakeholders to get requirements
  • Requirements analysis
    Prioritise product backlog
    Estimate Prioritise product backlog
    Tasks are estimated during Sprint Planning by team
  • Requirements specification
    Product Backlog
    Sprint Backlog, broken down into different tasks
  • Requirements validation
    DoD
    Sprint Review
    Daily Scrum to understand problems
  • Requirements change management
    Daily Scrum
    Sprint Review
    Project Tracking during the day
  • Architecture
    Create architecture based on the product backlog (pre-game phase)