InfoQ Homepage Agile Techniques Content on InfoQ

Articles

RSS Feed

Newer Older

TDD with Selenium and Castle

Dan Bunea shows developers how TDD can be applied in .NET using Selenium RC and Castle. Test first principals provide architects a way to quickly jump into active development early in the application development lifecycle. The benefits of TDD are a drastic reduction in defects as well as increased flexibility in the code base since the application evolves quickly through an iterative process.

Dan Bunea
on Feb 20, 2007
Interview: Using Agile for SOA

Recently, Digital Focus documented their experience using Agile to tackle SOA for Federal Home Loan Banks. The incremental approach included adopting an SOA platform that could grow as the SOA application portfolio grew, and getting frequent feedback from customers and developers. InfoQ interviewed both the client and the author of the experience report on the project, and business-IT alignment.

Deborah Hartmann Preuss
on Dec 04, 2006
Adopting Agile Development Practices: Using Patterns to Share our Experiences

Agile adoption often proves challenging. Participants at a recent OpenSpace event focused on the dynamics of adoption rather than the structure that results from adoption. The resulting patterns are part of an effort to compile Agile adoption patterns answering: "What specific practices should I adopt?", "How can I adopt incrementally?" and "Where can I expect pitfalls?"

Amr Elssamadisy
on Nov 06, 2006
Book Excerpt: Agile Software Development, 2nd ed.

In this updated classic on Agile software development, Alistair Cockburn adds reflections from five more years of practice and research. InfoQ brings you Chapter 1, in which he compares software development with another team-cooperative game - rock climbing - and two common comparison partners, engineering and model building, in order to explore alternate ways of thinking about the work we do.

Alistair Cockburn
on Oct 30, 2006
Book Excerpt: Agile Retrospectives: Making Good Teams Great

Project retrospectives help teams examine what went right and what went wrong on a project. Traditionally held at the end of a project, they're actually too late to help - no wonder we call them "post-mortems". Agile teams need retrospectives that are iterative and incremental, to find problems and design solutions to help teams improve early on, when improvement yields the most benefit.

Esther Derby Diana Larsen
on Aug 21, 2006
Using Logging Seams for Legacy Code Unit Testing

Using logging seams you can easily create unobtrusive unit tests around legacy classes, without needing to edit class logic as well as avoiding behavior changes.

Ian Roughley
on Aug 01, 2006
Agile: The SOA Hangover Cure

Author Carl Ververs who is an expert on SOA Integration and Distributed Systems writes about the application of "Agile" development philosophies that ensures that organizations can overcome architectural paralysis and get moving on those important SOA projects, while at the same time ensuring that the architecture is sufficiently flexible and adaptable for future growth.

Carl Ververs
on Jul 31, 2006
Book Excerpt: Practices of an Agile Developer

This book collects the personal habits, ideas, and approaches of successful agile software developers and presents them in a series of short, easy-to-digest tips. Practical and focused, it offers proven and effective agile practices to make the reader a better developer. InfoQ.com brings you an excerpt, "Chapter 7: Agile Debugging," as a free pdf download.

Andy Hunt Venkat Subramaniam
on Jul 24, 2006
Book Review: Agile Java Development with Spring, Hibernate and Eclipse.

Anil Hemrajani relates Agile practices to Java and several open source toolsets (Spring, Hibernate, Eclipse) designed to make Java development simpler. It's a high level overview of some free technologies used in web app development. Matt Morton liked this book, recommending it to technical managers and intermediate developers in small Java web development shops.

Matt Morton
on Jun 28, 2006
Dealing with Legacy Code

Here's a three-pronged attack to use on the legacy code that everyone eventually inherits: Build, Automate, Test. Use this BAT to create a safety net to ensure your code continues to work the way you want it to. Richardson shows how this helps quickly identify and eliminate unintended side effects. See how your day-to-day work compares, and see if you need to approach your work differently.

Jared Richardson
on Jun 12, 2006