One characteristic of agile development is continuous involvement from testers throughout the process. Testers have a hard and busy job. Jeff has finally starting to understand why testing in agile development is fundamentally different.

While some debate which, if any, industry practices deserve the designation "best practices," this tongue-in-cheek look at the horrors of some of software's "worst practices" drives home the value of the good ones and may help us improve the quality of our software.

Testing professionals are often viewed as the pessimists of the software world. Some people think testers will do anything to prevent an application’s release into production. In reality, testers should be pro-active protectors of the organization and a strong voice for its customers-lines of business, end-users of the applications, system designers, developers, and the operations group responsible for application support. Theresa Lanowitz believes that testers should be customer advocates, representing all constituents in each and every stage of the application development lifecycle. As such, testers help ensure delivery of quality products that meet the needs of all. To be a successful customer advocate, you must understand and balance the complex web of requirements, constraints, roles, skills, and abilities of all stakeholders.

Esther Derby has noticed something lately, namely that when people write about collaboration, they discuss facilitated meetings. Well-run meetings that encourage participation and building consensus are certainly valuable, but there's more to collaboration than just well-run meetings. Esther explains that true collaboration assumes shared responsibility and shared ownership and boosts creativity and learning.