Project Management

Please login or join to subscribe to this thread

Rating team cross functional team members based on success or failure of the project.

linkedin twitter facebook   Information Technology   Resource Management   Talent Management  
avatar
Srikantha R Manager Agile Program Management| Publicis Sapient Bangalore, Karnataka, India
Hi All,

Recently i came across a situation where I need to rate project team members who have worked on same project. But the project didn't do well in terms of cost and schedule due to lot of technical and resource challenges from one of the functional team.
It was a project executed with two different domain functional team (say A and B). While one of the team (A) is able to execute their share of work within approved cost and schedule, the other team couldn't achieve due to various challenges both from internal team (B) and external client side.
The members of team A obviously expects good rating since they have completed the given task on time and schedule with accepted Quality. However, from business and organizational point of view, its a 'RED' project with high cost overrun.

How team A and B can be justified with good rating? Any thoughts on this?
Sort By:
avatar
Samuel Vaddi Avon, In, United States
I think this is exactly why we try to setup the rating criteria ahead of time and ensure understanding and fairness. We should identify and recognize which criteria are in someone's own control vs. which are outside of their control.

Perhaps you can come up with 2 sets of criteria (in scope of control - 1,2,3 and outside scope of control - 1,2,3) and rate each team on both sets of criteria
avatar
Srikantha R Manager Agile Program Management| Publicis Sapient Bangalore, Karnataka, India
Thanks Samuel, for suggestion. Unfortunately we set ratings common across all projects and it will not differ for each project and team. (Like Schedule, quality, budget etc).

Team A which is delivered on time within schedule and budget was responsible for backed development activities and team B which failed to deliver onetime was responsible for front end development activities.

Any other different thoughts from anybody on this?

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Familiarity breeds contempt -- and children."

- Mark Twain

ADVERTISEMENT

Sponsors