How do you estimate time
-
How do you estimate time fir writing code? If your manager ask you to give him a time for something to be done?
My Name in English[^] Translation done By OriginalGriff
Experience. It's not an exact science - it's guess work based on "how long this took me last time" plus a bit of "how accurate and complete is the spec?" with a soupcon of "what else do I have to do at the same time?" and some extra "padding time to make me look good". Occasionally there is also "How much am I being paid for this?" and "how much do I like this guy and want to do this?" Complex. So about 8.73 working days, probably.
-
How do you estimate time fir writing code? If your manager ask you to give him a time for something to be done?
My Name in English[^] Translation done By OriginalGriff
-
Experience. It's not an exact science - it's guess work based on "how long this took me last time" plus a bit of "how accurate and complete is the spec?" with a soupcon of "what else do I have to do at the same time?" and some extra "padding time to make me look good". Occasionally there is also "How much am I being paid for this?" and "how much do I like this guy and want to do this?" Complex. So about 8.73 working days, probably.
-
Don't drink tea, don't smoke. So no. Coffee breaks are extra, natch.
-
So based on Griff numbers: (8.73 + 2) * 3 = 32.19 :omg:
My Name in English[^] Translation done By OriginalGriff
-
So based on Griff numbers: (8.73 + 2) * 3 = 32.19 :omg:
My Name in English[^] Translation done By OriginalGriff
No, no, no! You are supposed to think of a number, not me!
-
No, no, no! You are supposed to think of a number, not me!
-
So based on Griff numbers: (8.73 + 2) * 3 = 32.19 :omg:
My Name in English[^] Translation done By OriginalGriff
-
Isn't it a slandered timing for writing code
My Name in English[^] Translation done By OriginalGriff
Nope - stealing my numbers is plagiarism, not slander!
-
Nope - stealing my numbers is plagiarism, not slander!
-
How do you estimate time fir writing code? If your manager ask you to give him a time for something to be done?
My Name in English[^] Translation done By OriginalGriff
A slightly serious answer. Split it down into easily manageable task. Estimate each task. If the estimate is less than 1/2 day, round up to 1/2 day IF the estimate is greater than 2 days, split it into smaller tasks. Add the total. Multiply by 2 if I am doing it, or three if someone else (not because I am better but because there needs to be additional time for them to interpret, and for contingency if I missed anything) Round up to the nearest week or day depending how big it is. Add a couple of days for contingency. Present the estimate. Be prepared to negotiate. Note my time as I develop against each of the tasks - so next time I will be able to estimate better.
MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
You are joking right
My Name in English[^] Translation done By OriginalGriff
My lawyers will explain it all to you when they arrive. Shouldn't be long now...
-
My lawyers will explain it all to you when they arrive. Shouldn't be long now...
-
I'm out of here bye. Will deactivate my account :~
My Name in English[^] Translation done By OriginalGriff
You fed up with the Muslim Brotherhood already? :laugh:
-
How do you estimate time fir writing code? If your manager ask you to give him a time for something to be done?
My Name in English[^] Translation done By OriginalGriff
-
How do you estimate time fir writing code? If your manager ask you to give him a time for something to be done?
My Name in English[^] Translation done By OriginalGriff
Do a Work Breakdown Structure[^]. Estimate each item individually, and total them up. Add a buffer (10 or 20 percent, depending on experience). In an agile project, you can follow Planning Poker[^].
-
How do you estimate time fir writing code? If your manager ask you to give him a time for something to be done?
My Name in English[^] Translation done By OriginalGriff
محمد م. محمد wrote:
How do you estimate time fir writing code?
There's the fundamental flaw. A time estimate needs to include more than just "writing code". Documentation, debugging, unit testing, feature testing, QA testing, rewriting... So, break your requirements down into smaller chunks, recurse (and I do mean, re-Curse) until you feel like you can confidently make an estimation and if you can't, refine the requirements further. Then for every 10 hours of code writing, factor in: 1 hour for documentation 1 hour for debugging 3 hours for testing (unit, feature, QA) 2 hours for rewrite based on requirement changes and problems resulting from testing and having to update the tests and docs. For every 500 hours of coding estimates, multiply the above additional factors by 2 to compensate for increasing complexity. Marc
-
Evidence Based Scheduling[^] :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
Eddy Vluggen wrote:
That's a great article. Thanks for sharing! Marc