Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Two things about this I really like:

* The automagical guessing of missing estimates. Propagating the estimate for a subtask to other subtasks at the same level makes a lot of sense for a first guess, if I'm any good at task breakdown. The propagating up to the "aunt/uncle" tasks (i.e. siblings of the parent) is a bit stranger - seems like it should dramatically underestimate most top-level tasks, and I'd worry about the anchoring effect. Still, it makes it very convenient and quick.

Have you thought about visually distinguishing autoguessed estimates from manually entered ones? At least for leaf tasks, I'd like a reminder of what I have left to estimate. (You could propagate up the "degree of guessedness" to parent nodes, but you probably wouldn't want to, or it would undermine the usefulness of guessing in the first place.)

* The visual tree structure is nice. I like how the horizontal arrangement puts a natural limit on how deeply you can nest, and therefore discourages overplanning :)



Yeah I could see this function well if you have some option to set all tasks on the same level. Atm it feels kind of confusing though, and especially the "bubbling". I made this structure, then added an estimation to subtask 2-1-1, and all the other estimations were filled in. I didn't understand at all what was going on at first and thought I had hit a bug.

http://s12.postimg.org/xth7k6fi5/Screenshot_from_2015_02_01_...


same thing that confused me too. I estimated one subtask and all other tasks and subtasks of other tasks were estimated. This seems to be a case of preemptive overengineering.


> The propagating up to the "aunt/uncle" tasks (i.e. siblings of the parent) is a bit stranger

Time is propagated to siblings, if they have no estimates from their own children.

Un-estimated siblings will be given the average time of the siblings with estimates.

Time will also propagate down the chain, and will be split equally over the children.

In the end, it is mostly bullshit, but then again, so are all estimates...

> Still, it makes it very convenient and quick.

Exactly. Sometimes, the best way of getting the right answer is to give the wrong one...

> Have you thought about visually distinguishing autoguessed estimates from manually entered ones?

Oh, they are. See the icon in front of them in the tree view?

Bulls-eye: Your own estimate

Checkmark: Actual time

Arrow: Auto-generated projection

They all have a title-attribute with their type in case you forget.

> I like how the horizontal arrangement puts a natural limit on how deeply you can nest

:)

It doesn't though. Still, you can fit like 8 levels deep on a normal desktop screen, but in practice, I've never found a need for so much nesting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: