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 should we do capacity planning and auto scheduling with multiple member kanban teams?

We're working on moving to Advanced Roadmaps from Microsoft Project for our cross-team project planning and roadmaps. The issue we've come up with is that the autoscheduler and capacity settings don't seem to take multiple team members doing multiple projects simultaneously. 

Here's a simplified scenario:

  • Kanban Team A has 3 members who each have a capacity of 30 hours/week giving the team 90 hours of capacity
  • Project 1 is estimated at 30 days (assignee A)
  • Project 2 is estimated at 30 days (assignee B)
  • Project 3 is estimated at 10 days (assignee C)
  • Project 4 is estimated at 20 days (assignee C)

What we're seeing is that:

  • Advanced roadmaps rightly sets the team capacity at 11.25 days/week
  • Unfortunately it schedules the projects sequentially with: 
    • Project 1 taking 2.6 weeks 
    • Project 2 taking 2.6 weeks following project 1 
    • Project 3 taking less than 1 week following project 2 
    • Project 4 following project 3
  • It appears the assumption when autoscheduling is that all team members are working on the same effort as opposed to each team member working on different efforts
  • Having different assignees for the epics doesn't impact the scheduling

When assigned to different team members what we believe should happen:

  • Project 1 would take 8 weeks (30 days at 30 hours/week)
  • Project 2 would take 8 weeks (30 days at 30 hours/week) concurrently with project 1
  • Project 3 would take 2.6 weeks concurrently with 1 & 2
  • Project 4 would take 5.3 weeks starting after project 3, concurrently with 1 & 2
  • All projects would complete at the same time

The questions:

  • Is there a way to have capacity equally split among multiple epics within a team?
  • Is there a way to concurrently schedule work based on the assignee? 
  • Has anyone found a workaround other than single member teams? (this feels like an anti-pattern we don't really want)

2 answers

1 vote
Nataliya Vasyliv
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Apr 26, 2022

Hi @Kerner 

Could be Team capacity a workaround for you? The ActivityTimeline plugin has a Team Timeline, that provides users of ActivityTimeline with an extra level of flexibility when it comes to planning team’s work, as it allows to schedule work not only for individuals but for the team as a whole.

ActivityTimeline provides a work scheme - a work schedule that can be assigned to a single individual or to a group of people, that defines their working days as well as the number of available hours during these days. 

Workload could be split between two or more issues. Via Bulk reschedule there is a possibility to schedule tasks based on the assignee. 

You can try a trial or we can provide a demo session for you if needed.
Best, Nataliya

Given this feature request, my guess is that there isn't a good option here.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events