Scrum Combined

What are the 3 Empirical Pillars of Scrum?

Transparency, Inspection, Adaptation.

Define Transparency in Scrum.

The process and work must be visible to those doing it and receiving it.

What does Inspection mean in the context of Scrum?

Regularly examining artifacts and progress toward goals to detect problems.

What is Adaptation in the Scrum framework?

Adjusting the process or product when inspection reveals issues.

List the 5 Scrum Values.

Commitment, Focus, Openness, Respect, Courage.

What does Commitment mean for Scrum team members?

Team members commit to goals and to each other.

Explain Focus in Scrum.

Concentrating on Sprint work and team goals.

Define Openness in the context of Scrum values.

Being open about work, challenges, and findings.

What does Respect signify among Scrum team members?

Respecting each other's capabilities and independence.

In Scrum, what does Courage entail?

Doing the right thing and tackling hard problems honestly.

How do Scrum values enable the empirical pillars?

Values like Courage and Openness facilitate Transparency.

Why is Respect important for Inspection in Scrum?

Without Respect, inspection can lead to blame rather than improvement.

What is the role of the empirical pillars in Scrum?

They uphold Scrum's process control theory based on empiricism.

How are the Scrum Values connected to the pillars?

They allow for effective implementation of the pillars in practice.

What is the consequence of lacking Courage and Openness in Scrum?

It leads to a lack of real Transparency.

How does Scrum define trust among team members?

Trust is built through the connection of values and pillars.

What does ‘iteratively’ mean in the context of Scrum?

Delivering value through repeated cycles of development and feedback.

What happens if a team lacks Focus during a Sprint?

The team may struggle to achieve Sprint goals effectively.

Why is Adaptation critical in Scrum?

It ensures that teams can respond to changes and problems quickly.

What is the ultimate goal of the Scrum framework?

To deliver value iteratively while building trust among team members.

How can the Scrum framework achieve improvements over time?

By using the three pillars and five values to guide the process.

MoSCoW Method

A prioritization technique that categorizes items into Must Have, Should Have, Could Have, and Won't Have.

Must Have

Items that are non-negotiable and act as sprint blockers.

Should Have

Important items that are not critical but necessary.

Could Have

Items that are nice to have but not essential.

Won't Have (this time)

Items that are explicitly deferred for future consideration.

WSJF – Weighted Shortest Job First

A prioritization method calculated as Priority = Cost of Delay ÷ Job Duration.

Cost of Delay

The economic impact that results from delaying the delivery of a job.

Job Duration

The time it takes to complete a job or task.

Kano Model

A technique that classifies features by their impact on customer satisfaction.

Basic needs

Features that are expected and do not delight users if present.

Performance needs

Features for which more availability increases user satisfaction.

Delighters

Unexpected features that can pleasantly surprise and wow users.

Value vs. Effort Matrix

A 2x2 grid that helps prioritize tasks based on their value and the effort required.

Quick Wins

Tasks that provide significant value for a low amount of effort.

Story Mapping

A technique that organizes user stories in a horizontal user journey and stacks by priority.

MVP

Minimum Viable Product; the top slice of prioritized user stories in story mapping.

100-Point Method

A prioritization technique where stakeholders distribute 100 points across backlog items.

Cumulative Voting

A method to aggregate stakeholder scores to determine item priority.

RICE Scoring

A scoring system calculated as Score = (Reach × Impact × Confidence) ÷ Effort.

Reach

The number of customers or users impacted by a feature or task.

Impact

The effect that a feature will have on the customer or the business.

Confidence

The degree of certainty about the reach and impact predictions.

Effort

The total work required to implement a feature or task.

Sprint

The core container for all other events; a fixed-length iteration (1–4 weeks) during which the team builds a potentially releasable product increment.

Sprint Planning

The meeting that kicks off each Sprint where the Scrum Team decides what to work on and how, with a maximum time allocation of 8 hours for a 4-week Sprint.

Daily Scrum

A 15-minute daily sync for Developers to inspect progress toward the Sprint Goal and adjust the plan for the next 24 hours.

Sprint Review

Held at the end of the Sprint where the Scrum Team and stakeholders inspect the increment and discuss the completed and incomplete work.

Sprint Retrospective

The final event of the Sprint focused on what went well, what didn't, and what improvements to commit to for the next Sprint.

Backlog Refinement

An ongoing process where the Scrum Team reviews and revises the Product Backlog items to keep it up-to-date and prioritized.

What is a Sprint in Scrum?

A fixed-length iteration (1–4 weeks) during which a potentially releasable product increment is built.

What is the purpose of Sprint Planning?

To decide what to work on and how for the upcoming Sprint.

How long is the Daily Scrum?

15 minutes, regardless of Sprint duration.

Describe the Sprint Review.

A meeting at the end of the Sprint where the Scrum Team and stakeholders review the increment and adapt the Product Backlog if necessary.

What is the focus of the Sprint Retrospective?

The team itself, analyzing what went well, what didn't, and planning for improvements.

What does Backlog Refinement include?

Reviewing and revising Product Backlog items to ensure they are up-to-date and prioritized.

What is the maximum duration for Sprint Planning in a 4-week Sprint?

8 hours.

Can the length of a Sprint change once it starts?

No, the length of a Sprint is fixed once it begins.

Who participates in the Daily Scrum?

Only the Developers, not the whole Scrum Team.

What happens during the Sprint Review?

Inspection of the increment and discussion of completed and incompleted work.

What is the aim of the Sprint Retrospective?

To commit to concrete improvements for the next Sprint.

What is an ongoing process of reviewing and updating the Product Backlog called?

Backlog Refinement.

What do teams ensure during Backlog Refinement?

The backlog is up-to-date and prioritized.

What is the purpose of a 15-minute Daily Scrum?

To synchronize and inspect progress toward the Sprint Goal.

How often does Backlog Refinement occur?

It is an ongoing process.

Sprint

A time-boxed iteration of work lasting a maximum of 4 weeks.

Sprint Planning

A ceremony that occurs once per sprint, with a maximum duration of 8 hours, to define the sprint goal and backlog.

Daily Scrum

A daily meeting lasting up to 15 minutes for the team to inspect and adapt progress.

Sprint Review

A ceremony that happens once per sprint, lasting up to 4 hours, to demo and inspect the increment created during the sprint.

Sprint Retrospective

A ceremony held once per sprint, with a maximum duration of 3 hours, to inspect the team and process, and define improvements.

Time-boxed

A fixed duration within which a specific ceremony or event must be completed.

Cadence in Scrum

The frequency at which Scrum ceremonies occur, including daily and per-sprint events.

Inspect and Adapt

The core principle of Agile Scrum where teams regularly assess their progress and processes to improve.

Stakeholders

Individuals who are involved in or affected by the project and are engaged during the Sprint Review.

Team Commitment

The agreement among team members to attend and actively participate in Scrum ceremonies.

Increment

The sum of all the completed product backlog items during the sprint and previous sprints.

Per-sprint Total

The cumulative maximum hours allocated for all ceremonies within a single sprint, totaling up to 22 hours.

Sprints vs Ceremonies

Sprints are iterations of work, while ceremonies are structured events that occur within a sprint.

Scrum Master

The role responsible for facilitating Scrum ceremonies and ensuring adherence to Scrum practices.

Product Backlog

An ordered list of items that need to be completed for the project, guiding the work during sprints.

Sprint Goal

The single objective for the sprint that the team aims to achieve during that sprint.

Max Occurrences of Daily Scrum

Up to 28 occurrences in a 4-week sprint, each lasting 15 minutes.

Timebox Summary

A summary of the maximum allowed duration for each ceremony performed during a sprint.

Order of Scrum Ceremonies

The fixed sequence in which Scrum ceremonies occur, with Sprint Review preceding the Sprint Retrospective.

PSM I Prep

Preparation for the Professional Scrum Master I certification, focusing on understanding Scrum principles and practices.

Order Matters on Exam

The importance of remembering the correct sequence of Scrum ceremonies for exam purposes.

Scrum

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

Scrum Master

The individual responsible for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice.

Scrum Team

The fundamental unit of Scrum, composed of a Scrum Master, a Product Owner, and Developers.

Product Owner

The individual accountable for maximizing the value of the product resulting from the work of the Scrum Team.

Developers

Members of the Scrum Team committed to creating any aspect of a usable Increment each Sprint.

Transparency

The state of work and process visibility necessary for effective inspection and adaptation.

Inspection

The act of examining the Scrum artifacts and progress towards goals to detect undesired variances or problems.

Adaptation

The process of adjusting any aspects of a process to minimize deviation from acceptable limits as soon as possible.

Sprint

A fixed-length event of one month or less during which a selection of work is turned into an Increment of value.

Sprint Planning

The event that initiates the Sprint by laying out the work to be performed.

Daily Scrum

A 15-minute time-boxed event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

Sprint Review

An event at the end of the Sprint to inspect the outcome and determine any future adaptations.

Sprint Retrospective

An event where the Scrum Team reflects on the past Sprint to identify improvements in quality and effectiveness.

Product Backlog

An emergent, ordered list of what is needed to improve the product, serving as the single source of work for the Scrum Team.