Daily scrum, when properly implemented in business and project endeavours leads to improved communication among teams, and by so doing, solves one of the greatest problems faced by teams today. 

 

daily scrum

 

Although Agile coaches and experts would recommend that Agile teams work within the same workplace as a way of maximizing collaboration, there are times when working with teams in remote locations becomes just inevitable.

So, this is the point where I introduce you to Sinnaps online project management software, a complete collaboration tool for businesses, organizations and just anyone undertaking any business activity.

It is great for teams, whether collocated or working remotely, and presents an even better way to organize your Scrum dashboard and prepare your team for remote work, Scrum meetings, Scrum stand-up meetings, Agile meetings, etc.

In this article, we will discuss daily Scrum meetings and all such things as purpose of daily Scrum meetings, who starts the daily Scrum, who is required to attend the daily Scrum, daily Scrum agenda, etc.

 

Daily Scrum

 

When managing projects, daily Scrum provides an avenue to make certain that the project is progressing positively towards the sprint goals, an opportunity to synchronize team activities and come up with plans that will ensure greater project success. Being an essential component of a sprint doesn’t make this activity any easy.

In fact, most often than not, teams tend to struggle to keep these meetings as effective as they ought to be. Meetings in which team member arrive 10 – 15 minutes later than the stipulated time, or where relevant meeting agenda are discussed on comment sections rather than addressed in the meeting are among the many challenges keeping businesses, teams and managers from reaching their project goals.

 

Online Free Project Management Course

You will receive 5 lessons over the course of 15 days

Subscribe now!

 

brainstorming thecniques

 

Agile Daily Scrum Meeting

 

Agile daily Scrum meetings are typically held on each day of a sprint. For consistency, it is held at the same location and begins at the same time for each day. As a way of setting the tone for work to be carried out in the coming days, it is typically held in the mornings. 

Scrum meetings are often carried out by members of the development team, the ScrumMaster as well as the product owner. So, who starts the daily Scrum meeting? There have certainly been a lot of questions regarding Scrum master daily tasks in Agile daily Scrum meetings, however, presiding over daily Scrum is not entirely the crux of a Scrum master’s daily activities.

The self-starting nature of Scrum teams means there is no stipulated rules about who starts a discussion or not. Should an issue arise about who starts a daily Scrum, then the best way to resolve this, would be for the Scrum master to bring it up in a sprint retrospective, where the issue will be resolved.

Efficient Scrum teams are those that are able to self-manage their activities even in the absence of the Scrum master. Among other things, the Scrum master daily activities would include the following:

  • Facilitating the meetings, and not necessarily participating in them.
  • Helping teams create and maintain their daily Scrum boards and teach them to use Scrum tools
  • Ensure daily Scrum questions are taken care of in sprint reviews, sprint retrospective and sprint planning sessions.
  • Ensure proper collaboration between Scrum teams and the product owner.
  • Conducting product owner daily scrum to walk the product owner through more technical user stories.

 

Time Box for Daily Scrum

 

All project activities under the Scrum framework are time-boxed, thus, daily Scrum meetings are inherently time-boxed activities. As a general rule, the time box for daily Scrum meetings is 15 minutes. Timeboxing Scrum meetings is a good way to maximize productivity by splitting projects into fixed periods for different project activities. 

In essence, this technique enables business leaders and project managers to limit the amount of time a team will spend on certain activities. The concept of apportioning a fixed length of time to a segment of activities in Scrum, where the unit of time or timeframe for such activity is called a tome box is quite useful in defining open-ended or ambiguous tasks.

Below is a list of Scrum activities as well as their generally accepted timeframe:

  • Sprint planning – For a typical sprint length of a week, the sprint planning sessions should be about 2 hours.
  • Daily Scrum – The time box period for this activity generally does not exceed 15 minutes.
  • Sprint Review – Again, for a sprint length, covering a period of 1 week, the sprint review generally does not exceed 1 hour.
  • Sprint Retrospective – Considering a sprint length of 1 week, the sprint retrospective time box should generally not exceed 1 hour.

You can look through other articles to see how you can improve efficiency by implementing time box for daily Scrum using Sinnaps.

 

 

Daily Scrum meetings are a good way to begin a project and ensure a smooth flow of activities throughout the project lifecycle. Among other things, members ask themselves the fundamental questions including what they did yesterday, what they’ll do today, as well as assess the viability of impediments or blockers that may likely keep them from achieving set objectives.

 

Artículos recientes

Escribe un comentario