Every PM has a lot to tell you about different fuck-ups on his projects. But why we share our fails so rarely? Of course, it is difficult to tell others about your failures, so we prefer to tell only funny stories or “one of my friends…”. We with my colleagues suggested to create the list of most common problems on our projects. I can’t hope it contains some new and fresh ideas but al least it should persuade you that you are not lonely in this world of failures.
I have heard from a lot of PMs that it is hard to involve the team into retrospective process. Team members are usually enthusiastic about discussing complaints, what the idiot is the customer (yes, I know that you don’t have that in your team, as all of you respect your customer, you have a great atmosphere in the team. But I do have these problems in my teams). When I try to ask the developers some more constructive questions – I get something like “Everything was ok” from the developer. How to get more?
Sometimes I am standing in front of the team, which is comfortably sitting in the chairs and looking at me, with their faces showing “Hm..one more meeting…what does that PM need? We didn’t have this crap with the previous PM!”. And I am thinking how to awake them, make the part of the process, share their thoughts (you’ll be surprised, how many great thoughts can developers come up with).