Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,375
Community Members
 
Community Events
176
Community Groups

Kanban, Prediction and linkage to a GANTT chart

Edited

Hello community, interested in your feedback. So we have Kanban teams, each focuses on a key area of functionality, each with its own backlog of tickets drawn from various epics. Now, some of those epics are part of larger programs that have required delivery dates. So the overall objective in my mind is how to blend Kanban methodology against tickets that sit on a GANTT chart? 

My thought is this. A ticket could contain two pairs of dates within it. It could have a required start/end date pair, specified by a project manager, that supports finish-to-start type dependencies, and appears in a GANTT chart. The second date-pair could be a Kanban start/end date which is read-only and calculated by Jira, based on the ticket's position in the backlog and the velocity of the Kanban board. 

The Kanban product manager's job is to monitor those date pairs, and adjust the position of the ticket in the backlog, until the calculated (aka predicted) dates align with the required dates. 

In this way, we preserve the benefits of Kanban but get the predictability required of work that has time-sensitive dependencies in a larger epic/program. 

Am I over-thinking this? Are there better ways? Can Jira support the calculation mentioned?

1 comment

@Curt Pearlman 

I have exactly the same problem and looking for solution. 

Have you solved it?

Comment

Log in or Sign up to comment