Until now there have been two camps for Application Quality Management (AQM) systems. Traditional Tools like HP QC that have proved inflexible for agile developments and maintenance heavy, or new agile tools from Version One or Rally Software, which are agile specific tools and not suitable for use outside agile environments or corporate-wide where teams are using a mix of processes. With many organisations moving to or experimenting with Agile, Original Software has been acclaimed by the analyst community as the best solution for supporting Agile. [Original Software nominated Agile Best Tool Award] Just as improvements in developer's software tools and methods have enabled a shift in development approaches, next generation technology for test automation is similarly reframing the opportunities for testers to automate earlier in the delivery cycle without incurring the heavy burden of script maintenance so often associated with traditional automation tools. This means that not only can an agile environment be adopted, application quality is maintained and the total testing time reduced. - See more at: http://www.origsoft.com/solutions/agile-software-testing/

1. Optimising Quality Assurance in an Agile World
Jonathan Pearson
Senior Solutions Consultant
Original Software

2. Quick Poll
How Agile is your company?
 All developments
 Majority of projects
 Piloting agile
 R & D
 No current plans

3. How is QA different in Agile?
 Whole Team Approach
 Continuous feedback
 Automation
 Respond to change
 No documentation overheads
 Collaboration

4. Agile QA landscape

5. Design Build Re-Factor
Plan
Review
Adapt
Continuous Validation and Feedback
Iteration
QA Strategy Application Quality Management
Quality trumps Quantity
Priority trumps Productivity
Elegant simplicity in design
Customer Collaboration
Quality Assurance Overview
Inspection
Big Picture View
Outside Collaboration
TDD
Pair-Programming
Continuous Integration
Re-Align User Stories
Manage Test Assets
Maintain Automation

6. 1 - Pitfalls when introducing Agile
 Lack of training & preparation

7.  Inadequate management tools
» Waterfall centric e.g. QC
» Designed for developers only
» Needs to be flexible as the
processes adapt
» Instant position information e.g.
burndown
2 - Pitfalls when introducing Agile

8.  Inadequate Regression Testing
» Very difficult to do manually
» Often done outside the iteration
» Lack of coverage leads to technical
debt
» Slows velocity
3 - Pitfalls when introducing Agile

9. Quick Poll
How do you currently carry out regression
testing for your Agile project?
 Within a sprint
 After a sprint
 Regression testing is carried out by a separate team
 We don’t do any regression testing

10.  Geographic Dislocation
» Collaboration can be difficult
» Not conducive to the ‘Whole Team’
approach
» More documentation often required
4 - Pitfalls when introducing Agile

11.  Compliance & Audit
» Needs can oppose goals of agile
» Specific quality gates may be
required
» Audit documentation often required
5 - Pitfalls when introducing Agile

12. So what's the best way to start?
AGILE!

13. Set Expectations

14. Sequential to Parallel
Dev Test Business

15. Stepping to (agile) Heaven

16. Manual Testing
Why so manual?
Why so slow?
Repetition,
repetition,
repetition …

17. Manumation
Developer speed
Re-tests
Education
Pre-requisite for
agile regression

18. Why Automate?
Short cycle times
Regression testing in sprints?
Multiple configurations
Reduce technical debt

19. Regression, But When?
Sprint 1 Sprint 2 Sprint 3 Regression
Sprint 1 Sprint 2 Sprint 3
In
Sprint
Release
Trains

20. Full Automation
Low emotional debt
Adaptable
In AND after sprint

21. Agile Testing Best Practice Poster
http://www.origsoft.com/contact/

22. Questions?
www.origsoft.com