Search
English

How to answer development estimate questions without guessing: give a range based on screen count and past results(qiita.com)

startupxo Discuss

Writing language: KoreanRead in the original language

Plain summary

- A Japanese developer (a Qiita author) proposes that when asked for a development estimate, you should not give a single gut-feeling number, but calculate it as number of screens × effort per screen. The author believes a number once spoken easily becomes the baseline against which the formal estimate is compared later. - Effort per screen is not a guess. It is the average obtained by dividing the total effort of past projects by their number of screens. Design, testing, batch and API effort are also included in the total effort and absorbed into the average, and the team fixes the rules for counting screens. - Because an estimate is a prediction, the author says to convey it as a range with three values: optimistic, most likely and pessimistic. The article's example (a hypothetical for explanation) is 8 to 18 person-months, an expected value of 11 person-months, and a line of about 12.7 person-months at which the work finishes with roughly 80% probability. - The author recommends placing commitments and budgets at the roughly 80% line, not at the expected value. The business side can reduce the amount and the range by cutting screens or finalizing specifications early. The author adds that for large projects effort per screen grows and productivity differs by team, so adjustment is needed.

Read source ↗

Found on

Qiita ↗ / Published by source

Have you run into something like this? Tell us in a line or two what you did. You do not need to know the product.

Sign in to comment

Keyboard shortcuts

Choose a post with J and K or the arrow keys, then press Enter.

K ↑ / J ↓
Previous post / next post
Enter C
Open summary and comments for the selected post
O
Open the original link of the selected post
/
Search
?
Show this help
Tab
Move to the submit or comment button, then press Enter

Type normally in text fields. Tab and Enter are always available.