Quotes About Agile

To do Agile right, you had to work in pairs, write tests first, refactor, and commit to simple designs. You had to work in short cycles, producing executable output in each. You had to communicate with business on a regular and continuous basis.

Implementation Patterns.

We in this industry sorely need to increase our professionalism. We fail too often. We ship too much crap. We accept too many defects. We make terrible trade-offs. Too often, we behave like unruly teenagers with a new credit card. Martin, Robert C.. Clean Agile (Robert C. Martin Series) . Pearson Education. Kindle Edition.

Agile is a process wherein a project is subdivided into iterations. The output of each iteration is measured and used to continuously evaluate the schedule. Features are implemented in the order of business value so that the most valuable things are implemented first. Quality is kept as high as possible. The schedule is primarily managed by manipulating scope.

You should be able to run all the unit tests with just one command.

The most efficient and effective way to review code is to collaborate in writing it.

QA and Acceptance Tests If QA has not already begun to write the automated acceptance tests, they should start as soon as the IPM ends. The tests for stories that are scheduled for early completion should be done early. We don't want completed stories waiting for acceptance tests to be written.

The reality is that a good project manager understands that these four attributes have coefficients. 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.

Classes and modules that are grouped together into a component should be releasable together. The fact that they share the same version number and the same release tracking, and are included under the same release documentation, should make sense both to the author and to the users.

THE STABLE DEPENDENCIES PRINCIPLE Depend in the direction of stability.

We develop features before infrastructure and frequently show those features to stakeholders.

Some folks think that Agile is about going fast. It's not. It's never been about going fast. Agile is about knowing, as early as possible, just how screwed we are.

if you want to get rich more quickly, you need to use more up-to-date, more hip, faster words of business and investing.

when agile projects fail, it's often because of cultural and philosophical differences between waterfall and agile methodologies.

VersionOne is a company that builds agile software tools, and also contributes to the agile community in many other ways.

Dave West of Forrester Research came up with a term for this: "Water-Scrum-Fall."6) In other words, they've become the most efficient waterfall team that they can be.

With a tracer bullet approach, you can implement very small bits of functionality very quickly, and get immediate feedback on how well your team communicates and delivers.

We believe that the major benefits of testing happen when you think about and write the tests, not when you run them.

Obviously, I'm coordinated and whatnot.

I pride myself on being limber.

Neat and deft and dexterous were adjectives that had never applied.

You've probably never heard anyone talk about sales agility before. Sales training programs don't even mention the word. But every top seller I know is an agile learner who knows what it takes to dive into a new situation and figure it out quickly.

agile development reflects a product lifecycle approach (continuous delivery of value), rather than a project approach (begin-end). While an individual release of a product can be managed as a project, an agile approach views a release as a single stage in a product's ongoing evolution.

In an agile project the team takes care of the tasks and the project leader takes care of the team.