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
Next: Root
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.
Our team is too large and handling both new features and production issues, making Scrum not really suitable. We like the Kanban board so far.
1. How do you estimate work to be done over X time periods so you have an idea on a release date target?
2. How do you show work completed (in various phases such as Investigation, Development, In QA) to management if there are no velocity reports?
3. Is there a way to setup sprints in combination with Kanban (is this Scrumban?)
Basically looking for other's expertise on using Kanban and being able to plan work and report efforts done. Thank you!
Thanks Gabriel. Our team is too large to use scrum, we are also tackling new features with bugs and production customer issues. They don't want to break the team into separate groups for scrum...so I'm wondering how best to use the Kanban board with Sprints?