Scrum Flashcards

1
Q

Scrum

A

a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

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

Scrum Team

A

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.

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

Product Owner

A
  • the primary interface between the team and the Business Owner
  • responsible for maintaining and prioritizing the backlog of tasks to be performed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Scrum Master

A
  • to keep the development team productive

- to ensure that their issues, concerns, and roadblocks are taken into consideration by the Product Owner

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

Development Team

A
  • responsible for delivering the product
  • typically cross-functional
  • self-organizing and defines the rules dictating how they work together
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Customer

A

the group or organization who is sponsoring the project and who will ultimately use it.

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

Business Owner

A

represents the customer and is the source for application requirements

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

Product Backlog

A
  • a list of the requirements the application must meet

- requirements are expressed as user stories of the format

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

user stories (stories)

A
  • short statements identifying the type of person, the functionality they need to perform in their own terms, and the value they expect to achieve from it
  • “As a … I want to … So I can …”
  • Sagas, Epics, & User Stories
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

main processes in Scrum

A

the sprint, sprint planning, the daily Scrum meeting, the sprint review, and the sprint retrospective

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

Sprints

A
  • application development cycles

- A fixed number of user stores are assigned to each sprint

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

Sprint Planning

A
  • at the start of each sprint

-

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

Daily Scrum Meeting

A
  • the goal is to make sure that there is transparency across the team to both successes and roadblocks.
  • Not intended to solve issues or problems.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Sprint Review

A
  • to demonstrate the working product to the customer

- all hands meeting

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

Sprint Retrospective

A

is conducted by and for the Scrum Team to promote continuous improvement.

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

story points

A

a measure of relative effort or difficulty required to complete a given story

17
Q

Burn-Down Chart

A

graphical view of the number of stories in the backlog that have been completed against the total number remaining across sprints

18
Q

velocity

A

a measure of average rate that stories are completed across sprints

19
Q

Product Backlog Refinement

A
  • the activities of adding detail, estimates, and order to items in the Product Backlog
  • also known as just “Refinement” or “Backlog Grooming”
20
Q

epic (Jira)

A
  • a large body of work that can be broken into many smaller pieces of work - stories
  • an abstract view of what we are trying to achieve
21
Q

story (Jira)

A
  • aka user stories
  • the written requirements from the end-user perspective and smaller pieces of work within an Epic
  • what is required to achieve the Epic
  • none technical
22
Q

task (Jira)

A
  • define all the related work that has to be done to complete the story
  • technical