Use Case: I am a ScrumMaster and/or a Product Owner and my team's burndown suddenly spiked upwards. I’m looking for a report or view to differentiate planned vs added or changed work to find the culprit (not for command and control, just to understand what changed without bothering the whole team, or waiting for the next daily standup). It's possible I may have over-customized my views and now can’t see the trees for the forest. I want some view or report that you can drill-down into to see the specific details of what exactly got added or changed, as opposed to the simple burndown,/burnup trend bars/graphs that the dashboard, cumulative flow, estimation accuracy and others provide. (This used to be so easy to see with XPlanner)

Comments

  • I have the same problem. I can see the effort hours using Task Effort Quicklist report but I can't see ToDo hours changed or new tasks added.

  • One thing that might be useful would be to provide a "table" that goes with the burndown that shows the backlog items that are included and their ToDo estimates that make up the chart. This could then be easily compared to the previous day's chart.

  • Any implementation would be good as long as the software automates the comparison and highlights teh deltas (don't want to have to try and eyeball the diffs). Being able to see this is also helpful when a team member that added items may be OOO and the rest of the team is in standup looking at the burndown scratching their heads trying to figure out what happened.

  • I think this report is now available in Dashboards. it would be nice to have this as common report instead of hiding it in Analytics.

  • Would the Project Scope Change report give you what you want?

    https://community.versionone.com/Help-Center/Lifecycle_Reports_Overview/Project_Scope_Change_Report

  • Can't say for sure if those suggestions/solutions do it as my team stopped doing Scrum and if/when we use VersionOne it's only in some KanBan manner to see all stories in progress, with no sprints, commitments, retros, planning, etc., we're off the rails now, so the need for this for me personally is a lot less. We have Ultimate Edition so I looked at Dashboards quickly but it seemed to just show metrics - I could not click through to task lists with hours deltas. On the PSC Report, perhaps more use of the filters would give me what I sought. If the solutions allow for drilling through the story point estimate metrics to get to the detail of what stories and their associated tasks changed significantly "in terms of hours" from the sprint/iteration (see I forget even which it's called in Scrum) planning, it could be useful to the original intent and use case I outlined. Not to point blame, but to be able to quickly get to what changed from yesterday to today (or between any days in the sprint). Especially useful when there is a distributed team, and remote engineers of their delegate are unable to make a standup and the ScrumMaster and rest of the team are scratching their heads wondering "what happened?" to the burndown trajectory. Also good when new stopries, or sets of tasks, get snuck in. Call out scope creep.

  • Although not pretty nor quick, I think looking at the History associated with a Story would provide you with the answer of what changed. The changes are indicated with a + sign preceding the current value. Pressing the + icon displays the previous value. Easiest thing would be to check to see what stories changed prior to the standup then simply display the history details for those stories.

    On another note, In my experience, if the team doesn't know what each other is doing then more data isn't going to fix their problem.

  • V1 has so many screens, dashboards, and reports, I'm not sure which +/- you're referring to. During a standup the team would typically all be looking at the Standup Dashboard, or perhaps the TeamRoom TaskBoard view, which would be presented based on backlog priority order, and perhaps filtered per speaker. So it would be good to see any unexpected CRUD changes highlighted in some manner, vs having to go into each individual story and review History. Though I'm guessing that's not what you meant, that there is some view or report with +/- more in context with any changes across the sprint contents.

    I agree that more data doesn't solve team communication issues, but with distributed teams, or highly specialized teams, if even one person does not show up for standup and has changed something in isolation and had not communicated ahead of time to someone else on the team, it can cause a bit of confusion for the rest of the team present to communicate to each other what they have done, are doing, changed, etc. I suppose we could lock it all down more, and say that only the SM has edit rights, but with remote teams, and home office employees, we want the sprint burndown board updated before the next team standupfor unable to attend. It's not that perfect ideal co-located Scrum teams, but it's reality in today's global workforce. Also, I see my original UC was teh SM or PO looking at the board and wondering "what happened", whereas that could (hopefully) be explained by a team at their next standup. It's when the team members in attendance are all also out of the loop on the changes, and look to the expert VersionOne ScrumMaster to quickly identify the changes, so they can answer the occasional gutcheck question "Is the Sprint commitment still achievable?"

  • Thanks for pointing me to the Project Scope Change report, Terry D!

  • The Scope Change report doesn't calculate data based on a date range. It would be useful if it did, as that would better show a picture of what changed during the sprint.

  • Marissa F - Which version of VersionOne are you using? VersionOne Ultimate's Project Scope Change report does include a date range which is initially set based on the sprint selected, but can then be manually modified.

  • Ditto on Scope Change Report... Another option: My org added a custom field called Unplanned. It's a checkbox that we use to indicate if a user story was added to a team AFTER sprint planning. These stories tend to be higher risk, have the potential to impact committed work--in practice, another story "should" be de-prioritized and removed from the sprint if work is being added. It's also a great talking point to see X% of a given team's work ends up being unplanned--gives you the opportunity to identify stakeholders who you make need to coordinate with better, and also provides context if a portfolio item is behind schedule.

  • The V1 Detail tracking report? it provides the deltas (added, deleted, modified) at the story level, can specify your Project, your Spring, your Team.

  • Apologies, I had the wrong report name; the Project Scope Change report is what I was thinking of.