Here i came across a peculiar case . One of my team member defending "The assigned work is done by another employee who already left the company , now we are fixing minor bugs there ,so why should we take the ownership of that whole work / process ?" Saving Changes...
Sort By:
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Because no single person owns a work product. It ultimately is the company or organization who owns the work product and, through it authority matrix, delegates the custody of it to specific positions or roles. Saving Changes...
This is a serious issue, and is actually not good for the project. It appears that team lacks the commitment & courage to take ownership. A PM must stress on developing a culture of personal accountability, a passion for the work in team.
This is a great opportunity for the team to showcase their value to the management by demonstrating commitment required to achieve organization goals & objectives. Saving Changes...
One point to always keep in mind is that in a project code is not owned by any one person, complete solution is a team effort. Ownership comes to picture where one module / portion of solution is assigned to a resource (resource is accountable). In this case RACI matrix is very helpful to avoid any confusions. RACI helps clarify Accountability (ownership) from Responsibility. As per Service management principles many people can be responsible for a piece of solution but only one person can be accountable for the same, hence RACI in this case will be most beneficial to avoid confusion. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
If you assign she/he to the activity is nothing to discuss. I really do not understand the point. Saving Changes...
From my point of view, there are several points that you should review (with your team, PMO or by yourself)
- Property of product
- Team Building
- Roles and Responsibilities
- Procedure and correct communication about what happens if someone will leave the team (As knowledge transfer, documentation, how to split the pending tasks)
Try to analyze the comment of your team member, use it an opportunity to improve the team, your management and leadership skills or maybe your company template procedures.
