Agile Change Quotes & Sayings

USE EMOTIONS AS INFORMATION. Horses use emotion as information to engage surprisingly agile responses to environmental stimuli and relationship challenges:

(a) Feel the emotion in its purest form
(b) Get the message behind the emotion
(c) Change something in response to the message
(d) Go back to grazing. In other words, let the emotion go, and either get back on task or relax, so you can enjoy life fully. Horses don't hang on to the story, endlessly ruminating over the details of uncomfortable situations

-- from an October 30, 2013 article on the Intelligent Optimist magazine — Linda Kohanov

Agile processes guarantee change and your ability to make these changes depends on your application's design. — Sandi Metz

If your goal is to deliver a product that meets a known and unchanging specification, then try a repeatable process. However, if your goal is to deliver a valuable product to a customer within some targeted boundaries, when change and deadlines are significant factors, then reliable Agile processes work better. — Jim Highsmith

Change is not for its own sake, it's the means to the end, not the end. — Pearl Zhu

DevOps and its resulting technical, architectural, and cultural practices represent a convergence of many philosophical and management movements (including): Lean, Theory of Constraints, Toyota production system, resilience engineering, learning organizations, safety culture, Human factors, high-trust management cultures, servant leadership, organizational change management, and Agile methods. — Gene Kim

Creating change-agile businesses will eliminate the need for what we today call change management. — Paul Gibbons

I've always been a decent runner so I've never been massively unfit, but for this I've got stronger. I've got rid of a bit of podge and I'm just a bit leaner, which means that I'm just quicker at moving, I'm more agile and I recover much better as well. At the moment I feel ultra-fit and it's been an amazing change. — Greg James

People talk about the businesses of the future needing to be more agile and more responsive if they are to be successful. But this requires a deep change in the way organisations work. — Andrew Curry

I take a lean-startup approach: creating agile, interdisciplinary teams that get the minimum viable product to market as soon as possible. It's my job to be entrepreneur-in-residence, an internal change agent. — Todd Park

First, how could I protect my team from the incessant demands of the business and achieve what the Agile community now refers to as a "sustainable pace"? And second, how could I successfully scale adoption of an Agile approach across an enterprise and overcome the inevitable resistance to change? — David J. Anderson

Agile Manifesto." It declared the following values: people over processes; products that actually work over documenting what that product is supposed to do; collaborating with customers over negotiating with them; and responding to change over following a plan. Scrum is the framework I built to put those values into practice. There is no methodology. — Jeff Sutherland

Creating change requires innovation: developing new products, creating new sales channels, reducing product development time, customizing products for increasingly smaller market segments. In addition, your company must be able to respond quickly to both anticipated and unanticipated changes created by your competitors and customers. — Jim Highsmith

Agile processes harness change for the customer's competitive advantage. — Adam Vardy

Agility is the ability to adapt and respond to change ... agile organizations view change as an opportunity, not a threat. — Jim Highsmith

Worse yet is the rejection of upfront requirements. The basic observation is correct: requirements will change, and are hard anyway to capture at the beginning. In no way, however, does it imply the dramatic conclusion that upfront requirements are useless! What it does imply is that requirements should be subject to change, like all other artifacts on the software process.

[...]

The agile advice here is irresponsible and serious software projects should ignore it.The sound practice is to start collecting requirements at the beginning, produce a provisional version prior to engaging in design, and treat the requirements as a living product that undergoes constant adaptation throughout the project. — Bertrand Meyer