Menu
I am a PHP developer, and I often have no idea in terms of days--let alone hours--how long something will take me at work. I am often writing new stuff, merging it with old legacy crap. I can tell my boss what week I will likely have something done--and maybe what half of what week--but I how in the world am I to know specifically what day something will be done? Isn't that a bit unrealistic, considering that bugs and other unknowns often arise and eat time? I can only minimize these things so much...
I am thinking of saying the following:
"Look, i understand that me saying "tomorrow! tomorrow!" is not helpful. The best I can do for you on many things I'll work on is tell you what half of a given week I will likely have it finished. and if it looks like I can possibly have it done by Friday of the given week, then we better move to the next week."
642
To calculate days in inventory, divide the cost of average inventory by the cost of goods sold, and multiply that by the period length, which is usually 365 days. Calculating days in inventory can help show whether a company is operating efficiently or not.
Days in inventory is calculated by dividing average inventory (in dollars) over a given time by cost of goods sold (COGS) during that period and multiplying the result by the number of days in the period (typically a quarter or a year).
A common way to calculate the cycle time is to take the total number of paid man-hours in a month, and divide that by the number of finished products produced that month. This gives the amount of time required to produce one item.
In the Date & Time Wizard dialog window, switch to the Difference tab and do the following: In the Date 1 box, enter the first date (start date) or a reference to the cell containing it. In the Date 2 box, enter the second date (end date). In the Difference in box, select D.
Time estimation is hard.
But the times when I've done this well all have a couple things in common:
1.) I received very good and complete requirements for the project. This is important and you should ask the tough questions to make sure that the requirements really are as complete as possible.
2.) I broke the project down into sections, wrote each section on a white board, and then estimated the time for completion for each section individually. I had the rest of my team contribute as I do this so I don't forget anything. This seems so simple, but it works so well. I think it allows you to be more realistic by reducing the possibility of overlooking a part of the project that may be time consuming. If you can write down and plan out the project at a granular level like this it'll help immensely.
During this whole time estimation process you may even gain a better understanding of the project and what needs to be done. That can prevent mistakes, writing & re-writing code, etc. And that's good for everybody.
134
Go with your hunch and then add 50% time. You'll meet the deadlines, won't stress yourself, your boss will see quality code over fast code and you'll probably be faster than expected once in a while. Everybody wins :)
21
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
