Is filling in bespoke timesheet systems to appease the Client. Enter your hours against a specific contract number, job code, TFS code or whatever.
It's fine if you have a job code, but if your work dries up, what do you put into the tool?
Seems to be the same pattern for me. Run out of work, tell client. Client mumbles something about more work in the pipeline. Nothing happens.
Then the "what are you currently working on?" discussion. "Errm, I'm doing some structured reading on WCF and exception shielding".
tulip hits the fan.
I did tell you I was bored. No you never. Yes I did.
I might have something more to do in a weeks time after the first round of SIT is complete, but for the mean time I'm slack. And I know that conversation is coming, and I'm dreading it.
It's fine if you have a job code, but if your work dries up, what do you put into the tool?
Seems to be the same pattern for me. Run out of work, tell client. Client mumbles something about more work in the pipeline. Nothing happens.
Then the "what are you currently working on?" discussion. "Errm, I'm doing some structured reading on WCF and exception shielding".
tulip hits the fan.
I did tell you I was bored. No you never. Yes I did.
I might have something more to do in a weeks time after the first round of SIT is complete, but for the mean time I'm slack. And I know that conversation is coming, and I'm dreading it.
Comment