Automatically estimate a release of sprint

[Julia Hwang]

Is there a way to automatically estimate a projected release date of a sprint considering these factors:

- automatically calculating the sum of the original estimates in the sprint

- number of resources on the team

- holidays/vacations of the team

[Danut M _StonikByte_]

Hi @Julia Hwang,

Welcome to the community!

Sprints in agile are by definition time-boxed (2-3 weeks long). What you should do, is to adjust the sprint scope (amount of work planned) to fit the sprint duration and the current team capacity, not to extend the sprint...

And what you should estimate is your entire release, not individual sprints. 

Jira does not provide a way to estimate a release. You could eventually search on Atlassian Marketplace for a plugin that provides such tool.  

In case you want to estimate a release by using a plugin, our Great Gadgets app offers a Release Burndown Burnup Chart gadget that can predict the ETA of the release based on the current team velocity or an expected velocity.

 

You could use this to estimate the current sprint, but again, this is not a good practice...

Danut.

[Pasam Venkateshwarrao]

Hi @Julia Hwang 

welcome to the community

• First, make sure the "Estimation" feature is enabled for your project in Jira settings. 
• Assign Estimates to Issues:

  Before starting a sprint, each issue within the sprint should have an individual estimate assigned in terms of story points or time. 
• Sprint Planning:

  During sprint planning, based on the team's capacity and historical velocity, select issues from the backlog to fit within the planned sprint timeframe. 
• Use the Burndown Chart:

  Once the sprint is underway, monitor progress using the burndown chart, which visually represents the remaining work against the sprint timeframe, allowing you to identify potential issues and adjust estimates if needed. 

  Burndown chart: Track the total work remaining and project the likelihood of achieving the sprint goal. This helps your team manage its progress and respond accordingly.

[Julia Hwang]

Thanks @Pasam Venkateshwarrao !

The burndown chart is great! However, it doesn't directly account for the number of resources on the team. Rather, the number of team members influences the chart and how steep or flat the burndown rate it. Do you know of any plug-ins that take the number of resources directly into consideration? This way, we can identify if we need to add more people on our team.

[Pasam Venkateshwarrao]

@Julia Hwang Yes i can suggest Bigpicture  can significantly support resources' planning and balancing processes on individual and team levels

Hope this helps