Sunday, January 31, 2021

The need for speed in agile

Fast feedback, valuing speed of delivery and rapid iteration seems to be the norm today in agile. Is speed over-emphasized in agile?

With complex systems, changing the pace of feedback can cause resonance, that can bring serious disturbance to an otherwise stable system. A faster pace can also drive teams to burn out. Requiring stakeholders to make up their mind and provide feedback at speed about for example a feature implemented in the last sprint may not get the team those well thought out comments that will improve on the final outcome. Forming a well thought out comment require time. Communicating the thought clearly takes time. Considering diverse views take time.

According to modern theory, those that can go trough a OODA loop (OODA comes from Observe, Orient, Decide, Act) most rapidly, will obtain advantage over those progressing slower. In areal combat this is likely to hold true, but in a collaborative environment this mind set seems foreign.

Obtaining reliable high quality feedback is crucial in agile development, but does the need for feedback to be "rapid" actually cause problems?

In my view the need for speed should be carefully considered and not just taken as the absolute undisputed truth.