Daily Scrum or Daily stand up meeting is one of the most important features of Agile Scrum practice.
The daily scrum or stand-up meeting is to give your team members a sense of progress (this is not a status update meeting – for the managers).
Keep it in the same time daily and at the same place – preferably in the morning, so that you can plan the whole day. Keep it to 15 mins and have this standing up – that will keep the team focused and brief.
There are team-members including scrum masters and PO who are committed and should mandatorily participate in the meeting, the “manager” and others are involved and will play a supporting role only when required. (Remember the Chicken and Pig analogy)
Each team member answers the following three questions:
- What did you do yesterday?
- What will you do today?
- Are there any impediments in your way?
Given the average team size of 7, each team member should not take more than 1.5 mins to complete her status update. So, one has to be precise, to-the-point and purposeful while updating the status. Here is a good template script for status update:
"Yesterday I have taken up the task called "create a new api for accessing the <xyz> data from <mmm> table". This is part of the user story: "As a user, I want to do <abc..>, so that I can achieve <def..>. The task is about 70% done and I need to add a few more validations and complete the unit testing before handing over to <testing team mate> for api testing. Remaining work left for this task is 3 hrs - which I'll do today. Apart from this, I'll take up the next task: "...." which is part of the user story: "As a ...". The planned effort of this task is 5 hrs and I'll complete this today. I have one impediment: I did not get enough time from <a team mate> to review my code as she was busy. Can I have another team mate to review my code today?"
Use this meeting to clarify any user story from the PO. Also use this meeting to add additional story, additional task to the sprint. Do not use this meeting for lengthy design/ architecture discussions. These are important, schedule separate meeting for these.
Scrummaster should maintain story/ task list, fill in the estimate and remaining time data everyday to generate the burn down chart. This gives important indication on overall sprint progress and helpful during Retrospection.
Mark a backlog complete only when it’s really complete – after integration, testing, bug fixing and other DOD (Definition of Done) criteria completed. Don’t keep these items towards the end. Use the physical post-it notes to move stories/ tasks from planned ->In progress -> Done.
Trust me, it's is a lot of fun to keep crossing completed tasks!
PS: More resources from internet: https://www.mountaingoatsoftware.com/agile/scrum/daily-scrum
No comments:
Post a Comment