In this episode, we continue a walk through the twelve principles of the Agile Manifesto. The second principle focuses on change and how it can be a competitive advantage. Changing requirements can be a headache and cause slippage. However, adapting to them can be a game-changer.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
I want to start the discussion about changing requirements with a call-back to our first principle. Our primary focus is on satisfying the customer. Therefore changing requirements signal a change in what is needed to satisfy them. We may find these alterations frustrating and might even experience over-runs based on them. Nevertheless, we must adapt if satisfaction is our priority.
The Competitive AdvantageThe idea of an agile approach being an advantage applies to far beyond software development. Agile athletes can dodge blows in boxing or tackles in football. Likewise, they can perform gymnastic feats and score goals. Similarly, agile organizations can adapt to the market quickly. Therefore, you often hear about nimble start-ups that "pivot" and grab a market lead. When agility is so valuable in most environments, it only makes sense for us to give that to our customers. We adapt to changing requirements to help them be successful. That goes a long way in providing satisfaction.
Even Late In DevelopmentI almost chuckle at this line. Do any of us run into changing requirements in the first half of a project? Yes, sometimes we do. However, it seems like late in development is the prime spot for these alterations to occur. Maybe they are just more noticeable. They are more costly. Just as bugs are more expensive to fix, the later they are found, requirements are harder to adapt to later in the process. This timing is a challenge that provides an opportunity to make a significant impact on satisfaction. Embrace these obstacles and satisfy your customers.
