“I’ve spoken of the shining city all my political life, … in my mind it was a tall, proud city built on rocks stronger than oceans, wind-swept, God-blessed, and teeming with people of all kinds living in harmony and peace; a city with free ports that hummed with commerce and creativity. And if there had to be city walls, the walls had doors and the doors were open to anyone
I’ve long worried about “ Best Practices ”. Sure I usually play along at the time but lurking in the back of my mind, waiting for a suitable opportunity are two questions:Who decided this was best practice?Who says this practice can’t be bettered?I was once told by someone from the oil industry that it was common for contracts to specify “best practice” should be used. But seldom
Last time I set out some of the things a Product Owner should be doing – or at least considering doing. Even a quick look at that list will tell you the Product Owner is going to be a busy person.So in this post I’d like to suggest some thinigs Product Owners should NOT be doing.Product Owners Cutting code should NOT be cutting code Having a former coder
If you hadn’t noticed I’m building a blog mini-series on the Product Owner role. Its a role I’ve long felt didn’t get the attention it should have. Frankly, in a Scrum setting, I think the Scrum Master gets too much attention and the Product Owner not enough.One aspect in particular of the Product Owner role really annoys me: they have so much work to do.
In the official guides all Product Owners are equal. One size fits all.In the world I live in some Product Owners are more equal than others and one size does not fit all.The key variable here is the amount of Authority a Product Owner has. In my last post I said that Authority is one of the four things every product owner needs – the others being legitimacy, skills
To be an effective Product Owner – and that includes product managers and business analysts who are nominating work for teams to do – you need at least four things. You may well need more than these four but these are common across all teams and domains.1. Skills and experienceThere is more to being a Product Owner than simply writing user stories and prioritising a backlog. Yes, you need to know
Last week I was in Holland helping a client with their agile adoption and digital transformation. When the subject of teams came up I started talking about Minimally Viable Teams. Yesterday I found myself writing an e-mail to the client expanding on the idea. And it seemed to me that the e-mail – or an edited version – was worth sharing here…The idea of an Minimally Viable Team (MVT) is based