Professional Developers Estimate Times | Passion for Coding. Being a great coder is only part of the skills required to be a professional developer. A professional developer is never isolated with the code. All work is done within the context of a project. A professional developer delivers not only high quality code, but also high quality time estimates. Back in June I wrote about programmers’ time estimates. With more than 100000 views of that post and a lot of interesting comments I want to take a closer look at a common mentality if developers. Time estimates are impossible. That mentality is totally incompatible with being a professional developer. As a professional developer I definitely have an interest in getting the estimates right, because if they are wrong some bad decisions are going to be made.
The product owner in a Scrum project is the one creating the prioritized product backlog. The problem with that description is that it is completely wrong. To enable the product owner to make an informed decision, a time estimate is needed. Estimating Times | Passion for Coding. If you’re reading this, you’re probably a developer. Being a developer myself and having worked with developers I know that one of the most dreaded questions for a developer is about time: How long time will it take to implement this? Most developer hates that question, simply because it is so hard to answer. Programming is about solving unknown problems. I’m often doing time estimations and I think I’m decent at it. One of the keys to improving any skill is gathering experience. This doesn’t look to hard, but there are quite a few fields in the database and forms. I’m not telling my estimate to anyone else and I make no commitment to anyone but my ego about being finished today. Another way to gather estimation experience is to perform disaster analysis.
Some tasks needed were simply forgotten when doing estimations. When I estimate a project I try to use methods to remedy the five reasons for disasters. A list of all the components that will be required in the system. Programmer Time Translation Table | Passion for Coding. An experienced project manager I used to work with claimed that he took the programmers’ time estimates, multiplied by pi and converted to the next time magnitude to get the true number. 1 day converts to 3.14 weeks. He had learned the hard way that programmers are bad at estimating times. To get a more precise conversion, I’ve created a translation table for programmers’ time estimations, trying to narrow down where things go wrong.
Time estimation is hard. Every programmer has an interval where the estimations are realistic. Going below that interval means that the overhead (building, testing checking in code) was overlooked. Going above that interval means that the task is too large to overview. For junior developers, the interval might even be non existing. It is also important to understand that experience in programming is not the same as experience in estimation. Eventually, every programmer will have use for estimation skills. Follow up a review with Face-to-Face meeting/webex. Job Scheduling vs Workload Automation vs Work Automation. Attack rather than Defend. Dhrityman should know all about your work.
Defects.