Several months ago I was leaving one of the best teams I worked with. I wanted to leave them something, that will help them coping with any issues they would have. That is when the idea of “Ideal Project Manager 1.0” came to my mind. Developers usually complain that PMs are doing nothing during the working hours, they are only telling everyone how they should work. I am close to this idea too, so I created this ultimately cost-efficient version of project manager which can 100% replace your PM. This PM works 24h/day, 7 days/week and can 100% replace the ordinary PM. Functionality includes all the good PM features – it provides you a piece of advice or direct command every time you have issue or task to solve.
So, I want to share with you this unique product, so it can help your teams too. Say hello “Project manager 1.0”!
Decided to create this post as I’ve heard this question many times during the last 3 weeks. Several people asked that during the cspo training; clients asked 2 times; my boss and my colleagues could not omit this question too(3 times in total). So I want to share some of my thoughts on this topic.
Let’s imagine a scrum team, which is working on a Product. We have a Scrum master – a nice guy – and a Product owner, who has a lot of great ideas and drives the product on. The team works hard every sprint (yes, they play tennis and drink coffee several times a day. And… oh, hell… they even read facebook and watch cat videos during the working hours. So, just an average team). And one day their stakeholder/big boss comes and asks Scrum Master, “Ok, I see the team is working. You have a scrum master, a product owner… But we have a release planned in 2 months. So, tell me, who is responsible for the delivery? Who is responsible for the release being shipped on time?”
Continue reading Ok…But who is resposible for delivery?
Once (ok, let’s be honest, not just once) I was thinking, “Why not to get rid of estimations?”. I heard a lot from the developers in our company that they hate estimating. That is usually a very painful process for a project manager, too. Not only because of the process itself, but because of what happens afterwards. If you worked on more than one project, you definitely know that the estimation your team created won’t be ok for business people. They certainly know that this feature is very easy and that story can be done in a day… Or, “My colleague – he is a developer himself – thinks this can be done in a week!”. They all need hours, exact numbers and deadlines. Team wishes not to provide that.
Continue reading It seems that I hate estimations. Really?
Once you start working with the team that is really great, you stop thinking about the things that make them great – their greatness just exists and you “feel” it. But “feel” doesn’t work for me – I really need to describe, classify, plan and predict. So, let’s try to describe the features of a great team, so it would help us breed more great teams. Have you ever been a part of great team? Or worked with one? Please share your experience.
What makes the difference:
Continue reading Great team checklist
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.
Continue reading PM rescue kit: Most common fuck-ups on your project
About two months ago I had a severe argue with one of our lead developers about ‘agile stuff’. After 15 min of listening to my enthusiastic speech his face became red and I could read “Woman, what do you know about the real life?” from it. And then he said the phrase I can’t forget: “And why do we need all of that? Why we can’t just collect our best architects and analytics and write down all requirements, describe models, create the ideal architecture, plan everything and then start development?”
Continue reading Where the miracle begins