Scrum Team

Aim for nothing, you hit nothing

Photo by Afif Kusuma on Unsplash

I was watching the movie Shang-Chi and The Legend of The Ten Rings (Movie, 2021) | Official Trailer, Cast, Release Date | Marvel on the airplane from India to Germany and there is one scene where a lady talks to her protégé and tells her “Aim for nothing, you hit nothing”

In this case, it is about a person who floats around in life with no perceived goal. This person goes on to learn archery and save the day by slaying a dragon.

In our projects, we have Developers working on Sprints (especially Agile projects).

Have you seen Sprints with no Goals?

These Sprints lead nowhere because the Developers do not feel that they need to aim for something. By aiming for nothing they are prepared to hit nothing.

Start small and define that Sprint Goal (You can make it SMART step by step at later stages)

  • Aim for some Sprint Goals and you might reach a few the first time.
  • The second time you will notice the Sprint Goals getting measurable and SMARTer.
  • The third time you will start asking yourself how did I not do it in the first place?

Are you ready to aim for a Sprint Goal and bring the dragon to the Sprint Review party?

Agile Agile Leadership

Decision latency

Photo by Anastasia Lysiak on Unsplash

Have you ever felt Decision latency in real life or work?

I recently felt it in real life.

I had ordered a bouquet of flowers to be delivered to a friend in the hospital.

The order process was seamless and I even got a confirmation of when it will be delivered.

Order date: Saturday

Delivery date: Tuesday

I get to know from my friend that she has moved to home early on Monday.

I contact the hotline of the flower provider on Monday and ask if they can change the delivery address.


The hotline person says that it is too late and the order has been processed.

The process workflow does not allow to postpone the decision of updating delivery address for the flower delivery person on the day of delivery.

I ask the hotline person of the flower provider on Monday if they can cancel the order.


The process workflow does not allow to cancel the order one day before the execution of the order.

I put the phone down and one hour later I get an email saying that the order is being processed to the wrong address.

The customer experience is so wrong at this place. Two NOs in a telephone conversation and followed up with an email confirmation which rubs salt in the wound.

I write an email to the service email address explaining what happened with the hotline and asking for other customer friendly options.


The order has been processed and a telephone or an email will not change things.

I then receive an email to rate the service with three smileys.

Guess which smiley I chose!

In our Agile teams, what is the decision latency – 1 hour, 1 day, 1 week, 2 weeks, 1 month?

Is it small enough that we can bring value to client fast enough?

If it is not small enough, can we recognize and fix it?

Interesting article from Jeff Sutherland:

Why 47% of Agile Transformations Fail! – Scrum Inc