Scrum Daily Standup Meeting(s)

This daily standup meeting has various names…

  • Standup meeting 
  • Daily Standup
  • Scrum Meeting
  • Daily

 … but its reason-for-being is for the development team to collaborate, keep up to date on progress towards the spring goal and identify any impediments to the upcoming days work. It can be facilitated by a Scrum Master, or a mature team may run it themselves.

See what has a to say about them


According to the Scrum Alliance

It is…

Timeboxed to 15 minutes.




A fundamental Scrum event

It is not…

 A status update.

For problem solving → these can take place immediately after with the necessary team members.

Run a Successful Daily Standup Meeting

  • Round Robin – Go to each person in sequence for their update.
  • Walking the (kanban) board and the progress.

Set a environment for success

Psychologically safe environment – free to ask question and make mistakes, without retribution. Value everybody’s opinion.

Its the team’s duty is to flag any blockers.

Change how you facilitate if things change (new members etc.) – remember the meeting Purpose. 

Fixed Agenda Daily Standup Questions

  1. What did you achieve yesterday?
  2. What are you doing today, aiming to achieve?
  3. Are there any blockers facing you today?

Tips for a Great Daily Standup Meeting

  1. Fix the time and location.
  2. Start on time.
  3. Avoid disruptions. Late comers need to catch up.
  4. Stick to the agenda (avoid small talk).
  5. Be VERY attentive.
  6. Use a parking lot → record the issues to be discussed after.
  7. Set Ground Rules (Establish norms, with the teams input):
  • Limit time for each person. The person ‘on the floor’ holds a ball or something (one person reporting at a time).
  • Electronics (phones) on exception.
  • Update are directed towards the team and the board, not the facilitator.
    • Appropriate level of detail.
    • Move / amend / add tasks on the board, add comments, add estimates/dates.
  • Decide on a specific mini celebration for tasks moved to done.
  • No sitting.
  • No Side conversations.
  • Sponsor (only an observer) and cannot ask for updates.

Any impediments  / dependencies?

Question for the meeting facilitator at the end of each update.

Anyone need to get together to do some peer programming?

Question for the meeting facilitator at the end of the meeting.

Sample Agenda for a Scrum Daily Standup

  1. Check if participants are there. If enough are there…start. If not, address this immediately.
  2. Thank you for joining
  3. This is Day X of the 14 day sprint
  4. Go over dashboard
  5. Go to each developer and tester
  6. Encourage my team to continually add comments to any upcoming story.
  7. Any open questions.

Useful Videos on Daily Standup Meetings

Links: blogs, videos, podast, books +

Here we share the online resources we found most useful and in line with the official Scrum guide.

Sites and Blogs

These guys lead by example and have some great articles and resources:

Definition of Done – DoD

5 challenges creating-done-increment

Team Ownership -done

Team Collaboration -done

General Information   Stephanie Ockerman Brett Maytom Nader Lucas Smith Lucas Smith Martin Hinshelwood Resources specifically for those interested in the Product Owner role Great place to start learning and to take certifications

Psychological Models In Scrum

Product Owner (PO) Learning Path Here (SM)

Scrum Master (SM) Learning Path Here (SM)

PSM 1 v PSM 2 here

PSPO2 suggested reading

Elevator Pitch: Agile

Product Owner

Telling It Like It Is Here. Ken Schwaber’s Blog:

PO Pdf Checklist HERE

PO: Tips for PO (see links at the end of the page) Here

Tools and Templates

See also


Scrum Master Toolbox

Scrum Master Toolbox

SAFe Business Agility Podcast

Podcast link

Guaranteed Irish Business Podcast

Podcast link

Visual & YouTube

Scaled Agile Framework (SAFe) Tutorial
User Story Mapping
Agile Product Ownership in a Nutshell
Irish Tax: VAT basics
Scrum Master Interview
Learn Jira
UX User Experience Design

Reactjs to build user interfaces. Learn how here


Sample website and app designs:

Books: Reading / Audio

The Professional Product Owner

The Professional Product Owner Buy Here

Authors: Don McGreal Don’s site

Ralph Jocham: Ralph’s site

The Art of Doing Twice the Work in Half the Time

Buy Here

Author: Jeff Sutherland (co creator of scrum)

The Hitch-hikers guide to Agile Coaching

Buy Here

Authors: The agile 42 Coaches

Agile42’s Site

The Goal:

Topic: Lean production journey for production plant

Buy Here

Author: E. M. Goldratt

The Phoenix Project

Topic: DevOps

Buy Here

Authors: Kim, Behr & Spafford

The Lean Startup

Buy Here

Author: Eric Ries

Scrum Master Job Description

The Scrum Master is responsible for managing and facilitating the Scrum process, ensuring the team adheres to the values and principles of the Agile methodology.

The Scrum Master’s primary responsibilities include helping to define and refine team processes, removing impediments to progress, and guiding the team toward successful outcomes.

The Scrum Master acts as a coach to the team, helping them to become self-organizing and highly productive.

The Scrum Master will also work with the Product Owner to ensure a clear understanding of the product goals, and help the team to prioritize accordingly.

The Scrum Master will be responsible for setting up and running daily Scrum meetings, helping to plan and facilitate sprint reviews and retrospectives, and assisting with any conflict resolution that may arise. The Scrum Master will also need to stay up to date with Agile best practices and be available to answer questions and provide guidance to the team.

Qualities that make a Great Scrum Master

A Scrum Master is a facilitator and leader who helps a Scrum team to follow the Scrum framework and principles. The most important skills of a Scrum Master include:

  1. Leadership: A Scrum Master must be able to lead the team and help them to work together effectively.
  2. Facilitation: A Scrum Master must be able to facilitate meetings and discussions, and help the team to make decisions.
  3. Communication: A Scrum Master must have strong communication skills and be able to convey information clearly and effectively to the team, stakeholders and other relevant parties.
  4. Coaching: A Scrum Master must be able to coach the team members, help them to identify and overcome obstacles, and improve their skills.
  5. Conflict resolution: A Scrum Master must be able to help the team to resolve conflicts and maintain a positive and productive working environment.
  6. Problem-solving: A Scrum Master must be able to help the team to identify and solve problems, and make decisions that are in the best interest of the project and the team.
  7. Knowledge of Scrum: A Scrum Master must have a deep understanding of the Scrum framework and be able to apply it effectively.
  8. Adaptability: A Scrum Master must be able to adapt to the changing needs of the team and the project, and be able to guide the team through changes.

Scrum Product Owner Job Description

A Scrum Product Owner is responsible for managing the product backlog and ensuring that the development team is delivering value to the customer.

The Product Owner is the voice of the customer and acts as a liaison between the development team and the stakeholders. They are responsible for ensuring that the product roadmap aligns with the company’s strategy and objectives.

The Product Owner is responsible for anticipating customer needs and developing features that address those needs. They will also prioritize features and manage the development team’s resources to ensure that the most important features are developed first. The Product Owner will also be responsible for setting clear goals, defining acceptance criteria, and monitoring progress against those goals.

To succeed in this role, the Product Owner should have a good understanding of the product, the customer, and the market. They should have excellent communication and organizational skills and be able to work effectively with multiple stakeholders. Additionally, the Product Owner should have experience working with Agile methodology and be comfortable with data-driven decision making.