Quotes About Agile

She's capable of anything, and she's as deft as a bear's tongue.

Prejudice is a shape shifter. It's very agile in taking forms that seem acceptable on the surface.

agile teams need short backlogs of small items, a number of which are quite well-articulated and socialized, but only just prior to the iteration boundary in which they will be implemented.

agile is the most disciplined and quality-driven set of development practices the industry has invented to date.

Build what you need as you need it, aggressively refactoring as you go along; don't spend a lot of time planning for grandiose, unknown future scenarios. Good software can evolve into what it will ultimately become.

The way you approach a big software cake is to break it down into lots of little cupcakes.

Slice out a release strategy. Remember: there's always too much to build.

Stories are the building blocks of communication between developers and those who use their work. Story maps organize and structure these building blocks, and thus enhance this communication process — which is the most critical part of software development itself.

There is nothing to winning, really. That is, if you happen to be blessed with a keen eye, an agile mind, and no scruples whatsoever.

I'm a very coordinated individual.

I'm athletic but in a dancer way.

I was always a mean and lean athlete - not tall - not large.

Prediction and being "right" will be less important than reacting quickly and taking corrective action.

want them to be as alert as a mouse at a cat show.

He hits from both sides of the plate. He's amphibious.

Oh, how I wish I had already regenerated to become the tall one with the dicky bow, thought the Doctor, who occasionally had visions of his future selves. He is always so fit and agile. I suppose all that incessant running down corridors that he does . . . will do . . . may do, in one of my possible futures . . . is good for something.

Imagine if Wells Fargo had adopted an agile approach to strategy: the company's top management would then have taken repeated instances of missed targets or false accounts as useful data to help it assess the efficacy of the original cross-selling strategy. This learning would then have triggered much-needed strategic adaptation.

Launch your product or service before you have funding. See how people respond to it before you have a PowerPoint and business plan - have something people can use, and go from there.

But I can write my tests later", you say. No, you can't. Not really. Oh, you can write some tests later. You can even approach high coverage later if you are careful to measure it. But the tests you write after the fact are defense. Tests you write first are offense. After-the-fact tests are written by someone who is already vested in the code and already knows how the problem was solved. There's just no way those tests can be anywhere near as incisive as tests written first.

First Law You may not write production code until you have written a failing unit test. Second Law You may not write more of a unit test than is sufficient to fail, and not compiling is failing. Third Law You may not write more production code than is sufficient to pass the currently failing test.

No matter how elegant it is, no matter how readable and accessible, if it hath not tests, it be unclean. Dave

A good manager drives a project to be good enough, fast enough, cheap enough, and done as much as necessary. A good manager manages the coefficients on these attributes rather than demanding that all those coefficients are 100%. It is this kind of management that Agile strives to enable.

If you let the tests rot, then your code will rot too. Keep your tests clean.

But if you want to understand what Agile is really all about, there is no better way than to study XP. XP is the prototype, and the best representative, of the essential core of Agile.