You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We're interested in using Advanced Roadmaps, but are trying to investigate what is required in order to get the value out of it that we're looking for (creating visibility into and estimating roadmaps, dependency mapping, tracking if things will be delivered on time). Some of our times are using Agile boards, and are pointing their stories. For teams on Kanban boards, do they have to point or use time tracking in order to provide the insight we're looking for? Or can Jira look at average cycle time for estimates?
We've been using a combination of both straight "waterfall" estimates (days, weeks, deliverables) and agile (points). We haven't gone so far as to use the autoschedule feature just because it doesn't seem to give us the results we want and I haven't had time to play with it. But with the ability to simply add a Gantt that is days long we use that for the waterfall stuff.
For the agile stuff, we have split the epics into placeholder stories that represent the total number of points of the epic. So, for example, an epic that is 20 points we might divide into 4 5 point stories. And then each story is represented by a sprint-long Gantt. That allows us to group by Teams and see from advanced roadmaps when stuff will get done without going over capacity.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.