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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How do you estimate and show work using Kanban?

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!

1 comment

Hi barbara!

I am curious to know why SCRUM cannot fit with your team size?

How is your team structured? Isn't there a dev team and a maintenance team?

As for your questions:

1. This might help you if you have a server instance of Jira :

2. I believe the metric "time in status" could help you figure out some sort of velocity:

Again, server instance only :(

I also read a bit about the control chart and I believe it could be something useful if you get to understand it. 

3. I suggest that you read a bit about those two sub set of AGILE because they are based on different principles.

I hope this help a bit but I am looking forward to seeing more users respond.



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 I'm wondering how best to use the Kanban board with Sprints?


Log in or Sign up to comment