At IBM’s Innovate conference a four person panel (Scott Ambler, Kim Warner, Reed Figgins, Brian Massey) addressed several issues with Agile and Testing. The starting question was the title line here. Agile generally thinks about small teams 5-15 people who work in close proximity (possibly the same room) with each other. Teams with the greatest success with Agile are co-located teams because they have the highest level of collaboration and this drives knowledge sharing and quality. Embedding testers in the agile team means that you are taking a proactive approach to quality and a recognition that quality is broader than just the code. However co-location will create the largest disruption, some of the test team may not fit well, and it can over time (if a team stays together) create blind-spots as the team begins to think more alike. While you should embed testers in agile teams, you should also have independent teams (potentially organized in COEs) that focus on automation, load/stress/performance, and to act as an independent IV&V team. The bottom line is Agile can provide many benefits but it is a transformation and requires discipline and the right people and not everything will fit in the agile box.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The IoT In Manufacturing Operations: Where Are We Now?
The Internet of Things (IoT) is a paradigm shift for manufacturing operations. Its fanfare creates uncertainty in state-of-the-art technology...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.