Sometime back, I read a blog stating that everything that goes wrong in a project can be traced to a commitment made by someone at some point of time. This is quite true. Let me share one experience with you.
In one of my previous projects, we found that the quality of resources that we are getting to staff the project was of very bad quality. Some resources were taken on board without having in depth technical know-how. This was not very apparent in the initial days of the project. But as the project progressed, there were certain team members whose efficiency was questioned. The project seemed like moving towards failure. Top management stepped in and tried to augment the resources. Experts were called in. After months of late nights and mail fights, somehow the project was completed.
Now, it was time for introspection for what went wrong and what went right. Though people were groping in dark to figure out what went right, everyone was sure of what went wrong – Not having the right people. It was written down and notes circulated and presentations made. The blame game continued. People were crying for the throat of the HR team which had staffed the project. Some were saying that the quality of input deteriorated because the screening was not good. All guns were pointed to the HR folks and their processes. But the trace back does not end here.
The question is why did the project staffing folks get such guys in the project? This can be traced to the discussion which happened between the project manager’s boss and the HR manager. The organization had got a huge project and the manager wanted to complete it within a specific time. The sales folk had committed that they can do it. They had revenue targets to meet. No one really focused if the organization had the required number of resources with correct skills. With the deal sealed and contract signed, the delivery date was fixed. Now a mad scramble begun for resourcing. Rapid action teams went out to scout for talent. They had their targets to meet. So they got whoever knew how to spell the language and asked them to work on the project… and the project was doomed for you know what…
In one of my previous projects, we found that the quality of resources that we are getting to staff the project was of very bad quality. Some resources were taken on board without having in depth technical know-how. This was not very apparent in the initial days of the project. But as the project progressed, there were certain team members whose efficiency was questioned. The project seemed like moving towards failure. Top management stepped in and tried to augment the resources. Experts were called in. After months of late nights and mail fights, somehow the project was completed.
Now, it was time for introspection for what went wrong and what went right. Though people were groping in dark to figure out what went right, everyone was sure of what went wrong – Not having the right people. It was written down and notes circulated and presentations made. The blame game continued. People were crying for the throat of the HR team which had staffed the project. Some were saying that the quality of input deteriorated because the screening was not good. All guns were pointed to the HR folks and their processes. But the trace back does not end here.
The question is why did the project staffing folks get such guys in the project? This can be traced to the discussion which happened between the project manager’s boss and the HR manager. The organization had got a huge project and the manager wanted to complete it within a specific time. The sales folk had committed that they can do it. They had revenue targets to meet. No one really focused if the organization had the required number of resources with correct skills. With the deal sealed and contract signed, the delivery date was fixed. Now a mad scramble begun for resourcing. Rapid action teams went out to scout for talent. They had their targets to meet. So they got whoever knew how to spell the language and asked them to work on the project… and the project was doomed for you know what…
No comments:
Post a Comment