The Latest

The authors explore the pros and cons of four other common styles of code reviews—over-the-shoulder, email pass-around, pair programming, and tool-assisted reviews—and see which ones is the most promising candidate for practical peer code reviews.

Some of the most powerful tools for software developers are now free--a fact which Chris McMahon believes should help bring small businesses and local developers together in the creation of custom software. Read of how he plans to accomplish this on a local level.

Test managers are in the precarious position of being responsible to both the project and the team, but the manager and team know best whether overtime will help or hinder project progress. In this installment of "Management Chronicles," a test manager keeps the concerns of her team in mind when evaluating the need for overtime.

Twenty years ago, Brian Marick defined a small startup's company process and coding standard in his position as head of quality assurance--and didn't win any popularity points. Looking back, Brian thinks that he and others in charge of process would be more successful using persuasion than using commands.

The flow of knowledge is more than mental. Better your team and improve your output through an adjustment in physical surroundings. Jean Tabaka describes the Japanese philosophy of "ba" and what it can mean to you and your development team.

Recognizing candidates who are capable of performing well on agile teams doesn't require keyword searches through a stack of resumes. It requires asking candidates questions that allow them to show you they understand the principles and can apply them in their daily work—even if their resume doesn't list particular terms. In this StickyMinds.com column, Johanna gives some excellent tips for the interviewer and the interviewee.