In our continuing effort to be the best source of information for keeping testers and test teams current, we have another issue to explore testing in Agile development. As Agile evolves, systemic problems arise and common rough situations become apparent. We want to provide solutions.
For anyone who has worked on Agile projects, especially if you have worked at more than one company or for a few clients, you know “testing in Agile” can be an adventure. Remember there are no “rules” or best practices for Agile testing. There are better practices. Every team and Scrum implementation is unique. This is still evolving.
The varieties of Agile implementations, most commonly Scrum, have a nontraditional concept of testing. Yet, most organizations still want someone to do the tasks associated with traditional testing, such as validation, regression testing, bug hunting, exploratory testing, scenario testing, data driven testing, etc. These words have different connotations in Scrum and Agile.
This month we are tackling more Agile topics with a specific focus on how these practices impact testing. As Agile matures and comes of age we are learning more, adjusting our practices, modifying our strategies and hopefully communicating better; we are being Agile.
In this issue, Emily Bache highlights principles to help you plan your testing strategy; I warn teams about the implications of technical debt; David Taber explains that if your team is set up to handle it, Agile can greatly benefit your projects in the cloud; Larry Maccherone looks at why Agile is becoming a vital strategy for small and large businesses; Joel Semeniuk breaks down his predictions on current and future Agile trends and what they mean for testing teams; John Turner reviews A Practical Guide for Testers and Agile Teams by Lisa Crispin and Janet Gregory.
As always, we hope this information is helping you solve problems and release higher quality products. September’s issue is on Mobile Testing.