What means Agile? . . . . . dec 11 2002 — sg5.dat
Software is like an iceberg, with only about 5 percent showing up on top, and really a lot hiding down below. The figure may even be down near zero (never less than zero) for some middleware projects, where practically the whole thing is submerged and out of sight.
The preface of Agile Software Development deals with imperfect communication, and in the java study group we certainly made the most of that but for the most part we will discuss modelling, when and how, and practices to adopt and avoid. In this way we can build a catalog and vocabulary of practices, in the same manner we have examined design and refactoring patterns in code.
In addition to "what does it do" and "what does it contain", the idea of "what does it ensure" was added to the characteristics of objects to evaluate, especially in the context of the quality or qualities of objects, further in the context of enduring business themes.
The study group book is Agile Software Developmentbuy at amazon.com by Alistair Cockburn, and everyone agreed that his rendition of how an epic poem might be written if it were planned and executed and done by a large team of poets in the same way as software development is done, was by itself worth the price of the book.
In the "build a vision" department, Software for your Head was recommended.
pools=XML, Blog, Ruby
