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
- 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)
