Estimasi iku sulit amarga perangkat lunak penuh karo sing ora jelas. Tujuane dudu presisi palsu, nanging rentang sing realistis, dikomunikasikake kanthi jujur sing nulungi bisnis ngrencana. TL sing apik ngira-ngira rentang, ngungkapi risiko, lan nggawe ramalan maneh nalika sinau.
Carane ngira-ngira luwih apik
✓ Break work down — small tasks estimate far better than big ones
✓ Estimate as a RANGE or confidence ("2-4 weeks, 70% confident")
✓ Include the invisible work — testing, review, deployment, unknowns
✓ Use history — what did similar work actually take?
✓ Involve the people doing the work — not just you
✓ Separate ESTIMATE from COMMITMENT (deadlines are negotiated, not guessed)
Conto konkret
Ketika ditakoni "berapa lama untuk dashboard anyar?", aja ujar "rong minggu." Ujar: "Pekerjaan sing kondhang kira-kira rong minggu. Ana sing ora jelas babagan API pelaporan, yen bersih, rong minggu; yen ora, luwih cedhak patang minggu. Aku bakal ngerti luwih akeh sawise spike sedhela."
