the blog for developers

Black Swans make managing development risks impossible

As a project manager I’ve been doing risk managment in software projects for years and as an event manager in private too. And I’ve been to several workshops about project and risk management. It basically boils down to rating the impact and the probability of risks and then plan actions to prevent, solve or mitigate them. The simpliest form is to rate the probability A,B and C (high to low) and the impact A,B and C (high to low) and rank the risks depending on impact and probability (A,A first and so on). After reading about black swans which are very high impact with very low probabilities risks I no longer think you can manage risks. Just be aware of and live with them. Like a stock market crash or the crumbiling of the Berlin wall. Could you manage those? In the framework from above they would rate as AAA/ E or above risks. What do they look like in software development? Your team decides to found a startup, your client goes bankrupt, two developers in your team quiet, the feds raid your company, you client gets a new CEO which reprioritizes projects and so on. Can you manage those risks? Some think they can.

Whenever I’ve asked in workshops or in talks with peers what to do about AAA impact risks people said well, we don’t manage them, they are too unlikely. And I might add, you can’t do anything about them as a project manager. Most of them are out of your sphere of influence. Can you hire people on standby? Can you protect your client from bankrupcy ? Can you influence job decisions at your client? Can you influence the Feds? What do project managers instead? They rate minor impact risks like not delivered hardware (which can easily solved by ordering last minute from Dell) or wrong requirements to the top (A) and “manage” them. But real risks are ignored. With some time people grow blind spots for real risks, happily manage small impact risks and feel save. Untill your team outsources itself or your client goes bankrupt.

Thanks for listening.

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

About the author: Stephan Schmidt has more than 15 years of internet technology experience and 10 years experience in agile. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own.
Leave a reply.

Leave a Reply

What people wrote somewhere else:

Additional comments powered by BackType

Guide to CodeMonkeyism

Over the last 4 years I wrote many articles on this blog. To make it easier for you to find the relevant ones, I've organized them into topics.

Top 10

6 reasons why my VC funded startup did fail

Go Ahead: Next Generation Java Programming Style

Java Interview questions: Write a String Reverser

The dark side of NoSQL

7 Bad Signs not to Work for a Software Company or Startup

Is Java dead?

Scala vs. Clojure

Never, never, never use String in Java

No future for functional programming in 2008 – Scala, F# and Nu

Clojure vs Scala, Part 2

Java Developer

Is Java Dead?

Go Ahead: Next Generation Java Programming Style

Be careful with magical code

All variables in Java must be final

Never, never, never use String in Java

Bending Java: More readable code with methods that do nothing?

NoSQL Guy

NoSQL: The Dawn of Polyglot Persistence

The dark side of NoSQL

Essential storage tradeoff: Simple Reads vs. Simple Writes

Sharding destroys the goals of your relational database

The unholy legacy of databases

Startup/CTO

Development Dream Teams

6 reasons why my VC funded startup did fail

American vs. European style of Software Development

12 Things to Reduce Your Lead Time and Time to Market

The high cost of overhead when working in parallel

Essential storage tradeoff: Simple Reads vs. Simple Writes

Job Seeker

Another Good (Java) Interview Question

7 Bad Signs not to Work for a Software Company or Startup

Java Interview questions: Write a String Reverser (and use Recursion!)

Java Interview questions: Multiple Inheritance

As a Manager: What I value in developers

Top 10 Tips (+1) to Get a Pay Raise

Agilist

What Developers Need to Know About Agile

5 Practices Better to Change in Your Scrum Implementation

Scrum is not about engineering practices

ScrumMaster and ZenMaster: The joke of certification

What is Trans-Scrum?