The only thing less complicated than a burn-down chart (story points or effort hours) to track progress within a sprint would be to just use the Scrum board as a basis for assessing where we are at. However, if we are looking at a release or project spanning multiple sprints, some sort of forecast against the overall backlog is needed and a burnup or burndown chart are good ways to do this...
Kiron
Kiron, this looks like complete different framework which needs more devotion and concentration I will stick with my plan for now and might consider it later after other achievements. thanks for your comment Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
You do not have to use it but I agree with Andrew, it is not complicated, it is actually very simple but Id rather use Burn Up charts as they reveal more info. You can use any information radiator that is sufficient and clear enough to show progress.
...
1 reply by Riyadh Salih
Sep 17, 2018 9:19 PM
Riyadh Salih
...
Rami, thanks for your comment yeah it looks like that different approach complete different set up, I might revisit it later
Saving Changes...
RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
Agree with Kiron & Sergio
...
1 reply by Riyadh Salih
Sep 17, 2018 9:20 PM
Riyadh Salih
...
Rajesh, thanks for comment
Saving Changes...
Shweta PaiScrum master| ResMedHalifax, Nova Scotia, Canada
Ultimately it depends on what you are trying to measure. If you are new at scrum then your 1st goal is to get the team adjusted to scrum. A lot of times, the scrum master has to work on the mindset of folks. Once the team has adjusted, then we can start looking at burndown/burnup charts. Burndown chart is the next level after your team is comfortable with the new way of working. For a new team, as a SM, I keep eyes on the burndown chart to see how my team is doing i.e. are we closing stories fast enough but I start having the discussions with the team once they have settled in. You don't want the team to close stories just so that the charts are perfect. Hope this helps.
...
2 replies by Riyadh Salih and Shweta Pai
Sep 17, 2018 9:23 PM
Riyadh Salih
...
Shweta, thanks for your feedback looks like you have master that very well, I always look for such matrix which shows real story.
Sep 18, 2018 8:34 AM
Shweta Pai
...
Glad you found it useful. For a new team, until we get the house in order, there is no point in measuring the next level because it would only demotivate them and we definitely don't want that.
You do not have to use it but I agree with Andrew, it is not complicated, it is actually very simple but Id rather use Burn Up charts as they reveal more info. You can use any information radiator that is sufficient and clear enough to show progress.
Rami, thanks for your comment yeah it looks like that different approach complete different set up, I might revisit it later Saving Changes...
Ultimately it depends on what you are trying to measure. If you are new at scrum then your 1st goal is to get the team adjusted to scrum. A lot of times, the scrum master has to work on the mindset of folks. Once the team has adjusted, then we can start looking at burndown/burnup charts. Burndown chart is the next level after your team is comfortable with the new way of working. For a new team, as a SM, I keep eyes on the burndown chart to see how my team is doing i.e. are we closing stories fast enough but I start having the discussions with the team once they have settled in. You don't want the team to close stories just so that the charts are perfect. Hope this helps.
Shweta, thanks for your feedback looks like you have master that very well, I always look for such matrix which shows real story. Saving Changes...
Eric IsomOwner| learn.pmguaranteed.comUt, United States
I highly recommend you start by reading "Scrum: The Art of Doing Twice the Work in Half the Time" for an excellent introduction and broad understanding of the principles and applications of Scrum.
Community Champion
