Think Twice Before You Plan Your Work as a Software Engineer

This is my first medium post so bear with me.

Lately, I’ve been toying with the idea of “overestimating” the tasks during our regular planning sessions. The motivation came from the book Essentialism by Greg McKeown that I have been picking up during the past couple of months. There have been other interesting ideas that relate to the field of Software Engineering but I will attempt to explain those in the future.

Role of estimations

Our Workflow

Why “overestimate”

But Why

A similar example is given in the book — students routinely underestimate the amount of time their work will take and end up suffering later as a consequence. Something quite interesting is that, if the estimations are provided anonymously, this bias towards underestimating doesn’t manifest. Another point for the argument that peer pressure plays a role here.

So there we have it — we have talked about why we plan our work as software engineers, how we go about doing so, what are some chinks in the armour of this process and what we can do to combat that.

I hope this has been useful.

Software Engineer