Estimating.

  • Why is it so painful, and why are we always wrong?
  • Why does the business need our estimates?
  • How can we be better with estimations?
Photo by Mikhail Nilov from Pexels

Why so much pain?

  • try to outline (in writing or in our head) a rough outline of the tasks/problems we need to solve,
  • Imagine roughly how much time each of those will take us, and
  • Add some time for any ‘unknown’ issues that might arise.

Why does the business keep pestering us for estimations?

how can we be better?

Break everything into tasks that are no longer than a day (SCRUM)

Don’t estimate (Shape Up)

Just add X%

Recomendations (let’s estimate better)

Change the scale

  • hours
  • days
  • half-months
  • months
  • half-years
  • years (although if you are estimating in years, you have more significant worries)

Reflect on your estimations

Be upfront with uncertainties

Conclusion

--

--

--

Full Stack developer @ Seraphin, learned how to code @ Le Wagon. I love coding and plan to keep learning as much as I can about it :)

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Learning Effective java-item27

Why does Rails feel so strange?

Conventional Commit messages in git

NodeConf Barcelona 2017, A Retrospective

Introducing MakerDAO Risk Dashboard

Improve Website Loading Speed with 07 Proven Ways | Next Gen Hosting Pakistan

Swift: Class vs Struct

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Pablo Curell Mompo

Pablo Curell Mompo

Full Stack developer @ Seraphin, learned how to code @ Le Wagon. I love coding and plan to keep learning as much as I can about it :)

More from Medium

Study case: managing an engineering team

Leadership Communication 1o1: How to Make Sure Your Messages Stick — Petra Wille

How Product Managers and Product Architects interact, matters!

Debt management in product teams