Early Warning – Do you ignore risks in Scrum?

My friend and I were rushing to a dinner party. When I started my car, a red battery symbol was blinking. I ignored it and headed to the venue. After two kilometres, my car broke down while the red symbol was still blinking. It was 9 p.m. when we began our search for a repair shop. 

We accepted the help of a few people and pushed the car some distance. As we stopped at a red light, we realized that the closest available shop in the other direction, toward home. We pushed the car through a U-turn and headed back, but the shop was closed by the time we reached it. However, we were close to home and found a place to park the car. We decided to call the mechanic the next morning.

These small incidents in my personal life always help me improve my work with Agile teams. I learned the following lessons from this incident, which can definitely help me in an Agile environment:

  1. Do not ignore any warning signs or risks. Agile is all about inspecting and adapting. We run on small cycles so that we can identify the risks as early as possible. Generate a plan as soon as you have identified any risk.

    If I had taken the right action, I would have enjoyed the dinner, but there was still the risk of arriving late.

  2. Take the best possible action in accordance with the organization’s objectives. If you cannot mitigate the risk when it is identified, take the best possible action so that you are still on target with your objectives.

    It is sometimes wise to take a U-turn to come around again with full vigor. You’ll get better results.

 

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *