Managing Risk with Scrum
In my experience of doing software development for non-developers, risk is one of the most difficult things to deal with. It’s so easy and tempting for customers to think and plan in terms of the definite “I will have feature X by date Y”, that the risk of X not being available by Y gets quietly ignored. Any such failures come as a complete surprise, even when the details of feature X were not even known at the time an estimate was made.
Several development project management methodologies try to cope with this, and Scrum is probably the most well known. Here’s an InfoQ article about risk and scrum.






For years Frank Carver has been paying attention to the strange world of convergent technology. During that time he has discussed and researched broad subject areas, come to some surprising conclusions, produced and distributed digital media, scattered ideas and opinions like sparks from a firework, and above all consulted for businesses both large and small to help develop and deploy successful systems, services, and products in this highly complex arena.

