We're not using Scrum nor Sprints, but we would like to have a report that will help us to predict deadline and scope changes. Does that exist in JIRA?

Maria Soledad Cánepa June 24, 2016

We have a vert dynamic project with constant changes and we do not use Story Points, all with hours. We use FixVersions to do the planning and Epics to keep things categorize.

Also, we don't put estimates on main tasks but on sub-tasks (analysis, design, implementation sub-tasks, QA sub-tasks, etc)

Version Report is not providing good data, no predicted deadline or anything. Is there an way that we can use JIRA without limiting only to "Issue Tracking" tool?

Using JIRA Cloud here.

 

Thanks! And thanks in advance for any recommendation.

1 answer

1 accepted

1 vote
Answer accepted
C
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 25, 2016

maybe use sprints as weeks, and let the data roll over.   while you are not doing scrum, this will build the cadence to provide forecasting.   you can use issue count for forecasting. this can be accurate is the units of work are similar in size.

Maria Soledad Cánepa June 25, 2016

Do you mean, for each fixVersion create a Sprint that i'll close each week?

Thanks for your answer, btw.

Peter June 25, 2016

More like just create weekly Sprints and require your team to assign each issue to one.  You would then close the Sprint weekly and roll everything that is none Done to the next Sprint.

On Scrum boards, FixVersion and Sprint have no required relationship and are independent of each other.

By doing this, you would be able to generate burndown charts based on your estimated vs actual hours.

Maria Soledad Cánepa June 29, 2016

Thanks, @Peter Ho!. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events