Burndown Chart shows zero for story points

I am testing the User Story Map features of VP and I think I am following the process correctly but when I come to the Burndown Chart for a Sprint the Story point shows as zero (using VP 16.3). Here is the process I followed:

  1. Make a Simplified 2 (3-level) User Story Map.
  2. Make some user stories, put them in Release 1, assign a user and add to the development backlog.
  3. Click Estimate and Spike and put the user stories on the affinity table.
  4. Click the Sprint tab and make a new sprint and add user stories to the sprint.
  5. Change the Sprint to Working.
  6. Click on the Burndown Chart.

At this point both the Estimated burndown and the Actual burndown show as zero. I expected it to show the points for the sprint as the estimated burndown starting value.

Other things I have tried are to synchronize it with Tasifier and change things in Tasifier. In Tasifier the user stories look like they are tasks but when I click on them there is an effort box with nothing in it. If I add subtasks and give them a value for the effort I think it changes that Actual burndown on the chart but the estimated burndown is still zero. I have not been able to get the estimated burndown to be anything other than zero.

I have not tried using the full Scrum Canvas and working through the examples for that.

Any advice on what I am doing wrong? Is it possible to just use the User Story Map like I am trying?
David

Here is the Burndown Chart.

Hi Dwaldo,

Thank you for your post. The two problems you reported are both forwarded to our engineering team for further checking. I will let you know when there is any update.

Best regards,
Jick Yeung

Hi Dwaldo,

Here are the steps to creating burndown chart:

  1. Create the user stories

  2. Add them to the development backlog

  3. [Optional] Perform affinity estimation

  4. Create a Sprint and add the stories into the sprint

  5. Assign user story to a Team. To do this:

i. Click on the first button in the bar of the sprint row:
image

ii. Create your team(s):
image

iii. Drag the user stories to the corresponding Team columns:
image

  1. Sync the user stories to Tasifier.

  2. Create sub-tasks from the “user story task”.

  3. For each sub-task, enter the Effort
    image

  4. Set the Sprint to Working. This generates the burndown chart

Best regards,
Jick Yeung

Jick,
I tried this and it works. I think the main thing is that when you change the Sprint from Planning to Working the burndown chart is created. So, if you have have no tasks then the effort is 0. You have to create tasks in Tasifier and put the effort for each task then change from Planning to Working.

Also, I thought that if I changed the effort for a task then the estimated burndown would update to a new value. But it does not. The Actual burndown changes but the Estimated burndown does not. It stays at the level that was there when the Sprint changed from Planning to Working.

Thanks,
David

The connection from Tasifier to the Sprints on the Sprint page is not clear. I tried changing the percent complete on one of the tasks but the Actual burndown on the Sprint Burndown chart did not change. How do I update the completeness of the tasks so that it shows on the burndown chart?

Hi Dwaldo,

Thank you for your reply. I have forwarded your question to our engineers. When there is an answer, I will let you know.

Best regards,
Jick Yeung

Hi Dwaldo,

The actual burndown is formed by considering closed tasks. The change of percent complete has no change to the figure.

Best regards,
Jick Yeung

Jick,
Thanks so much! That works perfectly. Thanks for answering my questions.
David