|If your product owner behaves like this|
way they are doing it wrong: very wrong!
Every scrum master needs to be on the lookout for some anti-patterns in how product owners do their jobs. In a perfect world, the product owner and the scrum master are like siblings working toward the same goal. The reality is that mismatched business priorities and lack of cooperation by business partners can happen in any organization. So this article will help you recognize the smells which you should look out for as a scrum master. I hope a few of you will be kind enough to provide some suggestions of how to deal with these anti-patterns. Many of these examples come from Roman Pichler’s excellent book on product ownership.
The Under Powered Product Owner
We have all seen this product owner. They have the look of an abused animal. They are not empowered to say “no” and they when they say that they speak for the business you know what they are really saying is they speak for their boss who will overrule them when it is convenient. The under-powered product owner is a figurehead who is their because the scrum process says so. The people with the real say will not abdicate their authority to let this product owner do the job. The authoring of user stories consists of being called into the boss’s office to take dictation from the boss. Priorities are set by the boss and if something goes wrong it is the fault of the development team rather than the boss. Everything is a priority so nothing is a priority until something goes wrong which triggers a spasm of unsustainable development.
The Over Worked Product Owner
According to Certified Scrum Master training, each software project should have a product owner and a scrum master along with a group of developers ranging in size from five to seven people. Executives look at this as a waste of resources and often assign multiple scrum masters over many development teams and do the same with product owners. The by-product is the over worked product owner. Currently, at my firm I work with a Product owner with his work divided among four software development teams. What this does is that it forces the Product owner to only spend the minimum amount of time necessary to get stories written and to make sure that priorities are getting fit into the sprint. The stories are rewritten by the scrum master or another developer so they are clear enough to be understood by the other developers. Stand up meetings, retrospectives, and demonstrations are missed because they are not considered critical by the product owner. The only time they turn up is when something goes wrong or when upper management is paying attention. Quality suffers, and the notion of sustainable development is nothing more than a sick joke.
The Absent Product Owner
Sometimes projects are kicked off and the executives who demand the work can’t find or won’t hire a product owner. The software is still expected to get written but no one can be bothered to write the user stories. Software developers and scrum masters should just be smart enough to find out what creates user value. This creates situations where what is constructed is often not what the business wants. Fortunately, the failure process is faster so the executive can ask questions like “what is wrong with you people?” and “this is a simple business process why am I paying you so much money to screw this up?”
The Product Owner by Committee
Some projects have a great deal of visibility and multiple project teams; this creates the product owner by committee. These are individuals who are all empowered to write stories in the backlog and they are also equally empowered to set priorities. This pulls the development like taffy and forces the scrum master and the development team to juggle priorities with dexterity of chain saws. One mistake creates, the loss of a limb and the destruction of a career. In addition, the horrific aftermath generates meetings which are outside the scrum process and cut into the productivity of the team. This is why many of us in the agile community are discussing how to scale large projects because multiple development teams and product owners leads to this situation.
The Rogue Product Owner
This is a product owner who has his own personal interests in mind rather than the needs of the business when creating work for the development team. You know when you work for a rouge product owner when your boss comes to you and asks what your team is working on. This is because the team is making life easy for the product owner but new customers are not being generated because the features to attract those new customers are not prioritized as highly by the product owner. This undermines the agile process because the only value being created is for the product owner instead of the business.
So there you have it; five different anti-patterns for product owners. Be on the watch for all of them otherwise your life as a scrum master is going to become very painful.
Until next time.