Hi Jim,
Sort of.
If I put my Agile Coach hat on, I would say that the metric you are looking to generate is not one that will give you the most insight to what needs to be done. To give you a case in point, the burndown chart shows that you are six days into the sprint and not one story has been Accepted. This really sets off my thought processes as to how your team is working and how they are interacting with the Product Owner, Scrum Master and other Stake Holders.
Focussing on the detail (in this case hours) is usually symptomatic of a different problem that centres around predictability and throughput.
------------------------------
Nik
Rally Sales Engineer
Rally Software
------------------------------
Original Message:
Sent: 01-17-2020 01:41 PM
From: Jim Smith
Subject: Burndown - Above the line / Below the line
@Nik Antonelli - Checking to see if I answered your question. Any help would be appreciated.
Original Message:
Sent: 01-17-2020 10:47 AM
From: Jim Smith
Subject: Burndown - Above the line / Below the line
In our weekly status meeting we use the difference to visually display how the teams are trending. Identifying the numbers above or below the line help all team see the trend to start productive conversations to get back on track if we are over or even see if one team well under the line might be able to lend a hand to another team while giving an executive summary in the form of the burndown.
Original Message:
Sent: 01-17-2020 08:25 AM
From: Ted Copeland
Subject: Burndown - Above the line / Below the line
Jim, are you using the difference to make decisions about how teams operate for the next week? Like Nik, I'm interested in the actions you take based on the data you're currently calculating manually.
Ted
Not a Rally engineer, just a guy interested in burndowns
Original Message:
Sent: 01-16-2020 02:47 PM
From: Jim Smith
Subject: Burndown - Above the line / Below the line
We use the value to clearly identify the number of hours +/- on the trend line in presentations as sometimes the scaling can be hard to identify the exact number. On Tuesday mornings we gather the burndowns for each track / workspace and manualy calculate the difference between the TODO bar and the ideal burndown for the day before which is Monday. We then overlay that on the copied burndown with a graphic. Calculating that number for 25+ burndowns tends to be time consuming. If there were a way to identify the +/- of the trendline, that would help save a lot of time. I've attached a screenshot to provide more context.
Original Message:
Sent: 01-16-2020 02:35 PM
From: Nik Antonelli
Subject: Burndown - Above the line / Below the line
Hi Jim,
I have been thinking about your issue and I am wondering how you would describe the value you are getting from knowing the daily difference between the actuals and the target. Could you give me one or two sentences on how you use this information and how it helps?
I have written many apps based on what customers want or ask for. Usually, I have to get a sense of the 'why' before I can suggest solutions.
Thanks,
------------------------------
Nik
Rally Sales Engineer
Rally Software
Original Message:
Sent: 01-15-2020 07:36 AM
From: Jim Smith
Subject: Burndown - Above the line / Below the line
Each week I compile a presentation of burndowns for our teams. When doing this, we found it valuable to identify how many hours above or below the line each project is.
This comes with administration overhead since the only way I know to obtain the +/- is to manually calculate the difference between the "To Do" hours and the ideal burndown line.
Is there a data field in Rally or easier way to accurately calculate the over / under on a burndown for a given day on a project?
I've attached a picture to place some context around my question.
Thank you in advance.