Auto-schedule is modifying orginal estimate according to the team hours allocation

Anthony GERARD
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 10, 2025

Hey,

We are working on a plan on a project. We tried the config Kanban and SCRUM and we have the same issue with the Auto-schedule feature.

1. We setup all the original estimate on all tasks of our board. 

2. We assigned a team to all the tasks that we created in the plan overview. For this team, we added 70 hours per week with 2 members (irl, 35 hours / week / person). 

3. We added all the dependencies between all these tasks. 

4. We have seen that the auto-schedule modified some estimated duration of tasks by "spending" some hours from the pool of the team. For example, a task that was initially planned for 2 days (7 hours per day), has been modified to 1 day (14 hours in one day). 


This issue is a big problem for our plan because for all our tasks, we can only have one worker per task and the fact that we have 10 employees in the developement will obviously not accelerate the development of the task by 10.

How can i add some constraints to the auto-schedule feature to only have one person (from the team set up) used per task and avoid any modification of the initial original estimate? 

PS: we also tried some modifications on the configuration of the auto-schedule like "dependencies config (Sequential/Concurrent)" or Inferred dates, ..., we always add the same issue.

Best regards

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events