Making Daily Scrum Meetings Really Effective & Efficient (Part 5 of 5)

If you’ve been reading my earlier posts in this series, you know all about the High-Effectiveness, High-Efficiency Daily Scrum Quadrant.

As I wrap up this series, I’ll leave you with 8 practical tips every ScrumMaster should follow to improve the effectiveness and efficiency of their daily Scrums:

1. Arrive at the daily Scrum meeting room 10 to 15 minutes before the scheduled time.

2. Prepare audio, Web and video conferencing connections for remote or distributed attendees.

3. Open Daily_Journal files for each team member (click here to download the template). A team may decide to use a shared folder on a network file server to keep Daily Journal files for its team members (one file per member for each sprint). Alternatively, these files can be maintained on SharePoint or Google Docs. Remind your  team members to finalize and close their files 30 minutes before the meeting start. Files should not be locked out or in read-only mode; they should be editable. Log into your agile tool and keep the team’s burn-chart, cumulative flow chart, and Kanban boards (Storyboard, Taskboard, Testboard) open for the Scrum team.

4.  All the above start-up activities should be completed prior to the daily Scrum meeting so no meeting time is wasted.

5. Ask each team member to present information in his/her Daily_Journal already projected on the screen by following the guidelines covered in this article; this takes 2 minutes per person on an average.

6. Show and discuss team-level burn-charts (burn-down and burn-up) and Kanban boards, identify and log issues, if any; approximately 2 minutes.

7. No issues are discussed at the meeting; issues are only identified and assigned to the appropriate people to resolve them outside the daily Scrum meeting.

8. Focus on the patterns mentioned in the “High Effectiveness – High Efficiency” quadrant of the table, and avoid various anti-patterns and dysfunctions noted in the other 3 quadrants.

I have seen dozens of Scrum teams use the daily Scrum methods, tips and Daily_Journal template described in this blog series for making their daily Scrums both highly effective and efficient.  I hope you are able to apply this information in your own daily Scrums. Got any tips of your own to share? What has worked for you? What has not?

If you would like to receive a single file version (as a PDF document) of this 5-part blog series, please send me an email at Satish.Thatte@VersionOne.com requesting the document.

Part 1

Part 2

Part 3

Part 4

Part 5

 

 

This entry was posted in Agile Benefits, Agile Development, Agile Management, Agile Project Management, Agile Teams, Agile Tools, Agile Velocity, Iterative Development, Kanban, Scrum Development, Scrum Methodology, Scrum Software, Scrum Tools. Bookmark the permalink.

4 Responses to Making Daily Scrum Meetings Really Effective & Efficient (Part 5 of 5)

  1. Scott Hamilton says:

    It would be great to turn this into a feature request for VersionOne. Having it integrated into the sprint data already in the system would help with the administrative overhead, and having it all in one place means fewer tools each member has to work with in the process of executing the daily tasks.

    • Satish Thatte says:

      Scott, thanks for your feedback on my “Daily Scrum” blog. I have submitted your request as a new feature to support Daily Scrums to VersionOne Product Team. Many others have requested similar things (a new feature to support Daily Scrums in VersionOne).

      Regards,
      Satish Thatte
      Agile / Lean Coach and Product Consultant
      VersionOne

  2. Pingback: Making Daily Scrums Really Effective & Efficient (Part 4 of 5) | The Agile Management Blog

  3. Pingback: Making Daily Scrum Meetings Really Effective & Efficient (Part 3 of 5) | The Agile Management Blog

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>