Are You Used to Delivering Daily and Responding to Change?

“Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.” — Agile Manifesto

Are you used to delivering working software on a daily basis and changing the software in response to emerging requirements?

That’s a pretty good question, and timeless, too.

I remember several years ago, when a vendor asked me that, and I remember laughing and thinking, “yeah, that’s what we try to show other people how to do.”

What was great though, was the vendor followed up with a short-list of precise questions:

What is your current software development process?
Key milestones?
Release frequency?
Daily practices?
Build frequency?
Approach for getting / learning requirements?
Approach for dealing with changing / emerging requirements?
Approach for creating testable software? (e.g. you change the software for requirement X, how quickly can you make and verify the change)

That’s actually a really good set of questions both to quickly get a handle on your software development process and to test how “agile” you really are.

It also reveals your culture and how responsive to change and feedback you really are.

What is Agile?
10 Ways to Make Agile Design More Effective
40 Hour Work Week
Don’t Let the Big Get in the Way of the Small
Don’t Push Agile, Pull It
How To Drive Digital Transformation the Agile Way
Kanban for High-Performance Teams
How Agile and Lean Help Business
How Agile Skills Improve Job Security
How To Drive Platform Adoption and Customer Success