Skip to main content

Why big tasks are hard to estimate properly and what to do about this.

I will begin this by stating clearly: you should never get to the point where you need estimate how long it will take a big task to be completed. You should never have big tasks in the first place. There are a lot of reasons why having big tasks is a seriously bad idea.

Firstly, big tasks have big requirements and by the time the developer is halfway there he will most likely have forgotten parts of the requirements. A developer working on a big task needs to keep the requirement fresh inside his mind each day. Otherwise if he forgets some things he won't implement them at all. This is an issue even where I work. So extra time is wasted just refreshing those requirements.

Secondly, big tasks tend to affect a lot of systems inside an application. Most developers don't know all the systems in the application so he might spend a lot of time figuring out how those systems work and how does his task affect those systems. A series of smaller tasks can be worked on in parallel and you get more flexibility when assigning developers to those tasks. You can choose for example developers that are experienced working on areas and systems related to those tasks. On bigger tasks it's almost impossible to find a developer that knows all the affected areas. Having more developers with better understanding of the implications of the changes will reduce the development time and number of bugs.

Thirdly, it takes a longer time for a big task to reach the testing period. A small task reaches the testing period faster which means that the testers will never run out of work.

And finally, smaller tasks are easy to fix because you have a smaller portion of code that you need to analyze for bugs.

No wait, there's more. Smaller task are easier to accurately estimate. Even if some of them takes more to finish, you can keep a ratio of 50/50 of tasks that are finished earlier and tasks that are finished later. If you keep that ratio and sum up all the time it took to complete them you will have a better change of being on track because everything will balance out.

All in all, I think that the extra time wasted to split a big task into smaller tasks is recovered later due to the things I mentioned above.
Labels:

Comments

Post a Comment

Popular posts from this blog

Some real soft skills which are useful as a developer

I keep hearing more and more that as a software developer you still need soft skills, that soft skills are more important than technical skills and so on. But no one really has any concrete ideas about what these soft skills actually mean as a developer. Everyone just keeps talking about them but I don't see anyone actually going into details about them with concrete examples. Not to mention that a lot of people are just trying to make money out of these things and when they say that soft skills are important it is usually followed by some self advertising about their soft skills trainings. And to make matters worse, some of these preachers, pardon people, don't have a lot of experience in the development field. Some of them are not that good developers and then they say, that not only technical skills matter but also soft skills. Maybe they are not so great developers because they also don't have good enough soft skills also. Now on to the concrete part of soft skills....
Post a Comment
Read more

Some software development common sense ideas

 I haven't really written here in a long time so it's time to write some new things. These are just some random common sense things that seemed to short to write about individually but seem really interesting and useful to me or other people 1. There is nothing fixed in software development, all things vary by circumstances and time Remember the documentation that didn't seem that important when you started the project, well after a couple of years one the application has grown and become really complicated, no one actually knows everything about the application anymore. So now you really need that documentation. What happens if you suddenly need much more people to develop the application because of some explosive growth? Without documentation, new developers will just look at the application like they look at a painting. This actually happened to me. Maybe in the beginning of a project, a technology really helped you a lot but as the project grew, it started making things...
3 comments
Read more

My experience joining Microsoft, one of the leading companies in the industry

 This past year I finally made a big leap in my career and joined on of the leading companies in this the software industry, it's been one of my lifelong dream to join such a company and now it happened. It's been quite a journey and I noticed a lot of things so far that I would have never imagined.  Firstly, the scale of things is something that completely blows my mind. I never thought that I would be part of tens of teams, just in my local division in geographical region. Everything is massive and scattered around the globe with hundreds of teams out there. And getting so many teams to work together is really a challenge, especially making sure that they don't constantly reinvent the wheel.  Or another very challenging aspect is the fact that no team is actually alone and depends on the work of many others teams. Here I noticed several skills that are really useful which I never though of before. One of the skills is getting the right information and reaching the...
Post a Comment
Read more