Five stories, mostly based on real life, that might help you see how Agile can become mechanical and what you should do about this.

This article presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.

This article is about applying Agile methods in an environ-ment that may be more familiar with high ceremony project manage-ment methods – methods that might be considered heavy weight in terms of today’s agile vocabulary.

There are a number of methodologies and approaches to agile development. For the sake of this article, the discussion will center on how to handle defect management within the context of a software project that uses an Agile methodology.

This overview helps project management and teams in selecting the best iterative method(s) for their projects, based on the major risks they want to tackle. The overview highlights the focus of the different methods, ie. which risks are mainly addressed. This is not a detailed course on all the methods, but references to literature are provided.

This paper discuss experiences and lessons learned in doing offshore agile development.

In Agile projects, it's a common practice to visualize and share project status in “big visible charts” on a wall of the project room. Lean systems also use such devices. "Kanban," in Japanese means, loosely translated, 'card or sign'. In a Lean production system, Kanban is a method which uses standard units or lot sizes with a single card attached to each. A new card is "pulled" into the system only when the work represented by an "in progress" card is completed. In this paper, I explore visualization methods found widely in agile projects these days, and then propose using Kanban Boards to organize three viewpoints (Time, Task, and Team) so that the whole team understands the current status of the project and can work in an autonomous, motivated and collaborative manner. Finally, I introduce a software tool “TRICHORD” that implements Kanban Boards to realize project visualization from the three viewpoints.

The basics of installing and configuring the Hudson continuous integration engine to continuously build and test Oracle Application Development Framework applications

This article proposes a set of techniques and practices to leverage the agile approach to software architecture—increasing overall quality, streamlining development practices, and providing business value as a constant flow. The article describes issues that are related to component API design and behavior-driven design, continuous measurement of complexity, automated quality-attribute evaluation, and design rationale recording.

It's now well understood that multi-tasking on a personal level is bad and slows down the rate at which we work. Roger Brown demonstrates the same problems plague teams.