(web.archive.org)

268 points behnamoh | 1 comments | 27 Sep 21 04:48 UTC | HN request time: 0s | source

Show context

entrep ◴[27 Sep 21 06:58 UTC] No.28667859[source]▶

Is this doable?

A better approach would be to break it down as much as possible. This has the following benefits:

  * You will identify tasks you haven't though of

  * You will get a better picture of the total effort needed

  * It will be easier to provide grounds for your estimates to stakeholders

  * Developers will see progress as tasks get closed

  * Commits can be traced to specific tasks

  * Better estimates for remaining work during sprint/iteration/what-ever-you-call-it

replies(4): >>28667980 #>>28667993 #>>28668420 #>>28668669 #

1. Scarblac ◴[27 Sep 21 07:21 UTC] No.28667993[source]▶

>>28667859 #

> A better approach would be to break it down as much as possible.

Better still is to do that, and then multiply the end result by π.

(as explained in the article, it's mostly to compensate for scope creep, and that isn't in your list of benefits)

↑

Always Multiply Your Estimates by π (2013)