[raw_anon_1111]

Nope. As far as the client is concerned, payment is delayed until the requirements are met that were laid out in the statement of work. They could care less how many hours were put in.

I personally have put in extra hours to complete a project for a client that I did the proposal for as the SME in the technology because I underestimated. I’m a salaried employee for my consulting company and didn’t get paid extra.

Our consultants in Brazil and Mexico though while they also don’t have to track their hours for our benefit. They have to get approved to work over 8 hours a day because of labor laws in those countries. I can imagine that if they might do more granular tracking so they can justify the need to work (and get paid) for more hours.

As a team lead, I’m just going to track Jira stories being done on time if I need to be on the approval chain.

I have heard about projects at my current company where we have to give the client free work because the requirements weren’t met within the time allotted. I’m sure there were internal retrospectives where we had to go through our Jira board and see why stories were mis estimated or whether sales underestimated.

But even that falls on the implementation side because one of the staff consultants or engineering manager has to sign off on an SoW before it goes to the client.

Even during the retrospective, no one is trawling through Salesforce for details. We are looking at Jira.

I’m not saying we don’t track work output. I am saying we aren’t tracking granularly in our time tracking system that is only for billing clients. No one is expecting us to track every hour.

[pjmlp]

Usually that only works in Time-and-Material projects, and where management does a hard line with the original SOW, and the final delivery actually matches the original SOW.

When they don't, there are those hardliners that want a justification what they were paying for.

[raw_anon_1111]

This is true. The three consulting companies/departments I have worked for have had T&M projects that are SOW based and staff augmentation projects.

I said in another reply (don’t remember whether it was to you or not) that I avoid staff augmentation projects for a lot of reasons.

But if you are in consulting and doing SoW based work, it’s a dereliction of duty by your tech lead not to insist on signed change order if the requirements veer materially from the SOW. It puts your company at risk of not being paid and/or having to do free work.