The Latest

For some organizations Agile methodologies like XP, Scrum, and Crystal work well off-the-shelf.

Many people talk about an end-to-end software development process in which requirements are developed and transitioned seamlessly into code with tests tracing back to the requirements.

Congratulations! Your team is entrusted with testing the next release of an excellent product, one your customers have depended on for years.

Agile development projects are different. Sure, they still have high-level business requirements, but they usually lack system descriptions, technical design documents, and system architectures.

Given the choice between making an estimate of the time and resources to complete a project or getting root canal surgery, most of us would rush to the dentist’s office. We know that the pain of a root canal is short lived ...

An old-yet still true-saying is "You can't test quality into a software product." By planning for the quality expected in your software, your team and management will focus on the big picture-integrating development methods, the test processe

We often hear about the difficulties and failures surrounding Agile methodologies. Articles describe everything from team and execution issues to the inadequacy of Agile methods on large projects and failures in large organizations.