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
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 question 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) Kanban dates align with the required GANTT 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?