BROADCASTS.com

b'

Description:

This week, Dan Neumann shares the most downloaded episode from the Agile Coaches\\u2019 Corner podcast called What is Agile? where Sam Falco and Dan unpack the true meaning of Agile. You can\\u2019t miss it!

\\xa0

Key Takeaways:

• Why was it necessary for the Agile Manifesto to be declared? What is the history behind it?

• It was created in reaction to what was happening in the software industry in 2001 (predominantly waterfall and other predictive methods with lousy track records for delivering on time).

• In response to \\u201cscope creep\\u201d (AKA changes or uncontrolled growth in a project\\u2019s scope at any point after a project begins).

• Because it is tough to predict what you need to do when you\\u2019re trying to solve a new problem every time.

• Out of necessity (as any work that requires creativity and a high degree of uncertainty about the outcome you\\u2019re trying to achieve [such as software development] is difficult without a set of principles and values).

• Because every problem is unique with software development.

• In the Harvard Business Review in 1986, an article was published titled \\u201cThe New New Development Game\\u201d that outlined the need for a new way of working where teams could be given objectives instead of tasks, and they work together as a unit to accomplish their work.

• The \\u201crelay race\\u201d method was clearly not working, and agility offered a better model, better compared to playing rugby.

• \\u201cAgile wasn\\u2019t: \\u2018Let\\u2019s get together and think about a new way of doing things.\\u2019 It was: \\u2026 \\u2018Hey, we\\u2019re doing some things. It seems to be getting better results than the industry as a whole. What are we doing that\\u2019s common across the different methods?\\u2019\\u201d \\u2014 Dan Neumann

• What is the Agile Manifesto?

• Those that came up with the Agile Manifesto didn\\u2019t put it together to justify their existence; they put it together because they recognized the success they were having through its methodology and wanted to figure out the commonalities.

• It\\u2019s the thing we point to when someone says, \\u201cWhat is agile?\\u201d

• If you ask if something is Agile, you can reference the manifesto\\u2019s values and principles.

• What is Agile?

• It\\u2019s creating a competitive advantage and being the disruptive force.

• Delivering working software as your primary measure of success.

• A collection of values and principles as laid out in the Agile Manifesto.

• It is the ability to respond to change and demand deliberately, not just react.

• Controlling risk:

• Building stuff that people actually want and will use.

• Solve the problem that the customer has called for and not gold-plating everything.

• Agile practices are simply that; practices \\u2014 they\\u2019re good in some circumstances and not good in others.

• Are you changing just to change or are you harnessing change for competitive advantage? Is change happening to you or are you creating the change?

• Change is not just about keeping up with your competition but making your competition keep up with you.

\\xa0

Mentioned in this Episode:

Extreme Ownership: How U.S. Navy SEALs Lead and Win, by Jocko Willink

\\xa0

The New New Product Development Game, by Hirotaka Takeuchi and Ikujiro Nonaka | Harvard Business Review (January 1986)

\\xa0

Agile Software Development Ecosystems: Problems, Practices, and Principles, by James A. Highsmith

\\xa0

The Surprising Power of Liberating Structures: Simple Rules to Unleash A Culture of Innovation, by Henri Lipmanowicz and Keith McCandless

\\xa0

LiberatingStructures.com

\\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

\\xa0