Petro Tarasenko "You've become a TL. What's next?"
1 like•56 views
The document provides advice for a new QA team lead on next steps. It suggests creating a solid plan that addresses current challenges, future vision, timeline, and key performance indicators. The plan should be shared with key stakeholders like testing team, managers, developers, and product teams. It also emphasizes learning about priorities, challenges, and allies/detractors. Finally, it advises rehearsing the plan to concisely convey necessary information to busy managers.
Petro Tarasenko "You've become a TL. What's next?"
- 1. 27.10.2019 You’ve become a QA TL. What’s next?
- 2. Петро Тарасенко В QA з 2013р. В IT з 2008 р. QA TL / QA Guild Master @ wix.com QA Meetups organizer in Dnipro
- 4. ✤C
- 7. Michael Bolton “As a member of the Context-Driven School Software testing, I maintain there’re no universally best results available from testing, just as there’re no BEST practices”
- 9. What to talk about? - What you expect from me? - What you expect from QA? - What works good with QA? - What doesn’t work with QA? - If we as QA could change something quickly and it made a big impact, what would it be?
- 10. Key people? - Testing team - Your manager - Dev teams, products, support
- 11. Testing team - Maturity(seniority) level - Project/Domain/Technical knowledge level
- 14. Your manager - Priorities - Expectations & Outcomes
- 17. Date Take your time and learn
- 18. Make a solid plan
- 19. Golden circle by Simon Sinek
- 20. What plan covers Plan can be either a document in the KB or Presentation Current status & Main challenges (WHY) Future vision & How it can be done (HOW) When and what exactly will be done (WHAT)
- 21. ✤ Main challenges ✤ The vision ✤ Automation ✤ QA development ✤ Knowledge base ✤ Processes ✤ Main KPI ✤ Main milestones (detailed plan) ✤ QA Efforts & Involvement
- 22. Current status & Main challenges - 3 people out of 5 are new - Big automation technical debt (Mobile is almost zero) - No transparency in automation coverage - Only 1 engineer is doing automation - QA is still out of time estimation process (sometimes QA becomes a bottleneck because few tasks come simultaneously) - Prod incidents because of missed regression bugs
- 24. Date
- 25. Date
- 27. Date
- 28. Date
- 29. Date
- 30. Engineers vs Manager timing version For Management For Engineers
- 33. Date Management usually doesn’t have much time…So…
- 34. Do a rehearse!
- 35. Date So true!!!
- 36. Date Execution
- 39. Questions?