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.
It is time for my first post to be translated 🙂
No doubt retrospectives are one of the most important meeting in the development process. But teams usually tend to ignore them. If you don’t push them they just stop doing retrospectives at all, as this activity seems “useless” to them. But when else can we get such a magical push and start changing for the better, if not during retrospective? We can continue making the same mistakes over and over again.
I really love games, that is why I am trying to use them in my work life too. When it comes to the serious questions – adopting new processed framework or show the team why it is great to work in a team – I prefer to use games too. It is fun, it is easy and very engaging. When I came across lego scrum simulation by Alexey Krivitsky, I thought – “Bingo! That is what I need.” In addition – I really wanted to buy some lego and could not find any excuse to do that…So it was my chance.
Everyone is writing unit tests, everyone cares about their tech debt, everyone performs refactoring… Sure! Enter the nearest dev team room and ask them several questions:
- Do you do TDD?
- Do you write unit tests?
- Do you perform refactoring?
And you’ll hear the same I usually do – “No”. And when you ask “Why?” the answer will be “We have no time!”.
I am a cruel PM, one of those guys who keep saying to the teams: “We have no place for that in the budget!”. But it scares even me. So, PMs, stop blaming the teams, it’s your job to protect them and forget about “We have no time!”.