Does Jira support flexible sprint measurements?

[ori gal]

Do you know if it's possible to set the sprint measurements (velocity, predictably) to calculate from 'To do' to 'ready for deployment', instead of using all columns into the calculation? 

[Nic Brough -Adaptavist-]

Velocity is calculated as commitment (what is taken into a sprint) against what the team delivers.  Predictability and other measures are usually built from velocity amongst other things.

Jira considers the last column on the board to be thee measure of delivery.  If it's not in the last column, it is not done.  If it is in the last column, it is done.

There's no way to change that, you wouldn't be measuring velocity if you did it differently

There is an argument that you could define "done" as being a set of columns on the right, rather than just one, but that has the problem that multiple columns are of no use to the team, because once an issue reaches the first of the done columns, they don't care about its later status, so there's not really a lot of point in having the columns on the board.  I don't think Atlassian are ever going to implement that for Software boards.

[Bill Sheboy]

Hi @ori gal -- Welcome to the Atlassian Community!

Yes, and...to what Nic notes: You seem to be asking about a lower level of measurement than is typical for a Scrum team.  What problem are you trying to solve?

Rather than re-defining those typical Scrum measures, please consider looking at cycle time or lead time.  Cycle Time is a measure of time from a starting point to an ending point in your process.  For example, Build Cycle Time could be from start/end of development steps.  Lead Time is the overall time from issue creation until done and released to customers.  These measures include any *waiting time* between steps, so they can help uncover slow downs and focus improvement ideas.  Together, they provide fact-based predictability to help with forecasting.

Jira has a built-in control chart to see this information, which you may learn about here:

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

There are more sophisticated versions of such reporting available from the marketplace as addon apps, and I suggest investigating your needs and trying the built-in reporting before trying those.

Kind regards,
Bill

[Emre Toptancı _OBSS_]

Hello @ori gal ,

I guess you want to use the velocity chart to get some kind of analysis about the trend of time spent on individual (or a group of) statuses in your workflow.

Using the built-in Control Chart of Kanban boards might help with that since it allows you to inspect individual (not statuses but) board columns. Control Chart has limited transparency about its inner workings and offers limited flexibility but can give you a very good overall picture.

If you want more details and more flexibility, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. It is available for Jira Server, Cloud, and Data Center.

Time in Status allows you to see how much time each issue spent on each status and each assignee. 

    

You can calculate averages and sums of those durations grouped by the issue fields you select. For example average resolution time per week, month, issuetype etc.

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

 

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT