Scrum Flashcards

1
Q

What is the most important aspect of Scrum?

A

Time (schedule-oriented)

-Fixed schedule with adjustable scope

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

What is success at Scrum?

A

Customer satisfaction = Success = Quality = Features delivered

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

Why is Scrum a Lightweight Process Framework?

A

A process framework is a standard that must be followed consistently and lightweight means that the process is kept as small as possible to maximize the amount of productive time available.

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

What is the planning logic of Scrum?

A

Planning and estimative the period of time that is closer to us is easier and simpler that the farther.

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

Type of projects Scrum is optimized for

A

Needs change quickly (fluid scope)
Plenty of implementation can be done quickly
Success measured by customer satisfaction with
-responsiveness (burn-down priorities)
-turnaround time (feature delivery)

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

Benefits for Project Managers of Scrum

A

Planning and tracking are easier and more concrete

  • Distribute the responsibility of planning
  • Awareness about the state of the project to address issues quickly

Less experience is needed

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

What are the meetings of Scrum?

A

Sprint Planning

Daily Scrum

Sprint Review

Sprint Retrospective

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

What are the roles of Scrum?

A

Scrum Master

Product Owner

Development Team

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

Scrum concepts

A

Story

  • Identify the functions needed
  • Products requirements

Sprints
-Time period to identify the activities, without thinking too much on the effort needed

Self-organization

  • Few people, easily organize
  • No task delegation
  • Rely on people, not process

Shipped!
-Deliver only stories that are completed

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

What are Scrum Stories?

A

Product requirements in a short narrative description

-Common format

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

What are the Scrum Stories types?

A

User Story

  • User-facing functional requirement
  • Product Owner responsibility
  • Small business cases, specific, very small detail

Technical Story

  • Functionalities supporting the user-facing features in User Stories
  • Development team responsibility

Defect

  • Bug report
  • Product Owner monitor
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a Sprint in Scrum?

A

Fixed period of time, cycle
2-4 weeks
Small teams (3-7)
-If needed, break into more teams with 1 SM and 1 PO

Scope of the sprint is fixed, once started, no change requests allowed!

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

What is the Scrum Master role?

A

Ensure the process run smoothly

Remove obstacles that impact productivity

Teach and give info for the PO

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

What is the Product Owner role?

A

Represents the customer

Link between team and client

Responsible for Stories and priorities

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

Planning on Scrum

A

Plan based on the value to the project per sprint

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

Scrum Stages

A
Vision
Product Roadmap
Release Planning
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
17
Q

What is the Vision Stage in Scrum and its steps?

A

Most important phase
Understand the why/reason behind a project and link with organization’s strategy

Develop product objective
Create and validade vision statement
-From understanding customer and client needs
-Align everyone, even small teams can have different interpretations in mind

18
Q

What is a Vision Statement? Templates?

A

Communicate exact information related to the project
-It can be done to every MVP inside the project

Elevator Statement
Product Envision Box

19
Q

How to create a Product Roadmap?

A

Identify product requirements

  • Themes
  • Features
  • Epic User Stories
  • User Stories
  • Tasks

Organize in logical groups

Estimate effort and priority level

  • Effort is difficulty, not hours
  • Priority, how beneficial for the product
  • Many methods, matter of preference

Envision high-level time frames

20
Q

How to estimate effort and priority level?

A

Use Fibonacci sequence for effort and value
-Priority = Value / Effort

Use any scale, e.g., shirt size

Use a scale for effort and another for priority

Use MS.CoW for priority
-Must, Should, Could, Won’t

21
Q

What characterizes a release?

A

Minimal marketable features for your customer

22
Q

Sprint Planning Meeting goal

A

Select the user stories to be developed in this sprint
Breakdown into tasks
Self-organize tasks

First sprint is an experiment to be able to understand if what was planned makes sense or not and what to do about it

23
Q

Daily Scrum questions

A

Yesterday I completed
Today I’m going to take on
My impediments are

Active listening to others

30s for each question

24
Q

Goal of Sprint Review

A

Check if and show WHAT was planned was done

1h / sprint week

25
Q

Goal of Sprint Retrospective

A

Check the HOW

What went well?
What would we like to change?
How can we implement that change?