Quotes & Sayings About Agile Development

There is romance, the genuine glinting stuff, in typewriters, and not merely in their development from clumsy giants into agile dwarfs, but in the history of their manufacture, which is filled with raids, battles, lonely pioneers, great gambles, hope, fear, despair, triumph. If some of our novels could be written by the typewriters instead of on them, how much better they would be. — J.B. Priestley

Agile Project Management -like its lean development counterparts- streamlines the development process, concentrating on value-adding activities and eliminating overhead and compliance activities. — Jim Highsmith

Countering the juggernaut of formalism is a minority worldview of equal historical standing, even though it does not share equal awareness or popularity. Variously known as hermeneutics, constructivism, interpretationalism, and most recently postmodernism, this tradition has consistently challenged almost everything advanced by the formalists. Iterative development practices, including XP, and object thinking are consistent with the hermeneutic worldview. Unfortunately, most object, XP, and agile practitioners are unaware of this tradition and its potential for providing philosophical support and justification for their approach to software development. — David West

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

The more detailed we made our plans, the longer our cycle times became — Donald G. Reinertsen

The essence of Agile movement, whether in new product development, new service offerings, software applications, or project management, rests on two foundational goals: delivering valuable products to customers and creating working environments in which people look forward to coming to work each day. — Jim Highsmith

The Scrum idea of a separated Scrum Master is good for Scrum, but not appropriate for most projects. Good development requires not just talkers but doers. — Bertrand Meyer

To focus on the visible at the expense of the essential is irresponsible. — Bertrand Meyer

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

Half, Not Half-Assed — 37 Signals

As an Agile software development team, we'd been following the hallowed eXtreme Programming tenets, including YAGNI. That is, You Aren't Gonna Need It: a caution to not write unnecessary code - — Anonymous

There's no way to force someone to be energized. However, you can remove roadblocks. — James Shore

following one process and the development team with different process philosophies, terms and metrics. In Waterfall, once a "plan" is baked and approved, there is an expectation that the plan will be followed and delivered upon, even if the development team is using Agile to execute. Now I'm going to say it, "But that's not truly Agile," since Agile requires the plan to be flexible and consistently reprioritized and revised. We see this approach so often that we've heard many describe it as, "WaterScrumFall. " It's really business as usual — Anonymous

when organizations adopt Agile practices, it is imperative that team leaders and development managers learn a better approach to leading and managing their teams. — Jurgen Appelo

Management Challenges to Implementing Agile Processes in Traditional Development Organizations, — Barry Boehm

Agile methods don't attempt to describe everything that any development effort might need in thousands of pages of documentation. Instead they describe a minimal set of activities that are needed to create swarm intelligence. — Jim Highsmith

Most literature on the subject of agile methodology... is written from the viewpoint of software developers and programmers, and tends to place its main emphasis on programming techniques and agile project management - testing is usually only mentioned in the guise of unit testing and its associated tools. ...However, unit tests alone are not sufficient and broader-based testing is critical to the success of agile development processes. — Tilo Linz