A tester's survival guide for agile transition

Agile transformation is challenging, especially for testers who are accustomed to working in a silo. As a lone tester on a team, it’s difficult to find the time to learn new methodologies and adapt to be able to incorporate them as part of your process.

While it’s apparent that an agile approach can bring forth several benefits such as the faster delivery of new features, it’s not always obvious what a tester should do to be a part of this change.

Although there’s literature covering the tester’s role in an agile environment, this talk will move beyond the theory and provide a journey of a tester’s experience in making this transformation.

Make no mistake... transitioning to agile is not an easy feat, so this talk will not only cover my personal successes but will also highlight my failures and critical lessons learned.

Transcript

1. A tester’s survival guide for agile transition Parveen Khan | Senior Test Engineer | Scott Logic @parveen_khan10
2. @parveen_khan10
3. Following Waterfall process! @parveen_khan10
4. • Requirements gathering • Design • Development • Testing @parveen_khan10
5. Why agile? @parveen_khan10
6. Started reading about it! @parveen_khan10
7. @parveen_khan10
8. 2 week sprint @parveen_khan10
9. From once in 3 months to once in 2 weeks @parveen_khan10
10. Sprint attack @parveen_khan10
11. Too many questions! @parveen_khan10
12. @parveen_khan10 Biggest question
13. @parveen_khan10
14. Three Keys! @parveen_khan10
15. Collaboration Planning Decision making @parveen_khan10
16. Collaboration @parveen_khan10
17. Team collaboration @parveen_khan10
18. Scrum as a Collaboration tool! @parveen_khan10
19. Why and how we started scrum! @parveen_khan10
20. Whole team trust! @parveen_khan10
21. Planning @parveen_khan10
22. - Plan for estimations - Plan for writing test cases - Plan for exploratory testing @parveen_khan10
23. Plan for estimation @parveen_khan10
24. Problems while estimating @parveen_khan10
25. Breaking down estimations @parveen_khan10
26. • Reviewing requirements • Writing test cases • Functional testing • Exploratory testing • Regression testing • Contingency time for retesting of raised issues @parveen_khan10
27. Plan for writing test cases @parveen_khan10
28. Detailed test cases as in waterfall @parveen_khan10
29. Too time consuming @parveen_khan10
30. High level test scenarios @parveen_khan10
31. @parveen_khan10
32. Plan for Exploratory testing! @parveen_khan10
33. Exploring the application @parveen_khan10
34. New ideas and edge cases @parveen_khan10
35. #PQIP (Problem, Question,Idea, Praise ) @parveen_khan10
36. @parveen_khan10 By @simon_tomes
37. Extra assurance and satisfaction @parveen_khan10
38. Decision Making @parveen_khan10
39. Quick decision making! @parveen_khan10
40. Regression run @parveen_khan10
41. Feeling More Valued! @parveen_khan10
42. Key takeaways! @parveen_khan10
43. Stand up/Scrum meeting is a small thing that is surprisingly very important @parveen_khan10
44. • Planning in agile is part of every day • You need to plan continuously and constantly @parveen_khan10
45. • Being proactive • Have courage • Taking initiative • Leading instead of following @parveen_khan10
46. We were panicked initially but we embraced the change!! @parveen_khan10
47. Happy testing ever after @parveen_khan10
48. Thank You! @parveen_khan10 You can find my slides here - https://speakerdeck.com/parveenkhan/a-testers-survival-guide-for-agile-transition
49. @parveen_khan10 @spkeazee @techgirl1908 @maartep
50. @parveen_khan10 Useful resources: • Agile Testing : A practical guide for testers and agile team • Sample PQIP session • Exploratory Testing by Maaret
51. @parveen_khan10 Please, give me any kind of feedback