1. Home
  2. Training Library
  3. The Daily Scrum

The Daily Scrum

Developed with
QA

Contents

keyboard_tab
Facilitating Purposeful Agile Meetings
1
Scrum Roles
PREVIEW6m 1s
2
Scrum Events
PREVIEW6m 25s

The course is part of this learning path

play-arrow
Start course
Overview
DifficultyBeginner
Duration19m
Students155
Ratings
5/5
starstarstarstarstar

Description

Course Description

This module looks at the different scrum events and scrum roles, before focusing on best practice for the daily scrum.

Learning Objectives 

The objectives of this course are to provide you with and understanding of: 

  • What the scrum events are 
  • What the roles in scrum are 
  • How to run a daily scrum 
  • Best practice for the daily scrum  

Intended Audience 

This course is aimed at Scrum Masters who want to improve their individual knowledge of facilitating scrum events in service to their Scrum team and their wider organization 

Prerequisites

There are no specific pre-requisites to study this course 

Feedback 

We welcome all feedback and suggestions - please contact us at qa.elearningadmin@qa.com to let us know what you think.

Transcript

The daily scrum is all about transparency in the scrum team and making sure that everyone knows what's happening during the sprint. The daily scrum, sometimes called a stand-up, is a team catch-up. It's time-boxed to 15 minutes, and it's held every day of the sprint. The daily scrum is held at the same time every day to reduce complexity, and so everyone knows that they can't make other commitments unless they'll be towards achieving the sprint goal. The daily scrum should be conducted face-to-face. Now this doesn't mean that everyone has to be in the same room, however. Digital meetings can be conducted. Just make sure that everyone has a webcam. One of the key values of scrum is openness. Ensuring that daily scrums happen face-to-face helps uphold that value. The dev team plans the work for the next day or until the next scrum. The daily scrum helps to optimize the probability that the development team will meet the sprint goal. Seeing what everyone is working on gives visibility to all of the progress on the product increment. The structure of the daily scrum is set by the dev team. Each member of the team typically needs to answer three questions. What did I do yesterday that helped reach the sprint goal? What will I do today to help reach the sprint goal? And is there anything stopping me from helping reach the sprint goal? The team will be able to see what progress is being made towards the sprint via the daily scrum. Understanding what everyone is working on helps provide clarity. The daily scrum should be no longer than 15 minutes. Given that, if there are things that need to be discussed in further detail, the appropriate members of the dev team can communicate within the scrum if they need to talk to one another in more detail. This sort of discussion to discuss, adapt, or replan the sprint normally happens immediately after the daily scrum with the relevant members of the dev team involved. Sometimes, others outside of the scrum team sit in on the daily scrum. The scrum master needs to ensure that they don't interrupt the scrum. Daily scrums improve communications. They eliminate other meetings, identify impediments to development so they can be removed, and they highlight and promote quick decision making and improve the development team's level of knowledge. This is a key meeting that follows the transparency, inspect and adapt the pillars of empiricism on which scrum is based on, as well as upholding the values of openness.

About the Author
Students2912
Courses36
Learning paths9

Tony has over 20 years’ experience in Business Development, Business Change, Consulting and Project/Programme Management working with public, private and third sector organisations.

He has helped organisations to design and create process and procedures to align ways of working with corporate strategy. A highly motivated and detailed solution provider utilising a wide range of methods and frameworks to provide structure whilst promoting creativity and innovation.

As a confident and self-motivated professional with excellent communication skills Tony is able to bring people together and get them working as a team quickly.

Tony is an Agile and Scrum trainer with a vast knowledge spanning IT Systems, Business Change, Programme and Project Management. With excellent presentation skills and a solid background, he ensures that all clients gain maximum benefit from his training. He has successfully guided those new to the industry through their initial training, helped experienced staff as they progress in their careers and worked at Director level advising on best use and practice, as well as tailoring courses to fulfil the exact needs of clients.