Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Template for daily scrum meeting status
Last Post 16 Mar 2016 09:33 PM by Ian Mitchell. 13 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
aparna s
New Member
New Member
Posts:1
aparna s

--
23 Apr 2014 11:57 PM
    Hi all,
    My client need a daily status report to be sent using the i mputs from daily scrum call.
    can sombody help me with a template ?

    Regards,
    Aparna S
    Ludwig Harsch
    Basic Member
    Basic Member
    Posts:272
    Ludwig  Harsch

    --
    24 Apr 2014 02:20 AM
    What does your client need it for?
    This request indicates that the purpose of the daily SCRUM is not fully understood.
    Chee-Hong Hsia
    New Member
    New Member
    Posts:73
    Chee-Hong Hsia

    --
    24 Apr 2014 02:50 AM
    I think this is an inevitable behaviour.

    It doesn’t matter how much scrum training and/or knowledge the clients receives, at the end of the day it’s about the result. And because of this, they want to be “in control”.
    I’m curious in how many Agile participants here has actually told a non-developer “Hey you are a chicken, don’t interfere!”

    Despite this, by applying scrum the team is able to communicate towards stakeholders/clients etc. on many levels, like daily, sprint and release planning. So I think you’re talking more on the daily planning level?
    If that’s the case, I would communicate something like a burn-down chart, just to give the client an idea of where the team is at.
    Just be careful that this level of planning doesn’t happen on personal level. Its a team effort.
    Arun Vattaparambil
    New Member
    New Member
    Posts:2
    Arun Vattaparambil

    --
    24 Apr 2014 11:17 AM
    HI,

    Before you send this information out, There arises a question how does your daily scrum operate now.
    1) Does every participant address his/her tasks completed/ in progress since last call, predicted work to be done till next stand up and finally pointing out impediments or obstacles.. if this ritual is followed clearly, there is no need of any documents minutes unless the audience is a stake holder is overseeing four or five scrum teams.

    2) Nevertheless, if you have to send a scrum meeting status. I would recommend to do it in a simple format in an excel and not spend much time on it.
    Team :
    Scrum Member :
    Story:
    Task:
    done & planned
    issues:
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    24 Apr 2014 11:04 PM
    Your client should care about the incremental delivery of results of value, and not about daily status reports. That aside, it's the responsibility of the Product Owner to liaise with and represent the client on an ongoing basis.

    If you are a Scrum Master, you have a responsibility to work with other stakeholders to remove impediments so Sprint Goals can be met. As such, might it be appropriate to put the focus on risks, issues and impediments that need to be highlighted to those parties?
    Etienne Laverdière
    New Member
    New Member
    Posts:1
    Etienne Laverdière

    --
    01 May 2014 09:40 AM
    Making this excel report is a waste, sending and managing this report is a waste. If they want to have an idea of what happening in Daily Scrum Meeting, the best thing they could do is to assist to the DSM and *not interfere*.

    Do not send any excel file of any sort, you will be trapped inside it.

    The Daily Scrum/Standup Meeting reports already exist. They are the Taskboard and the Burndown chart. Theses are the only report you need to send to your manager. I cannot be clear enough on that.
    Himadri Bhattacharya
    New Member
    New Member
    Posts:18
    Himadri Bhattacharya

    --
    01 May 2014 11:55 PM
    I agree with the sprint burn down chart and a list of risk, issues and impediments.

    Scrum is all about collaboration, so the product owner can ask the client to be present at the daily scrum meeting but they should NOT be allowed to talk or question the team. Scrum Master as facilitator should ensure that. After the daily scrum meeting is over the client can discuss any issues/concerns with the Product Owner.

    Personally I haven't worked on any team where the client has been available to us everyday - if you have such an opportunity then make full use of it.
    Standup Report
    New Member
    New Member
    Posts:1
    Standup Report

    --
    19 Oct 2014 12:34 PM
    www.standup.report - Your daily scrum report tool
    You should also get a web template for Standup Report there.
    Dharmesh Kothari
    New Member
    New Member
    Posts:3
    Dharmesh Kothari

    --
    20 Oct 2014 03:17 PM
    This is common for teams that have been used to a different style of software project management in the past and are used to seeing reports. Suddenly with Scrum they realize there are no reports and feel at a loss. It needs education and convincing that Scrum is efficient and different. It is efficient because it is different. It cuts down on a lot of waste - unnecessary reports, unnecessary meetings etc. but still makes everything transparent. The scrum artifiacts - sprint backlog, sprint burndown are the artifiacts the customer should be looking at. It seems like currently he is not plugged into the process. But he should be.
    Nicolas Girault
    New Member
    New Member
    Posts:1
    Nicolas Girault

    --
    13 Mar 2016 11:23 PM
    Hi,

    I wrote an article about sending daily reports to product owners: http://www.theodo.fr/blog/2015/10/y...-reports/.

    More recently I've been working on an app to automate as much as possible this report. It assumes you use Trello to manage the production workflow: http://theodo.github.io/scrumble.

    I hope it can help!
    Alzoubi Ila
    New Member
    New Member
    Posts:6
    Alzoubi Ila

    --
    16 Mar 2016 05:52 AM
    wouldn't it make sense to document the discussions and action items in case the scrum master needs to take that summary to scrum of scrum?
    Olivier Ledru
    Basic Member
    Basic Member
    Posts:229
    Olivier Ledru

    --
    16 Mar 2016 12:43 PM
    The presence of the Scrum master is not required in the Daily Scrum.
    Why do you want the Scrum master to be in a Scrum of Scrum ?
    Alzoubi Ila
    New Member
    New Member
    Posts:6
    Alzoubi Ila

    --
    16 Mar 2016 08:33 PM
    Olivier - Here is what I learnt from scrum alliance training - The Scrum Masters and anyone else needed to deliver the Scrum of Scrums collaborative Definition of Done meet and communicate impediments, progress, and any cross team coordination that needs to happen by answering for the team the same three questions used in the Daily Scrum.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    16 Mar 2016 09:33 PM
    Why would Scrum Masters be needed to create a Definition of Done at any level?
    You are not authorized to post a reply.


    Feedback