Is this normal?

[NickFitz]

When I first started my current gig, mid-project, I was encouraged to double the time I estimated for tasks on the grounds that I had to learn about existing libraries and so forth. After a few weeks I was on top of the existing codebase, so I started giving realistic estimates during a planning meeting.

The product manager looked rather disconcerted, but after questioning me on the first couple of estimates he started just doubling my estimated hours for each task as he entered them into his spreadsheet

Now I just triple all my estimates and everybody's happy

[DimPrawn]

No one likes a rush job.

[Troll]

so I started giving realistic estimates during a planning meeting.

What!!!

Now I just triple all my estimates and everybody's happy

That's better!

[kirk]

the PM on the project I'm working on at the moment estimated 1 day for some documentation updates - by lunchtime today I had been pulled into two meetings and hadn't even looked at the documentation which needed to be completed today. 15:30 comes round and I finally take a look - 2 hours later, doc's completed! Lesson learned: PM's always over estimate, that way if it takes less time, all looks great!

[beaker]

I started a new contract on 1st November and I have done absolutely nothing!!

I'm in the same boat, but I started 1st March.

You'll learn to cope.

[ladymuck]

I had a contract where the last three months were spent thumb-twiddling. Local council, handing over my role to three (yes, count 'em, three) permies. There wasn't enough work to keep me occupied full time, bless their cottons. Took three months for the hand over to complete and I spent most of it plundering the depths of the Internet while they did the work and asked inane questions.

[MobileCheese]

Its usually the same most contracts, I try to make the most of it and use the time to brush up on skills, nothing better then getting paid for increasing your own value But also you can't sit on your butt you need to help you boss without him asking.