Daily Scrum Recipe

recipe
Published on
5 minute read

The Daily Scrum is an essential event in the Scrum framework. It offers the Developers an opportunity to reflect on their progress, and plan for the next 24 hours. But it’s essential to approach it with the right mindset and intent.

Purpose of the Daily Scrum

The primary objective of the Daily Scrum is not merely to go through a checklist of questions. Instead, it’s to actively manage ongoing work and strategize on how best to achieve the Sprint Goal. This meeting is a platform for Developers to discuss their work, challenges, and any impediments they might be facing. By doing so, they can effectively strategize on their next steps and ensure that they are on the right track.

Beyond the Three Questions

While the three standard questions—What did I do yesterday? What will I do today? Are there any impediments in my way?—provide a structure, they shouldn’t become a monotonous routine. Developers should not feel compelled to answer these questions robotically or feel the unnecessary pressure for everyone to speak. The focus should be on meaningful conversation and collaboration.

Beyond the Three Questions

Rather than discussing every item, the team should concentrate on elements in the Sprint Backlog that require intervention or are at risk. By honing in on these areas, the team can proactively address potential challenges and ensure they remain on course.

Emergent Practices

It’s crucial to understand that there’s no one-size-fits-all approach to the Daily Scrum. What works for one team might not necessarily work for another. Practices should emerge based on the team’s unique needs, challenges, and dynamics. Over time, as the team evolves and matures, so will their practices.

Asking more interesting questions

The Daily Scrum is not just a routine check-in. It’s an opportunity for the team to come together, collaborate, and strategise. By focusing on the right areas and fostering open communication, teams can remain aligned with the Sprint Goal and continue delivering value. Remember, the method in which the team conducts the Daily Scrum can vary, and what’s presented here is just one of many ways!

Daily Scrum Recipe

Overview of Flow for Daily Scrum

This recipe leverages a simple flow and consists of the following:

The Developers review their progress towards the Sprint Goal. They should actively manage the work that is in progress and maintain transparency of the present as reflected in the Sprint Backlog.

The Developers should own this event and facilitate it, although Scrum Masters may certainly facilitate as requested or as needed.

Why recipe?

You follow a recipe a few times to build muscle memory and understand the intended outcomes. Once learned one can tweak or change the recipe to adapt the outcomes to one’s own taste.

Suggested Flow Steps

Part 1: Review the Work in Process [~5 mins]

The Developers should review the work currently underway and identify any problems, issues, or missing information required to get to the Sprint Goal.

Getting to the more interesting questions and enabling us to focus only on the most valuable conversations requires that we maintain transparency of the Sprint Backlog so that we can easily see what is going on. We can then visualise that data in ways that allow us to identify those interesting items.

Facilitation Options

You can use the following visualisations:

Part 2: Create an Actionable Plan for 24h [~10 min]

The outcome of the Daily Scrum should be an increase in the transparency of the work underway, which should be reflected in the Sprint Backlog. What has happened in the last 24 hours that needs to be reflected on the Sprint Backlog, and what is the plan for the next 24 hours? Does the Sprint Backlog still represent the most essential work to get to the Sprint Goal?

We should leave the Daily Scrum with a plan for the next 24 hours!

Facilitation Options

Some Common Anti-patterns

Daily Scrum Recipe

Reference

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Capita Secure Information Solutions Ltd Logo
Jack Links Logo
Teleplan Logo
Alignment Healthcare Logo
Genus Breeding Ltd Logo

CR2

Philips Logo
Sage Logo
ALS Life Sciences Logo
Xceptor - Process and Data Automation Logo
Boeing Logo
Trayport Logo

NIT A/S

Lean SA Logo
Brandes Investment Partners L.P. Logo
Epic Games Logo
Hubtel Ghana Logo
Emerson Process Management Logo
New Hampshire Supreme Court Logo
Washington Department of Enterprise Services Logo
Department of Work and Pensions (UK) Logo
Washington Department of Transport Logo
Royal Air Force Logo
Nottingham County Council Logo
Milliman Logo
Alignment Healthcare Logo
ALS Life Sciences Logo
MacDonald Humfrey (Automation) Ltd. Logo
Lockheed Martin Logo
Capita Secure Information Solutions Ltd Logo