burndown | Burndown before you burnout.

1. Story points are not measurements of time, so no. Story points have an approximate correlation with time when we have a consistent team in a consistent context. Then the correlation is close enough that we can say that a team completes some number of story points in a period of time like 2 weeks. That is as specific as we can get. Any individual backlog item will vary too significantly to make a points-to-time comparison. This may seem frustrating, but it was specifically designed to subvert this type of time estimation.

2. Yes, absolutely. In fact, most teams in most contexts will find that multiple people working on an item in the backlog is the most effective way to work.

3. That's a pretty good rule of thumb. Think of it more like "experience has shown that...". Past that, there are no real rules around sub-tasks. They are there for the team or organize their own work. Make them as big or small as the team finds useful. You don't even have to use them at all. Also, to the previous point, it doesn't actually matter what the estimates or actuals for the sub-tasks add up to and there is nothing that says you even need to estimate them. Most teams I've worked in find estimating sub-tasks to be wasteful.

4. Yes, you are correct. A backlog item that takes multiple days to complete will not burndown until it is all done. That is intentional. This comes from a long history of work being "almost done" for a large percentage of time that it is in progress. By looking at done as a binary state, it creates incentive to finish items before starting others.

You also ask about structure. User Stories are a way of expressing the need of a user. In the example you give, I would assume that a Business Analyst is an end-user. I would also assume that this User Story is strictly describing work to format existing data. A best practice is to also add a "so that" to the end like "so that I can see trends over the past 4 quarters". It's important to keep in mind that User Stories are not a specification. They are a narrative that the team draws from to design an experience in their product. If that isn't what you're looking for, Scrum does not require you to use User Stories.

One way to do it would be to store the plot as a figure in the static folder of your Flask app folder structure and then display it on using an image reference in your html template. Something like this:

The built-in TFS burndown it according your Tasks, not the PBIs, see here more info.

In Azure DevOps Server 2019 and above you can add burndown chart according to Story Points:

https://docs.microsoft.com/en-us/azure/devops/report/dashboards/configure-burndown-burnup-widgets

There was in the past an extension Real Sprint burndown that is a chart for people using story point estimations per PBI, but I see now it's unpublished from the Marketplace.

You can go to his GitHub and try to build it and use it.

I found out the more effective way is to use another OData endpoint WorkItemBoardSnapshot where I can do server side groupby which is far more efficient than doing it in Power BI.

Here is some reference:

Sorry, it's not available right now. What you are looking for is a filter such as below:

We already had a raised feature request in our Develop Community user voice site:

Epic / Feature Burndown Chart

https://developercommunity.visualstudio.com/idea/964703/epic-feature-burndown-chart.html

You could kindly vote up it and monitor the status, our PM will review them.

Just a suggestion. You can make qa to work on previous sprint code. Lets say . Sprint 1 - Developed Something. Sprint 2 - Cut a Branch with sprint 1 changes and assign it to qa to test meanwhile developer can proceed with further development. Repeat the same proces in further sprints.

This way both qa and developer will be busy with their work without clashes.

Update

It appears the Done status was not in right-most column of the sprint board.

In Jira the issue journey should start from the Backlog or the left-most column of the board and build it's way to the right-most column. Reaching the right-most represents items in a 'successful' state.

Once you map the Done status to the right column then Burndown chart will be updated.

Original Answer

I'll explain how the burndown chart is displayed:

Estimation statistic: The vertical axis represents the estimation statistic that you've selected.

Remaining values: The red line represents the total amount of work left in the sprint, according to your team's estimates.

Guideline: The grey line shows an approximation of where your team should be, assuming linear progress. If the red line is below this line, congratulations - your team's on track to completing all their work by the end of the sprint. This isn't foolproof though; it's just another piece of information to use while monitoring team progress.

From your indication that the red line in the burndown chart only went down when one issue was canceled, which means that issue has an estimation.

Understanding the estimation statistic

On the left side of the chart you'll find the estimation for the burndown:

1- shows that the estimation used for this burndown is story points.

Check what your estimation is, and verify that all the done issue has value using that estimation strategy

On the queries results, I didn't find a way to convert the size (S, M or L) into a numeric value to display on charts.

We do not have any built-in feature about this.

For create a burndown chart, you need to use Remaining work/Story points on tasks (and bugs if they're managed with tasks) to populate burndown data. Additionally, the dates on those work items matter. To calculate burndown we're using an "as of" query that asks what the work item looked like on a specific day. For example, we're asking what the remaining work of tasks of User Story.

More details please take a look at our official doc here-- Configure and monitor sprint burndown

As a workaround in your scenario, you could export your work items to Excel. Then use Excel report to achieve what you need.

The Burndown Chart report on Jira's sprint board tracks the progress of all issues in sprint. To view two separate reports you have to create two separate scopes (one per project) and add them to two different sprints. You can run parallel sprints in Jira, just make sure that the Parallel Sprints checkbox is checked in Jira configuration.