Skip to main content

Five Also Rans - Product Development Risks That Can Kill Your Project!

“These are the only ones
of which the news has come to Harvard.
There may be many others
but they haven’t been discovered.”
 – Tom Lehrer, The Elements
While collecting feedback and materials for Ten Contracts, I received plenty of additional thoughts on what could go wrong. Top of the list were:
  • Too Many Cooks Risk: Are other vendors providing part of the solution? Are they working on
    an agile or a classical basis? Do you need to collaborate effectively across more than one company border? Who is empowered to address systematic impediments to success? Who gets to make decisions?
  • Worthless Feature Risk: All features contribute to the cost of the product, and some features contribute to the value of the product. The goal is to identify and eliminate worthless features before wasting money on their development.
  • Client Attrition Risk: Will the client discontinue the relationship if the deliverable does not deliver business value?
  • Fake Scrum Risk: as Scrum been imposed on the team? It is surprisingly difficult to tell a team to self-organize. Forcing agility on a team that doesn’t want to do it can cause many issues that are bad for morale, results, and performance. 
  • Phantom Resources Risk: Are people really working on the project? Or have they moved/been pulled off to work on something else? Applies to remote Product Owners as much as to Remote Development Teams.
  • Murphy’s Law: Whatever can happen will happen.  
Issues almost by definition crop up. This list will no doubt continue to grow. How can you handle risks?

What to do if the risks actually happen?

Creating a product is a challenging endeavor. Things can go wrong. The client wants something different than you thought. The stakeholders change their minds. Therefore, dealing with risk is a normal activity in any project.



You handle risks in Scrum by limiting your commitment to a particular course of action to a relatively short period of time. During the sprint, you are committed. At the end of the sprint, you can change direction if necessary.

Each Sprint the Whole Team collaborates to identify the best step forward given the situation at hand.
Every Sprint, the Product Owner – who is financially responsible for the success of the project – can reflect on the current situation to re-prioritize features, request a release or even cancel development.

If the Product Owner is constrained by contract to keep developing toward the original goal, regardless of what is learned along the way, money could be wasted, or the time could be better invested doing something else. Fixed scope projects are usually not in the client’s interest and they are not agile.

If you want to get the whole list right away, you can get my book "Ten Agile Contracts: Getting beyond fixed-price, fixed-scope." Or can click through the articles one by one.... Let's start get started in the top 10 with Number 10 (and my personal favorite): Bullshit Risk!


Comments

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…