Skip to main content

Top Project Risk Number 8: Stakeholder Risk

Will the stakeholders change, or even just change their minds?

Just before my team was scheduled to release the first version of the product, the client’s pilot customer changed their digital marketing manager, who was responsible for the product. We made the release, and he was shocked: “You have created a web-based media tool but don’t support the basic tags required to track readership! How could you?!”  
What happens if new people assume the role of key stakeholders in the project? Are they aware of and bound by the decisions about purpose, priority, scope or funding level made by their predecessors?

Even without personnel changes, decisions about prioritization can change any time and have an impact on many projects.

Let's say Mary, a middleware developer, is scheduled to work on Project A until the end of the month, and then move on to project B.  What happens if Sam, a stakeholder of the middleware team, tells Mary's manager that Project C is now the top priority? “Have Mary stop working on Project A and go to work on Project C.” Or “Divide Mary's time among projects A, B, and C.” Both of these alternatives delay Projects A and B. The second alternative also slows down Project C, because Mary only has one-third of her capacity for each project, meaning the work will take her at least three times as long as planned.

Both alternatives mean that both project’s development costs will be tied up longer before generating a return. They also increase the risk of not getting any return at all. If the company never returns to finish Product A or B, those development costs will have to be written off (or seen as part of the cost of Project C).

Unfinished work is very expensive, and the return on investment is negative. Scrum protects the Scrum Team from undue interference and unfinished work.

Stakeholder risk mitigation in Scrum 

Only the Product Owner may give instructions to the Development Team, and only through the sprint planning mechanism. Once the sprint has started, no one may change the sprint goal. In exceptional cases, the Product Owner can cancel a sprint. Since this means that work might be thrown away, this option should be used sparingly. If Project C really has become the most important, the Team can pick it up in the next sprint planning.

The rest of the organization must respect the sprint contract. If powerful stakeholders can treat the Development Team as a self-service shop, borrowing people whenever needed, the team will not be able to fulfill its commitments. They will not even want to make commitments, because they don’t have control of their time. They will be doing Scrum in name only, and the benefits of Scrum will be lost.


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…

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 …

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…