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.
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.
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.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs