Hi, great questions! > How does this handle concurrent distribution of work? For example, my team has an upcoming epic which would take 3 weeks if done sequent

Hi, great questions! > How does this handle concurrent distribution of work? For example, my team has an upcoming epic which would take 3 weeks if done sequentially by one person. But what if the team has 2 devs, or 4 devs? Does it assume a linear decrease in work with increase in number of devs? It's for this reason that Easy estimate works best with "Story points". It does not matter how many devs worked on the epic, but looks at the total story pointed completed for the project in the past and predicts the ETA based on the work completion. * Does it handle task dependencies? For example, there may be a sequential chain of dependencies in my epic that mean it will never be done faster than 2 weeks no matter how many people work on it. This is a project-management-hell and hard to get it right. Your best bet is to create a "techincal spike" ticket and try and answer all feasibility and dependency questions and manage risk. Then create smallest and realistic tickets from the spike and estimate the work required to be done by story-pointing them. Easy estimate then takes over to continually track the project status and project ETA. > Does it maintain the roadmap in response to ongoing delays or changes to scope? For example, if a task is delayed by 1 week, does it go through and figure out the new ETA? This may be quite complex as it may be efficient to re-assign devs to different tasks. As this is story point based, not completing work in a week would result in a drop of the velocity, making the app compute a new ETA. So yes, at all times, the app is computing the best eta based on the project velocity and shows how the project fares given the project due date. > Does it handle annual leave and varied working weeks? For example, if the end of the project is pushed back into a week where lots of people have annual leave, can it factor this into its estimate? This again is factored in as the velocity drops during annual leave of a team member / lots of people on annual leave, creating a delay in the project ETA