Scrum Glossary

Question 1

Sprint

Answer 1

Fixed length events of one month or less to create consistency. A new sprint starts immediately after the completion of a previous sprint.

Purpose: Produce a valuable and useful increment of a working product

Sprints are the heartbeat of Scrum, where ideas are turned into value.

Question 2

Stakeholder

Answer 2

Individual group, or organization who may affect, be or be affected by a decision, activity, or outcome of a project. Is represented by the PO and actively engaging with the Scrum Team

Person(s) external to the Scrum Team with specific interest in and knowledge of a product that is required for incremental discovery

EXs of stakeholders: CEO, Board of Directors

Question 3

Impediment/Blocker

Answer 3

Something that will slow down the delivery process of the team or not allowing them to progress. This is something the team may not be able to solve on their own

Question 4

Tasking

Answer 4

Identifying the items that need to be completed to have the successful completion of a user story

Question 5

Quality

Answer 5

The level of performance needed for the project

Question 6

Scope

Answer 6

The tasks required to complete the project or what need to be built

Work done to reach the goal and the amount of work. Is flexible and can be modified during the sprint

Question 7

Cost

Answer 7

The cost of the project or project’s budget, consists of all the financial resources needed to complete the project on on time, in its predetermined scope.

Question 8

Product Backlog Refinement

Answer 8

Is the act of breaking down and further defining the Product Backlog items into smaller items, typically occurs before Sprint Planning

On going activity to add details such as description, order, and size

Ensures the development team understands the items in the P.B to the level needed

Question 9

Acceptance Criteria

Answer 9

Conditions of satisfaction

Things to look for to know when the story is done. Story is incomplete without this and needs to be testable

EX: Acceptance Criteria
User wants to be able to add items to a shopping cart

Question 10

Kanban

Answer 10

A system that is a workflow management structure that encourages visibility, transparency, and accountability across teams

Question 11

Scrum

Answer 11

Comes from the Agile methodology. It is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions to complex problems.

Best used on software development projects. Used to facilitate all 5 scrum events and principles for a software development team

Question 12

Product Backlog

Answer 12

[ARTIFIACT] PO is responsible for managing this, as it is a prioritized or ordered list of work for the development team, never complete and always worked on

Includes features that the product should have, everything that is needed of the product; description, order, size

No backlog NO work for us a Scrum Masters

Contains undone things related to the product, almost like a to-do list. Needs to be ordered din ways to move towards the goal

PO is responsible for define the object, devs are responsible for sizing and estimation

Product goal is contained here

Question 13

Increment

Answer 13

[ARTIFACT] A new version of the usable product and can be released anytime during the sprint and is born when a product backlog item meets the D.OD

Solid stepping stone toward the Product Goal

Multiple Increments may be created within a Sprint

Should be usable and releasable at the end of every sprint but doesn’t have to be released. Needs to be usable without testable work

Question 14

Commitments Contained In an Artifact

Answer 14

Product Goal is contained in the Product Backlog

Sprint Goal is contained in the Sprint Backlog

Definition Of Done is contained in the Increment

Question 15

Definition Of Done

Answer 15

[COMMITMENT] Set of criterias that must be met before a story can become an increment or said to be done or meets the quality measured required for the product

Provides everyone a shared understanding of what work was completed as part of the increment

If a Product Backlog doesn’t meet the D.OD, it cannot be released or even presented at the review

All stories must meet this requirement

Question 16

Product Goal

Answer 16

[COMMITMENT] The future state of the product which can serve as a target for the Scrum Team to plan against

This is the long term objective for the Scrum Team

They must fulfill or abandon one objective before taking on the next

Contained in the Product Backlog(Artifact)

Question 17

Sprint Goal

Answer 17

[COMMITMENT] The single objective for the Sprint, often a business problem that is addressed

Provides flexibility in terms of the exact work needed to achieve it.

Created by the entire Scrum Team during Sprint Planning and then added to the Sprint Backlog

Specific, measurable, and flexibility

Brings Transparency to the stakeholders

Why are we carrying out the Sprint? How do we reach the Sprint Goal? What metric tells us the goal has been met?

EX of goals: Delivering a feature, addressing a risk, or testing an assumption

Question 18

Transparency

Answer 18

[EMPRICAL SCRUM PILLAR] Designed to provide change. The emergent process and work must be visible to those preforming the work as well as those reviewing the work.

Ensured at anytime, shared understanding of the work

Low transparency can lead to decisions that diminish value and increase risk

Question 19

Daily Scrum

Answer 19

Held everyday of the Sprint with a maximum timebox of 15 minutes.

Lets us know how the team is doing collectively and plan what work will be performed for the next 24 hours and go over how to increase value to the product

Inspect progress towards the Sprint Goal and adapt the Sprint Backlog as needed, adjusting the upcoming planned work

What have you been working on? What will you be working on today? Are there any issues or blockers you may be facing?

Question 20

Scrum Master

Answer 20

Servant leader that helps everyone understand the scrum theory and practice.

Responsible for promoting Scrum and understand Scrum values, theories, practices and roles.

Responsible for removing any impediments the team may face, coaches team in self management and cross functionality

Question 21

Scrum Values

Answer 21

Courage, Openness, Respect, Focus, and Commitment. These give direction to the Scrum Team and supports the organization

Question 22

Product Owner

Answer 22

Owns the vision of the product, says what needs to be developed, represents the needs of the stakeholders and the voice of the customer

Accountable for maximizing the value of the product resulting from the work the Scrum Team

Responsible for the product backlog management and ordering the Product Backlog items to highest priority and ensuring the PB is transparent, visible, and understood.

Has the final say on what criteria needs to be met for the work to be approved and accepted.

Question 23

Inspection

Answer 23

[EMPRICAL SCRUM PILLAR] Designed to provide change and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems

We inspect so we know what is needed

Question 24

Developers

Answer 24

Specialists who have the skills required to develop the product making them cross-functional. They write the code/testing. Developer won’t always mean a programmer.

They are committed to creating any aspect of a usable increment each Sprint, responsible for sizing items in the P.B, creating/adapting their plan toward the Sprint Goal and holding each other accountable

Question 25

INVEST

Answer 25

Independent, Negotiable, Valuable, Estimable, Small, and Testable

Question 26

Sprint Planning

Answer 26

This is the first event of the sprint, and initiates the sprint for the work to be completed. Purpose: create a working, tested and potentially shippable product.

Timeboxed of a maximum of 8 hours.

Everyone on the Scrum team must be in attendance

This is where the velocity and capacity is planned out for the team, and essentially protect the team from over committing

PO proposes the value of product, Devs select items, Devs plan the work for each Product Backlog Item, decompose into smaller units and upcoming capacity(how much can we get done).

Sprint Backlog and Sprint Goal are created at this time and all requirements/user stories must have a value statement and acceptance criteria.

Relative Estimation/Fibonacci Sequence are used for pointing the user stories.

Question 27

Adaption

Answer 27

[EMPIRICAL SCRUM PILLAR] Designed to provide change.

Changes made as soon as possible if any aspects of a process deviate outside acceptance limits or if the resulting product tis unacceptable, the process being applied on the materials being produced must be adjusted.

Adjustments must be made as soon as possible to minimize further deviation or drift.