search

adam-jw-casey / beavor

MIT License
1 stars 0 forks source link

Feature: Built-in PERT-style time estimation #24

Open adam-jw-casey opened 11 months ago

adam-jw-casey commented 11 months ago

Convert time needed to an enum, with a struct variant that takes an optimistic, mid, and pessimistic time estimate, and produces a best estimate using (O+4M+P)/6

adam-jw-casey commented 10 months ago

There are two ways this could be implemented:

  1. Purely UI: When entering a time estimate, the user is prompted for optimistic, mid, and pessimistic estimates. This is converted to a single value, which is stored in the task as currently.
  2. Concretely: As above, but all three estimates are stored, and could be used for probabilistic calculations. This could have very interesting interactions with #50 and #78 .
adam-jw-casey commented 8 months ago

The UI for both of the options above would be approximately the same. The only difference might be that the existing optimistic/mid/high estimates would be displayed when clicking on the time estimate for an existing task.

But this would be much easier to implement with no interaction with the database, i.e. as a feature the user can (or must) use for time estimation, but that doesn't exist at rest.