Daily Scrum Meeting: *Time Changes*

classic Classic list List threaded Threaded
2 messages Options
Dawn Smith Dawn Smith
Reply | Threaded
Open this post in threaded view
|

Daily Scrum Meeting: *Time Changes*

Hi Everyone!

What we've heard loud and clear is that the inconsistent times for the daily scrum caused a barrier to community participation in the development sprints and daily scrum meetings. Based on that feedback, we've changed the scrum times to be more consistent.

Below is the new, daily scrum meeting schedule and ways to participate:

Daily Scrum Meeting Schedule:
  • Monday, Tuesday, Wednesday, Friday: 14:00-14:30 UTC / 10:00am-10:30am EDT
  • Thursday: 19:00-19:30 UTC / 15:00-15:30 UTC (this occurs later in the day due to OpenMRS meetings on Thursday)
How to Join:
  • The daily scrum meeting takes place on the #openmrs channel on freenode.

Making the Meeting Efficient:

  • Be available at the proper start time.
  • Write your update 10 minutes before the daily scrum meeting.
    • Set your calendar reminder alarm for 10 minutes before the daily scrum meeting. When the alarm occurs, write up your work and prepare for the meeting.
    • The update should be a summary of the following:
      1. What you worked on during the previous day
      2. What you are currently working on today
      3. What you will continue to work on after the meeting has finished
      4. A list of any blockers, or items that are slowing down your progress
  • Stay focused on the IRC channel window.
    • If the daily scrum meeting were in person, we'd all be standing up. That's not easy to do on IRC, so it's important to pay attention.
    • The biggest delay in the meeting occurs when we focus on other windows on our computer. Either close or minimize those windows before the meeting.
  • Save all problem solving for the end of the meeting.
    • Updates, output, blockers, and change-of directions will go out quickly during the scrum from each individual. Afterwards, the group will go over problem-solving for the blockers that need to be resolved.
  • Be honest about blockers!
    • Blockers are issues that are getting in the way of doing other work, or challenging issues that are taking up a lot of time.
    • The main reason for the daily scrum meeting is to share information about blockers and resolve them together.
    • If you have worked on the same problem for more than 1 hour (even if you think you know the solution!) state it as a blocker.

Thanks you for your feedback and active participation in the community!

-Dawn
[hidden email] from OpenMRS Developers' mailing list
Darius Jazayeri-3 Darius Jazayeri-3
Reply | Threaded
Open this post in threaded view
|

Re: Daily Scrum Meeting: *Time Changes*

This time change is effective immediately, so starting tomorrow (i.e. Tuesday), all scrums will be at 14:00-14:30 UTC = 10am-10:30am ET.

(Except of course Thursday...)

-Darius

On Mon, Apr 16, 2012 at 10:06 AM, Dawn Smith <[hidden email]> wrote:
Hi Everyone!

What we've heard loud and clear is that the inconsistent times for the daily scrum caused a barrier to community participation in the development sprints and daily scrum meetings. Based on that feedback, we've changed the scrum times to be more consistent.

Below is the new, daily scrum meeting schedule and ways to participate:

Daily Scrum Meeting Schedule:
  • Monday, Tuesday, Wednesday, Friday: 14:00-14:30 UTC / 10:00am-10:30am EDT
  • Thursday: 19:00-19:30 UTC / 15:00-15:30 UTC (this occurs later in the day due to OpenMRS meetings on Thursday)
How to Join:
  • The daily scrum meeting takes place on the #openmrs channel on freenode.

Making the Meeting Efficient:

  • Be available at the proper start time.
  • Write your update 10 minutes before the daily scrum meeting.
    • Set your calendar reminder alarm for 10 minutes before the daily scrum meeting. When the alarm occurs, write up your work and prepare for the meeting.
    • The update should be a summary of the following:
      1. What you worked on during the previous day
      2. What you are currently working on today
      3. What you will continue to work on after the meeting has finished
      4. A list of any blockers, or items that are slowing down your progress
  • Stay focused on the IRC channel window.
    • If the daily scrum meeting were in person, we'd all be standing up. That's not easy to do on IRC, so it's important to pay attention.
    • The biggest delay in the meeting occurs when we focus on other windows on our computer. Either close or minimize those windows before the meeting.
  • Save all problem solving for the end of the meeting.
    • Updates, output, blockers, and change-of directions will go out quickly during the scrum from each individual. Afterwards, the group will go over problem-solving for the blockers that need to be resolved.
  • Be honest about blockers!
    • Blockers are issues that are getting in the way of doing other work, or challenging issues that are taking up a lot of time.
    • The main reason for the daily scrum meeting is to share information about blockers and resolve them together.
    • If you have worked on the same problem for more than 1 hour (even if you think you know the solution!) state it as a blocker.

Thanks you for your feedback and active participation in the community!

-Dawn
[hidden email] from OpenMRS Developers' mailing list


[hidden email] from OpenMRS Developers' mailing list