The Latest

By using an approach similar to that used by surfers to catch waves, you can effectively help your team transition to agility. Scott presents a four-stage process that alternates training with coaching and doing with learning.

In this interview, principal consultant and Agile Artisans founder, Jared Richardson, explains how misunderstanding requirements can cause major issues within an organization. He covers why team members need to communicate, how big projects are often mishandled, and the value of agile.

In this interview, Andy Berner of QSM talks about his upcoming presentation, the importance of keeping a well-groomed backlog, the pitfalls of the impossible zone, and why it's vital that you and your team keep your tools serving you and not the other way around. 

Alan Crouch addresses the question most commonly raised by those who are new to security testing: "How does security testing fit in my QA process?" Alan explains that security testing shouldn't be limited to the QA process, but instead should be applied throughout the entire software development lifecycle. Read this FAQ column for suggestions on how to improve your chances for success in catching security issues.

Practitioner, manager, and consultant Stephen Vance explains why we still need testers. Instead of just using the testing process at the end of a development cycle, Vance argues for integrated testing that solves issues throughout the process.

Prakash Pujar writes about his team's experience adopting some of the best agile practices to make their process extra lean and increase efficiency by increasing throughput—all without any change to the agile framework his team was following before and after. Here, he talks about some of the lean practices that worked for them.

Matt Heusser presents ten key factors to establish a team cadence—the time between running tests and getting a product into production. The shorter the cadence, the less time spent in test/fix/retest land, and the more time spent working on new features.