Agile and Lean Software Development

Agile and Lean Software Development

68,026 members
  • Join

    When you join a group, other members will be able to see your profile and message you. The group logo will be visible on your profile unless you change that setting.

  • Information and settings

Have something to say? Join LinkedIn for free to participate in the conversation. When you join, you can comment and post your own discussions.

Silke

Does anyone have any effective & insighful reporting templates (burn down chart, daily scrum report templates) that they are willing to share and explain how they work for you?

Client Services Manager, EMEA at lynda.com

Would be great to see some good and simple reports and how you use them when working with different onshore/offshore teams that you are coordinating for a delivery of an application.

  • Comment (10)
  • July 29, 2012
  • Close viewer

Comments

  • David G.

    David

    David G.

    Passionate Agile Transformation Coach and High Tech Executive

    My scrum masters put together a spread sheet that displays a release burndown chart. You might be able to adapt it for a daily sprint burndown. Would that be helpful?

  • Silke P.

    Silke

    Silke P.

    Client Services Manager, EMEA at lynda.com

    Hi David, thanks for answering ... Yes it would be great to get the spreadsheet your Scrum Master is using ... I have a burn down chart - but am always looking for versions to see if there is anything better out there :).
    How can I receive your template?
    Silke

  • David G.

    David

    David G.

    Passionate Agile Transformation Coach and High Tech Executive

    She's at another office this week. I'll reach out to her. One thing that's
    different for release plans is that it's common for the "ideal" to change
    due to "emerging requirements" that add to the Must Have list. So there's
    some additional complexity in these sheets, but you can probably just
    ignore those cases.
    Hopefully those situations don't occur (at least not frequently) within a
    sprint.

  • Chris J.

    Chris

    Chris J.

    Software Engineer at Pivotal Labs

    What kind of information are you looking to communicate and to whom are you communicating that information? Burn down, burn up, daily scrum report (doesn't a story wall communicate that) all have their place, but are used for very different things.

    Also, in my opinion, creating charts that show what is being done in a day or in a week is too small a time frame to be of any use. In my opinion, they are just another use of command and control and are used by managers wanting to ensure that their subjects, er.. employees, are doing things everyday. A daily standup is a far better method of determining what people are working on.

    A burn up chart, or any report, that charts activity over a period of time and allows you to predict activity into the future is a much better metric, especially when scope is included, for showing what your team has and can do.

  • David G.

    David

    David G.

    Passionate Agile Transformation Coach and High Tech Executive

    We provide release burn-downs for both the teams and for Management. It helps the teams know where they are as plan out later releases and reinforces the importance of velocity.

    We also use sprint burn-downs (although I personally prefer burn-ups). They are done by hand on whiteboards or easels in the Scrum meeting area. Even though they cover a short duration (2 weeks in our case), they provide useful fodder for some retrospectives. If they have flat-lined for 3 days or more, the team can see that something is wrong and the Scrum Master doesn't have to say anything, just update the graph in the room and let it speak for itself.

  • Silke P.

    Silke

    Silke P.

    Client Services Manager, EMEA at lynda.com

    Thanks David - it is occurring sporadically but we have a change control process in place to adjust requirements that might come in or will have to be taken out.
    What is your length for the sprints that your are running? Do you also have any resource capacity planning elements in your spreadsheets that could be interesting to compare to what I have right now also.
    Thanks for responding ...
    Regards
    Silke

  • David G.

    David

    David G.

    Passionate Agile Transformation Coach and High Tech Executive

    Our sprints are 2 weeks long. The spreadsheet has input for velocity for
    each sprint, so we can look at a moving average and adjust for upcoming
    known impacts (e.g. holiday or vacation, etc.) and guesstimate velocity.

Have something to say? Join LinkedIn for free to participate in the conversation. When you join, you can comment and post your own discussions.

Your group posting status

Your posts across groups are being moderated temporarily because one of your recent contributions was marked as spam or flagged for not being relevant. Learn more.

Feedback