The techniques for delivering work, regardless of function or subject matter, in an agile way.
For decades, agile teams have promoted strong Technical Agility as the keystone for “being” agile. The purpose being to increase quality & throughput and at the same time embracing uncertainty & change. Many of the agile methods developed over the last 20 years, such as Extreme Programming (XP), Behaviour Driven Development, Test-Driven Development, and DevOps, are almost entirely devoted to Technical Agility. And Technical Agility isn’t limited to just software either. Any domain of work can be technically agile - for example, we’re starting to see agility emerge in marketing and finance work with their own agile practices (e.g. Agile Marketing or Beyond Budgeting).
To be technically agile, any work practice or technique needs to be designed for ambiguity, be customer centric, seamlessly respond to change, and promote collaboration. To benefit from Technical Agility, your organisation requires the other 8 domains, but these techniques & practices are generally a good place to start.
Case Studies[edit source]
Further Reading[edit source]
Extension:DynamicPageList (DPL), version 3.1.3: Error: No results!
Books & Book Reviews[edit source]
Join the Business Agility Community[edit | edit source]
If you'd like to continue the conversation with like minded individuals around Business Agility Ways of Working, join the Business Agility slack community. Specifically the #future-of-work channel.
Library Steward[edit | edit source]
This section is currently un-stewarded. If you have a passion for this space and would like to take ownership for the guidance and insights within, please contact Evan Leybourn. The stewards of the Business Agility Library are leaders in their field and we quite literally couldn't create such amazing content without their support. These people & organisations are leaders in the community and, through their actions and insights, continue to expand the horizon of business agility for us all.