"Challenges Faced by Testers Working on Agile Teams" by Aldo Rall As a tester, moving into an Agile team can be frustrating and difficult. Often times leaving testers disillusioned and projects suffering due to a lack of quality. In this talk, Aldo Rall will be looking at the typical challenges that testers face when moving into the Agile world, and touch on some key points that needs consideration for testers to successfully adapt in this new and often strange world called Agile.

2. Challenges Faced by Testers starting work in Agile Teams
IC Agile Attendance Code: Indigo611
Copyright 2014

3. From a question on LinkedIn
“Share a few challenges ….in agile environments”

4. To Old Paradigms being Old

5. A “newer” Old Paradigm
•Dev team decided to “Go agile”
•Water-Scrum-Fall types
•AGINO
–Agile in name only
•SINO
–Scrum in name only
•Testing is still done after development

6. Talking the Talk, Without Walking

7. Let us look at how testers spend their time (1)
Source: The Future of Software Testing: Where do Testers Spend Their Time?, Published by IBM, October 2014

8. Let us look at how testers spend their time (2)
Source: The Future of Software Testing: Where do Testers Spend Their Time?, Published by IBM, October 2014

9. Let us look at how testers spend their time (3)
Source: The Future of Software Testing: Where do Testers Spend Their Time?, Published by IBM, October 2014

10. Signs of ‘AGINO’
Tools
Techniques
SDLC Approach
Structuring of Work

11. Why these shortcomings?
•Scrum not addressing Quality
•Testing is not Continuous
–How do you do testing as an ongoing activity in a sprint, and not fall into a mini waterfall implementation inside a sprint?
•Outsourcing of testing is still prevalent
–If software development is a core competence in Orgs –why outsource testing?
•Automation not addressed properly
–Build up technical debt
–Skills?
•Transitioning Testers
–“If you fail to transition testers to the correct mindset before trying to tackle the process changes, then you’re setting your team up for failure”
See “4 Steps Towards Developing the Agile Testing Mindset for Successful Transition to Agile Process” -www.SoftwareTestingHelp.com

12. And… some answers from LinkedIn
•“old testing approaches are shoehorned in agile environments with bad results”
•“testing is not a phasebut a continuous activity that happens at all levels”
•“need for a culture change where testing is responsibility of the agile team and not of the tester”
•“testers to have T-shaped skills and work in close collaboration with developers and product owners and not in isolated test teams”
•“unlearningthat traditional testers need to go through before they are ready to work in an agile environment where they are no longer the quality police”
•“increased need for test automation due to the frequent releases... test automation … is a development activity”
•“some teams think it is enough writing test automation at the UI level and not at the unit or integration level”
•“in agile context, distributed teamsare often a false economy”

13. What the Research is Saying
Source: The Future of Software Testing: Where do Testers Spend Their Time?, Published by IBM, October 2014

14. Source: The Future of Software Testing: Where do Testers Spend Their Time?, Published by IBM, October 2014

15. Signposts to a Shifting Paradigm
Tools
Techniques
SDLC Approach
Structuring of Work

16. In Closing
IC Agile Attendance Code: Indigo611