IS YOUR DEVELOPMENT TEAM USING AN ITERATIVE DEVELOPMENT PROCESS? WHETHER YOU CALL IT AGILE, SCRUM, KANBAN OR SOMETHING ELSE, THE QA TEAM WILL BE MOST EFFECTIVE IF THEY ADAPT TO AN AGILE APPROACH.
While every project and organization is different, these five concepts are a great starting point:
1. Dedicated QA team. Having full-time members for the duration of the project is key. Documentation can be minimal, and the team can move fast if the project is everyone’s highest priority.
2. Quality ownership. The QA team needs to feel ownership of overall product quality. While it’s important to run test cases and write defects, the end goal is to deliver a quality product. Do whatever it takes to achieve that!
3. On-going communication. One of the reasons that agile development works is because it breaks down functional silos. A key aspect is on-going, direct communication between team members. Communicating only through email, the defect tracking system and weekly meetings will slow you down. Instead, talk to the developers, product owner, and business analyst as questions come up. You’ll resolve issues quickly and efficiently.
4. Find (and fix) bugs early. The goal is to find defects as soon as they are introduced and get them fixed right away. Testing should take place as soon as there is a testable chunk of code, regardless of when that happens or how small the testable functionality is. Don’t wait until development is complete.
5. Strong QA fundamentals. Regardless of the development process you’re using, it’s important that the QA team knows how to design great test cases, write excellent bug reports and find bugs! Your team likely already has these skills, but if not, don’t overlook the fundamentals.
ATG offers a variety of services to support your QA organization’s transition to agile. For more information see: Quality Assurance and Performance > > >
Written by Julie Loucks, Quality Assurance Manager and Agile Software Testing Lead.