The Latest

As more and more people move towards adoption of agile practices, they are looking for guidance and advice on how to adopt Agile successfully. In this article the author presents a way to share knowledge that is more specific than full methodologies and processes, more general than war stories, and will help new agile adopters get beyond "It Depends!"

For agile adoption to continue, we need to address development issues that large organizations deal with, including large-scale development projects, geographically distributed development, and compliance. Let's take a look at what promising work is happening in each of these areas.

Miska Hiltunen takes a look at his own Tick-the-Code Inspection, Mihaly Csikszentmihalyi's study of happiness, and how you can cultivate quality through practical methods of empowering your software engineers to improve their own work.

What you don't know can hurt you, and what you do know can too. Lee Copeland takes a look at how the results of a 1949 Harvard experiment with playing cards should influence the way you evaluate your previous experience when building software

The value the U.S. Marine Corps places on teamwork can improve your software development team as well. Former USMC member Sean Buck shares how correctly applying Marine Corps principles will lead the way toward better, more effective test teams.

The requirements process is not a linear one. In this article, Michael Bolton helps you get in the game by showing how the elements of the requirements process–reference, inference, and conference–interact and influence each other.

Spending a little more time in design can help minimize the complexity of debugging and maximize the likelihood that the elements of a project will come together in the end. Payson Hall uses a parable and a program fragment to show how small changes to the problem can simplify the solution.