The Latest

An otherwise good project management book provokes Payson with definition of “success” that rubs him the wrong way. In this article, he presents his case.

Many people realize that the technical debt spiral is a perverse incentive—it ends up rewarding behaviors we don't want and causing long-term pain. In this article, Matt Heusser moves beyond cliché to talk about how tech debt happens and what we can do about it.

George and Bob Payne discuss one of the most beneficial and underutilized agile technique, test-driven development. The data is in, and you need to be doing this if you want to call yourself an agile engineer.

Whether you’re concerned about your day-to-day work or the long-term goals you’ve set, a good attitude can make all the difference. In this article, Laura Brandenburg expands on some tips gathered from Jeffrey Gitomer’s Little Gold Book of Yes! Attitude.

In  many ways, estimating project budgets or dates for agile projects turns out to be irrelevant. If you have a ranked backlog, and you finish features, you can always stop the project if you hit a particular date or cost.

Lisa Crispin writes that you need to understand the purpose of a user story or feature. Start with the "why." You can worry later about the "how." The customers get to decide on the business value to be delivered. They generally aren't qualified to dictate the technical implementation of that functionality. It's up to the technical team to decide the best way to deliver the desired feature through the software.

With all the faces it presents, surely software can be said to possess or lack beauty. But, what does it mean to have beautiful software, and how do we evaluate it? In this installment of his series on philosophy and testing, Rick Scott takes a closer look at software aesthetics.