2 ms·
I thought that we’d solved this problem - don’t do estimates but rather adjust what we build to fit the available time. And estimates of what is going to be shi
by randomsearch 6y ago
I thought that we’d solved this problem - don’t do estimates but rather adjust what we build to fit the available time. And estimates of what is going to be shipped get more and more accurate as time goes on (because you can ship what you’ve already built), whereas estimates of time remaining can continue to be wildly inaccurate for as long as you like (scope creep etc).
Then the end of the allotted time you have a product. Maybe it’s not good enough. So you either give up or you allot more time to it. But the product should be usable as-is and solve some of your problems.
Problem I have with the above is that it requires developers to be honest and put in consistent effort, but that’s more of a leadership and motivation issue.
- idoby 6y agoI agree, but that's still a form of estimation though, you're just estimating that you'd be able to deliver on your list of features in the time you have. You could be wrong, and then end up with less features, or be forced to spend more time.
- waynesonfire 6y agoi don't think the claim was that we're no longer estimating. the author was attempting to articulate the process of estimation, where initially one promises the world in N amount of time. As N draws near you reduce feature / scope as needed.. and perhaps when the deadline hits and all you got is a int main(void) { printf("hello world"); return 0; } you figure out what you can make due with where you're at. i like this approach and it resonates with a lot of other great comments in this post.