The Latest

There is definite asymmetry between building trust and destroying trust. While building trust can be complex and time-consuming, destroying trust can be done in one simple instant.

CM tools often have display characteristics that are commonly associated with human personality, and understanding this can help when it comes to evaluating, selecting, and implementing tools to support your software development process. This article will help you handle the people side of tools selection and adoption.

The testing craft is sometimes fascinated with high-tech, expensive tools that are intended to help managers keep up to date on what's going on. Yet, sometimes heavyweight tools aren't necessary. Michael Bolton describes how Paul Holland, a senior test manager, uses a decidedly low-tech approach to track and illustrate the testing story.

I often receive emails from recruiters that go something like this:

We are looking for a talented QA Engineer experienced in /test automation|Java|C#/ for our /test automation team|agile team/. Can you refer anyone?

*scream*

Here's what I replied to the latest one (I really did! I've only edited a little!):

Dear Recruiter,

A series of dining mishaps leads Lee to reflect on why mistakes happen in spite of well-defined requirements.

The demand for software environments has increased as more organizations use agile software development practices and are required to provide a fast turnaround of deliverable IT projects. Effective environment management improves the quality, availability, and efficiency of the environments in order to meet milestones, as well as ultimately reducing both the time to market and costs.

If you have recently transitioned to an agile team, you may have questions about the differences between user stories and use cases, especially how they differ from tradition requirements writing. In this article, Charles Suscheck defines each of these requirements types and uses a running example to illustrate how they differ in a real-world setting.