The Daily Stand-Up for Scrum Masters

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the entire team is driving to the same goal and working together towards the successfully completing the sprint. It is a short meeting, where those involved in the project interact and keep abreast of any changes that might have happened the previous day, and highlight any impediments that may be affecting the progress of the team. The forcing function of everyone having to stand for it also ensures that is it kept short and that people are physically more engaged and present. It’s a time each day for the team to come together and stay agile.

What is a Daily Scrum?

The Daily Scrum is a daily meeting where the team communicates their current work and highlights any impediments. This raises any issues with the Scrum Master who can then look to quickly resolve them to enable the development team to continue progressing with their work. The only people that should be speaking at this meeting are those that are committed to the sprint. The  time-boxed 15 min meeting requires that each member communicates to their team members three pieces of information:

● What did I do yesterday?
● What do I plan to do today?
● What, if anything, is blocking or impeding my work?

The daily scrum is attended be the developers, designers, testers, and other active development team members, the Scrum Master and, depending on the situation, the product owner. This is not a report to higher-ups regarding the project status but is a daily commitment to the team of the work that was completed and what you will get done to make sure the team succeeds.

59 Seconds Agile - The Daily Stand Up Meeting

59 Seconds Agile – The Daily Stand Up Meeting

What is a Daily Scrum?

If a developer says during the daily scrum that they will finish a database module during that day’s work, then the team will expect to hear that she finished the module at the next daily scrum. It is not a meeting where a manager is taking notes regarding who is behind and who is ahead, this is a time to commit to the team the work each team member plans to get done.

If impediments are identified during the daily scrum, a conversation should be held after the meeting to find a resolution. This is where the highest value within the Scrum Master’s role can be observed. The Scrum Master’s goal is to always help the team move forward, they are just as committed to the work laid out in the sprint as everyone else on the team. If missing software, broken equipment, or anything that is impeding the work of a team member it is the Scrum Masters responsibility to make sure this impediment is removed as quickly as possible.

The daily scrum meeting should happen at the same time and place every day so it becomes a regular part of the team’s daily routine. Generally towards the beginning of the day is best but find a time where everyone can commit to being there.

Why is this meeting important to the process?

This meeting is key to the scrum process because it provides a daily source of feedback to the Scrum Team.  They can use this feedback to immediately adapt to change, making the process more efficient. Through daily updates, the team can quickly identify impediments and take action to correct them before they begin to negatively impact the success of the project.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Scrum Masters

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Scrum Master?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Scrum Master?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

The Agile Manifesto For Scrum Masters

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Scrum Masters

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Scrum Masters

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Scrum Masters

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Scrum Masters

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Scrum Masters

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Scrum Masters

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

The Scrum Team Size For Scrum Masters

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Scrum Masters

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Scrum Masters

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Scrum Masters

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Scrum Masters

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Scrum Masters

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Scrum Masters

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Scrum Masters

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Scrum Masters

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Scrum Masters

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Scrum Masters

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting.  This…

Read More

Creating the Deliverables For Scrum Masters

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Scrum Masters

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Scrum Masters

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Scrum Masters

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Scrum Masters

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Scrum Masters

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Scrum Masters

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Scrum Masters

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More


Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Translate »