Peer Review in the PMO
I am a big fan of peer reviews. Whether it’s related to project management or not, I really feel that the peer review process can deliver a lot of significant benefits to a piece of work. On the one hand it acts as a significant motivator to the person doing the work--the knowledge that a colleague is going to be reviewing the work that you do is a great inspiration to do a good job. On the other hand, a review by a colleague can be seen as less threatening than a review by a manager or other senior resource.
However, when I talk to people who have experience of peer reviews in project management environments, I often hear horror stories of how things have gone badly: PMs have felt threatened, discussions have gotten defensive, comments have been taken (or delivered) personally, etc. So how do you implement peer review successfully with a PMO?
Understanding the basics
It’s human nature to be defensive when our work is questioned--it’s seen as a personal attack and a suggestion that we aren’t capable of doing our jobs properly. As project managers, we are in positions of responsibility and authority--we need to be seen as leaders of our teams, and if people question our work then that can undermine our ability to successfully lead our teams and deliver the project.
If a peer review process is going to be successful, it needs to recognize
Please log in or sign up below to read the rest of the article.
"Nothing so needs reforming as other people's habits." - Mark Twain |