blog

June 07, 2021

•5 min read

Daily Scrum Meetings: Purpose, participants, and guidance

cover

What is a daily scrum meeting in agile?

We know that agile teams use scrum to organize their process. Teams use the daily scrum to help keep their sprints focused and on target. In scrum, every day during a sprint the software development team holds a short meeting. We call this meeting the daily scrum. The development team holds the meeting in the same location at the same time of day. Mornings work best. Teams should time-box their daily scrum to no more than 15 minutes. The time-box keeps the daily scrum on-topic and focused.

Read on other types of the meetings in Agile meetings: Types, goals, and benefits article.

Every member of the team should attend the daily scrum. The scrum master, product owner, developers, and designers. People outside the team may attend the meeting, but only as observers. People from outside the team do not act as active participants. In each daily scrum the team members answer three questions:

  1. What tasks did you complete yesterday?
  2. What tasks will you work on today?
  3. Do you foresee any roadblocks or issues that might slow you down?

The daily scrum meeting should help members of the team focus on common goals. It should also help them to commit to what they intend to accomplish. The team usually has the daily scrum meeting while standing. The standing part is important. Teams who are standing have more focus and energy. A person who sits down will not feel the same sense of urgency, which could make the meeting drag on longer than necessary.

Software development teams use the daily scrum to accomplish several goals:

  • Adapt sprint backlog and daily plans to the current situation
  • Track progress
  • Improve team collaboration and participation
  • Identify roadblocks and impediments
  • Synchronize the team member's efforts for maximum impact

So why do we make time for a daily scrum meeting? 

Teams engage in daily scrum meetings to communicate. Each day the team updates the other members on the current status of their work and progress. The team members have a chance to explain what obstacles they are facing as well as ask for help. Daily scrum meetings help teams to focus on their work and understand their part of the sprint. Teams don’t have to send lengthy summary emails or long reports. Instead, they verbally update each other in real-time.

According to scrum.org,  “The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.

The Daily Scrum is a 15-minute event for the Developers of the Scrum team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.”

The daily scrum asks teams to highlight:

  • What each member accomplished the day before
  • What they will accomplish today
  • what they plan for the day after

This helps the team to understand the amount of work completed and the work that remains. The daily scrum meeting is the opposite of a status update meeting, where a boss asks for information about who is on or behind schedule. Instead, the daily scrum meeting has no hierarchy. Each team member commits to helping the sprint to the best of their abilities. The scrum master schedules and guides the meeting, but the scrum team arrives at the meeting on equal footing.

Daily scrum meetings ask teams to experiment and remain motivated. The daily scrum works best when the team members keep their comments brief. The daily scrum should not turn into a problem-solving session. Instead, team members who face obstacles should inform the scrum master, who will aim to remove the obstacles as quickly as possible.

Some brief guidelines for scrum meetings:

  • Teams should hold daily scrum meetings at fixed times and locations
  • All members should attend.
  •  The team should attend the daily scrum as a force of habit. The habit will reinforce easy communication between team members.
  • Teams should actually stand. Standing forces the members to think with speed and efficiency.
  • Each team member explains their progress in a concise manner.
  • The scrum master facilitates the meeting but doesn't boss. The meeting should happen without hierarchy.
  • One team member at a time speaks, nobody should interrupt them except with relevant questions.
  • Each team member speaks only once.
  • Teams can incorporate sprint boards and user stories into the daily scrum meeting.

Developers use the daily scrum meeting to gauge their progress toward the sprint goal. They also analyze their progress with the sprint backlog. The daily scrum helps the team to accomplish their goals. Each daily scrum should help the whole team communicate and self-organize.

The software development team uses the daily scrum to view their progress toward the sprint goal. They analyze their backlog and the work trends. These meetings help teams to understand challenges and end goals. Team members will sometimes meet separately after the daily scrum to discuss details and adaptations.

Daily scrum meetings facilitate effective communication within scrum teams. The daily scrum helps teams to share common goals. Daily scrum also eliminates other longer meetings. Daily scrum meetings help teams to identify impediments and obstacles. Teams that attend daily scrum meetings make thoughtful decisions more quickly and share knowledge in a more fluid manner. Here at Blocshop, we harness all the benefits of the daily scrum to deliver our projects on time and under budget. If you want to learn more about how we help companies achieve their goals using scrum, please do get in touch!

Learn more from our insights

cover-img

NOVEMBER 3, 2025 • 7 min read

CE marking software under the EU AI Act – who needs it and how to prepare a conformity assessment

From 2026, AI systems classified as high-risk under the EU Artificial Intelligence Act (Regulation (EU) 2024/1689) will have to undergo a conformity assessment and obtain a CE marking before being placed on the EU market or put into service.

cover-img

October 19, 2025 • 7 min read

EU and UK AI regulation compared: implications for software, data, and AI projects

Both the European Union and the United Kingdom are shaping distinct—but increasingly convergent—approaches to AI regulation.

For companies developing or deploying AI solutions across both regions, understanding these differences is not an academic exercise. It directly affects how software and data projects are planned, documented, and maintained.

cover-img

October 9, 2025 • 5 min read

When AI and GDPR meet: navigating the tension between AI and data protection

When AI-powered systems process or generate personal data, they enter a regulatory minefield — especially under the EU’s General Data Protection Regulation (GDPR) and the emerging EU AI Act regime

cover-img

September 17, 2025 • 4 min read

6 AI integration use cases enterprises can adopt for automation and decision support

 

The question for most companies is no longer if they should use AI, but where it will bring a measurable impact. 

logo blocshop

Let's talk!

blog

June 07, 2021

•5 min read

Daily Scrum Meetings: Purpose, participants, and guidance

cover

What is a daily scrum meeting in agile?

We know that agile teams use scrum to organize their process. Teams use the daily scrum to help keep their sprints focused and on target. In scrum, every day during a sprint the software development team holds a short meeting. We call this meeting the daily scrum. The development team holds the meeting in the same location at the same time of day. Mornings work best. Teams should time-box their daily scrum to no more than 15 minutes. The time-box keeps the daily scrum on-topic and focused.

Read on other types of the meetings in Agile meetings: Types, goals, and benefits article.

Every member of the team should attend the daily scrum. The scrum master, product owner, developers, and designers. People outside the team may attend the meeting, but only as observers. People from outside the team do not act as active participants. In each daily scrum the team members answer three questions:

  1. What tasks did you complete yesterday?
  2. What tasks will you work on today?
  3. Do you foresee any roadblocks or issues that might slow you down?

The daily scrum meeting should help members of the team focus on common goals. It should also help them to commit to what they intend to accomplish. The team usually has the daily scrum meeting while standing. The standing part is important. Teams who are standing have more focus and energy. A person who sits down will not feel the same sense of urgency, which could make the meeting drag on longer than necessary.

Software development teams use the daily scrum to accomplish several goals:

  • Adapt sprint backlog and daily plans to the current situation
  • Track progress
  • Improve team collaboration and participation
  • Identify roadblocks and impediments
  • Synchronize the team member's efforts for maximum impact

So why do we make time for a daily scrum meeting? 

Teams engage in daily scrum meetings to communicate. Each day the team updates the other members on the current status of their work and progress. The team members have a chance to explain what obstacles they are facing as well as ask for help. Daily scrum meetings help teams to focus on their work and understand their part of the sprint. Teams don’t have to send lengthy summary emails or long reports. Instead, they verbally update each other in real-time.

According to scrum.org,  “The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.

The Daily Scrum is a 15-minute event for the Developers of the Scrum team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.”

The daily scrum asks teams to highlight:

  • What each member accomplished the day before
  • What they will accomplish today
  • what they plan for the day after

This helps the team to understand the amount of work completed and the work that remains. The daily scrum meeting is the opposite of a status update meeting, where a boss asks for information about who is on or behind schedule. Instead, the daily scrum meeting has no hierarchy. Each team member commits to helping the sprint to the best of their abilities. The scrum master schedules and guides the meeting, but the scrum team arrives at the meeting on equal footing.

Daily scrum meetings ask teams to experiment and remain motivated. The daily scrum works best when the team members keep their comments brief. The daily scrum should not turn into a problem-solving session. Instead, team members who face obstacles should inform the scrum master, who will aim to remove the obstacles as quickly as possible.

Some brief guidelines for scrum meetings:

  • Teams should hold daily scrum meetings at fixed times and locations
  • All members should attend.
  •  The team should attend the daily scrum as a force of habit. The habit will reinforce easy communication between team members.
  • Teams should actually stand. Standing forces the members to think with speed and efficiency.
  • Each team member explains their progress in a concise manner.
  • The scrum master facilitates the meeting but doesn't boss. The meeting should happen without hierarchy.
  • One team member at a time speaks, nobody should interrupt them except with relevant questions.
  • Each team member speaks only once.
  • Teams can incorporate sprint boards and user stories into the daily scrum meeting.

Developers use the daily scrum meeting to gauge their progress toward the sprint goal. They also analyze their progress with the sprint backlog. The daily scrum helps the team to accomplish their goals. Each daily scrum should help the whole team communicate and self-organize.

The software development team uses the daily scrum to view their progress toward the sprint goal. They analyze their backlog and the work trends. These meetings help teams to understand challenges and end goals. Team members will sometimes meet separately after the daily scrum to discuss details and adaptations.

Daily scrum meetings facilitate effective communication within scrum teams. The daily scrum helps teams to share common goals. Daily scrum also eliminates other longer meetings. Daily scrum meetings help teams to identify impediments and obstacles. Teams that attend daily scrum meetings make thoughtful decisions more quickly and share knowledge in a more fluid manner. Here at Blocshop, we harness all the benefits of the daily scrum to deliver our projects on time and under budget. If you want to learn more about how we help companies achieve their goals using scrum, please do get in touch!

Learn more from our insights

cover-img

NOVEMBER 3, 2025 • 7 min read

CE marking software under the EU AI Act – who needs it and how to prepare a conformity assessment

From 2026, AI systems classified as high-risk under the EU Artificial Intelligence Act (Regulation (EU) 2024/1689) will have to undergo a conformity assessment and obtain a CE marking before being placed on the EU market or put into service.

cover-img

October 19, 2025 • 7 min read

EU and UK AI regulation compared: implications for software, data, and AI projects

Both the European Union and the United Kingdom are shaping distinct—but increasingly convergent—approaches to AI regulation.

For companies developing or deploying AI solutions across both regions, understanding these differences is not an academic exercise. It directly affects how software and data projects are planned, documented, and maintained.

cover-img

October 9, 2025 • 5 min read

When AI and GDPR meet: navigating the tension between AI and data protection

When AI-powered systems process or generate personal data, they enter a regulatory minefield — especially under the EU’s General Data Protection Regulation (GDPR) and the emerging EU AI Act regime

cover-img

September 17, 2025 • 4 min read

6 AI integration use cases enterprises can adopt for automation and decision support

 

The question for most companies is no longer if they should use AI, but where it will bring a measurable impact. 

logo blocshop

Let's talk!

blog

June 07, 2021

•5 min read

Daily Scrum Meetings: Purpose, participants, and guidance

cover-img

What is a daily scrum meeting in agile?

We know that agile teams use scrum to organize their process. Teams use the daily scrum to help keep their sprints focused and on target. In scrum, every day during a sprint the software development team holds a short meeting. We call this meeting the daily scrum. The development team holds the meeting in the same location at the same time of day. Mornings work best. Teams should time-box their daily scrum to no more than 15 minutes. The time-box keeps the daily scrum on-topic and focused.

Read on other types of the meetings in Agile meetings: Types, goals, and benefits article.

Every member of the team should attend the daily scrum. The scrum master, product owner, developers, and designers. People outside the team may attend the meeting, but only as observers. People from outside the team do not act as active participants. In each daily scrum the team members answer three questions:

  1. What tasks did you complete yesterday?
  2. What tasks will you work on today?
  3. Do you foresee any roadblocks or issues that might slow you down?

The daily scrum meeting should help members of the team focus on common goals. It should also help them to commit to what they intend to accomplish. The team usually has the daily scrum meeting while standing. The standing part is important. Teams who are standing have more focus and energy. A person who sits down will not feel the same sense of urgency, which could make the meeting drag on longer than necessary.

Software development teams use the daily scrum to accomplish several goals:

  • Adapt sprint backlog and daily plans to the current situation
  • Track progress
  • Improve team collaboration and participation
  • Identify roadblocks and impediments
  • Synchronize the team member's efforts for maximum impact

So why do we make time for a daily scrum meeting? 

Teams engage in daily scrum meetings to communicate. Each day the team updates the other members on the current status of their work and progress. The team members have a chance to explain what obstacles they are facing as well as ask for help. Daily scrum meetings help teams to focus on their work and understand their part of the sprint. Teams don’t have to send lengthy summary emails or long reports. Instead, they verbally update each other in real-time.

According to scrum.org,  “The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.

The Daily Scrum is a 15-minute event for the Developers of the Scrum team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.”

The daily scrum asks teams to highlight:

  • What each member accomplished the day before
  • What they will accomplish today
  • what they plan for the day after

This helps the team to understand the amount of work completed and the work that remains. The daily scrum meeting is the opposite of a status update meeting, where a boss asks for information about who is on or behind schedule. Instead, the daily scrum meeting has no hierarchy. Each team member commits to helping the sprint to the best of their abilities. The scrum master schedules and guides the meeting, but the scrum team arrives at the meeting on equal footing.

Daily scrum meetings ask teams to experiment and remain motivated. The daily scrum works best when the team members keep their comments brief. The daily scrum should not turn into a problem-solving session. Instead, team members who face obstacles should inform the scrum master, who will aim to remove the obstacles as quickly as possible.

Some brief guidelines for scrum meetings:

  • Teams should hold daily scrum meetings at fixed times and locations
  • All members should attend.
  •  The team should attend the daily scrum as a force of habit. The habit will reinforce easy communication between team members.
  • Teams should actually stand. Standing forces the members to think with speed and efficiency.
  • Each team member explains their progress in a concise manner.
  • The scrum master facilitates the meeting but doesn't boss. The meeting should happen without hierarchy.
  • One team member at a time speaks, nobody should interrupt them except with relevant questions.
  • Each team member speaks only once.
  • Teams can incorporate sprint boards and user stories into the daily scrum meeting.

Developers use the daily scrum meeting to gauge their progress toward the sprint goal. They also analyze their progress with the sprint backlog. The daily scrum helps the team to accomplish their goals. Each daily scrum should help the whole team communicate and self-organize.

The software development team uses the daily scrum to view their progress toward the sprint goal. They analyze their backlog and the work trends. These meetings help teams to understand challenges and end goals. Team members will sometimes meet separately after the daily scrum to discuss details and adaptations.

Daily scrum meetings facilitate effective communication within scrum teams. The daily scrum helps teams to share common goals. Daily scrum also eliminates other longer meetings. Daily scrum meetings help teams to identify impediments and obstacles. Teams that attend daily scrum meetings make thoughtful decisions more quickly and share knowledge in a more fluid manner. Here at Blocshop, we harness all the benefits of the daily scrum to deliver our projects on time and under budget. If you want to learn more about how we help companies achieve their goals using scrum, please do get in touch!

Learn more from our insights

cover-img

NOVEMBER 20, 2025 • 7 min read

The ultimate CTO checklist for planning a custom software or AI project in 2026

In 2026, planning a successful project means understanding five essential dimensions before any code is written. These five questions define scope, architecture, delivery speed, and budget more accurately than any traditional project brief.

NOVEMBER 13, 2025 • 7 min read

The quiet cost of AI: shadow compute budgets and the new DevOps blind spot

AI projects rarely fail because the model “isn’t smart enough.” They fail because the money meter spins where few teams are watching: GPU hours, token bills, data egress, and serving inefficiencies that quietly pile up after launch.

cover-img

NOVEMBER 3, 2025 • 7 min read

CE marking software under the EU AI Act – who needs it and how to prepare a conformity assessment

From 2026, AI systems classified as high-risk under the EU Artificial Intelligence Act (Regulation (EU) 2024/1689) will have to undergo a conformity assessment and obtain a CE marking before being placed on the EU market or put into service.

cover-img

October 19, 2025 • 7 min read

EU and UK AI regulation compared: implications for software, data, and AI projects

Both the European Union and the United Kingdom are shaping distinct—but increasingly convergent—approaches to AI regulation.

For companies developing or deploying AI solutions across both regions, understanding these differences is not an academic exercise. It directly affects how software and data projects are planned, documented, and maintained.

cover-img

October 9, 2025 • 5 min read

When AI and GDPR meet: navigating the tension between AI and data protection

When AI-powered systems process or generate personal data, they enter a regulatory minefield — especially under the EU’s General Data Protection Regulation (GDPR) and the emerging EU AI Act regime

cover-img

September 17, 2025 • 4 min read

6 AI integration use cases enterprises can adopt for automation and decision support

 

The question for most companies is no longer if they should use AI, but where it will bring a measurable impact. 

NOVEMBER 13, 2025 • 7 min read

The quiet cost of AI: shadow compute budgets and the new DevOps blind spot

AI projects rarely fail because the model “isn’t smart enough.” They fail because the money meter spins where few teams are watching: GPU hours, token bills, data egress, and serving inefficiencies that quietly pile up after launch.

NOVEMBER 13, 2025 • 7 min read

The quiet cost of AI: shadow compute budgets and the new DevOps blind spot

AI projects rarely fail because the model “isn’t smart enough.” They fail because the money meter spins where few teams are watching: GPU hours, token bills, data egress, and serving inefficiencies that quietly pile up after launch.

cover-img

N 19, 2025 • 7 min read

CE Marking Software Under the EU AI Act – Who Needs It and How to Prepare a Conformity Assessment

When AI-powered systems process or generate personal data, they enter a regulatory minefield — especially under the EU’s General Data Protection Regulation (GDPR) and the emerging EU AI Act regime

cover-img

NOVEMBER 13, 2025 • 7 min read

The quiet cost of AI: shadow compute budgets and the new DevOps blind spot

When AI-powered systems process or generate personal data, they enter a regulatory minefield — especially under the EU’s General Data Protection Regulation (GDPR) and the emerging EU AI Act regime

cover-img

N 19, 2025 • 7 min read

CE Marking Software Under the EU AI Act – Who Needs It and How to Prepare a Conformity Assessment

When AI-powered systems process or generate personal data, they enter a regulatory minefield — especially under the EU’s General Data Protection Regulation (GDPR) and the emerging EU AI Act regime

cover-img

NOVEMBER 13, 2025 • 7 min read

The quiet cost of AI: shadow compute budgets and the new DevOps blind spot

When AI-powered systems process or generate personal data, they enter a regulatory minefield — especially under the EU’s General Data Protection Regulation (GDPR) and the emerging EU AI Act regime