Skip to main content

Scrum Masters: Are you impacted by the First Impediment?

I just had a conversation with a graduate of my last Certified Scrum Product Owner class.

  • How is it going with Scrum?
  • Well, good, I suppose.
  • That sounds a bit hesitant...
  • Well, I'm called a Product Owner, but my job description is completely different, so I can't really make things happen the way I should
It turns out that her job description was missing some key aspects of Product Ownership, like the ability to make decisions.

I suspect this issue is widespread. People say were are going to do Scrum, because it will enable us to do many wonderful things. Then they fail before they start, by not even getting the basics right. Does this sound like your organization? 

Scrum Masters, Product Owners, is this your First Impediment? Do you have the full competency that your role should have? Step one, let's make the problem visible! What are you expected to do in Scrum that you are not allowed to do in real in your company?


Comments

Andrew said…
Yes, my PdO is the one defined in the article... In fact we have Product Team (4 PdOs) and they say the have autonomy and can decide what features will be developed in the product but many times they are just receiving decisions from the managers that they cannot change, and forwarding them to the development teams... :(
Peter said…
I feel your pain.

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …