We got tired of not being able to accurately answer "When will this be done?" and "Will anyone be required to work overtime on the current schedule?", or spending too much time in meetings and standups trying to answer those questions. Just opened up for beta. Would love some opinionated developers to guide future improvements (or feedback on the general idea).
Probably not as interesting now that you can play with the actual tool, but we also wrote several blog posts describing our thinking and goals for solving this problem:<p><a href="https://www.expectedbehavior.com/building-burndown/keep-the-big-picture-separate/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/keep-the-...</a><p><a href="https://www.expectedbehavior.com/building-burndown/schedule-important-work-first/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/schedule-...</a><p><a href="https://www.expectedbehavior.com/building-burndown/many-hands-make-light-work/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/many-hand...</a><p><a href="https://www.expectedbehavior.com/building-burndown/where-tasks-and-projects-go-to-die/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/where-tas...</a><p><a href="https://www.expectedbehavior.com/building-burndown/you-can-only-learn-from-your-mistakes-if-you-know-what-they-are/" rel="nofollow">https://www.expectedbehavior.com/building-burndown/you-can-o...</a><p>This is just v0.1 of the tool, so we haven't solved/built all the above yet, but maybe it shows some of our thinking process.
$10 per user/per month. That's insane, the problem you're trying to solve is a leetcode medium problem statement and should not cost this much.