Downloaded 14 times
Uploaded byMaaret Pyhäjärvi
ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement
The document discusses navigating improvement at work and changing more than we think is possible. It provides tips for naming discomfort, sharing work, dealing with rejection of ideas, and turning failures into learning opportunities. Specific problems mentioned include long release testing times, testing queues, and meeting expectations. Corresponding solutions proposed include more frequent releases, exploratory testing, test automation, discussing testing earlier, and explaining/stretching rules and expectations.
More Related Content
Similar to ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement
ATAGTR Keynote: I have a rock in my shoe - Navigating Improvement
- 1. @maaretp http://maaretp.com I havea Rock in My Shoe Navigating Improvement by Maaret Pyhäjärvi
- 2.
- 3.
- 4.
- 5.
- 6. @maaretp http://maaretp.com We canchange more than we think at work… but it requires persistence.
- 7. @maaretp http://maaretp.com Step 1.Name Your Discomfort *) It is HARD to know what bothers *you*
- 8. @maaretp http://maaretp.com sufficient coverage Problem:• Release testing takes 32 days • …and misses all the results found later Solution: • More frequent releases – shorter leash from working baseline • Contemporary exploratory testing • Test automation strategy • Move to better through small changes • Measure change and green
- 9. @maaretp http://maaretp.com sharing work Problem:• Much to test, accruing a queue • Developers test but their way Solution: • Power of product owner in reallocating team’s priorities • Adding +1 enough times makes the whole team over time • Mix of attended testing tasks with test automation programming tasks • Discuss ideas of testing earlier but maintain agency * power to decide with knowledge and attitude that goes with power
- 10. @maaretp http://maaretp.com You MayHave Also Heard… “Tester is a ROLE in a team that ANYONE in team could pick up” Yes, and…
- 11. @maaretp http://maaretp.com “This isa lot of responsibility for an engineering manager to shoulder…” - @johncuttlefish July 29th, 2021
- 12.
- 13. @maaretp http://maaretp.com living upto expectations Problem: • Release and story definition of done for organization • Culture of requiring Solution: • Explain, illustrate, communicate • Shift left the problem – requirements are scope management • Stretch the rules • Change the rules
- 14.
- 15. @maaretp http://maaretp.com Dealing withRejection https://visible-quality.blogspot.com/2020/07/dealing-with-rejection-in-teams.html Repetition Finding the Right Time Prioritize WhatYou Ask For Finding Right Words Finding Right Messenger Finding Right Medium Convincing a Subgroup Make It Sound Temporary Confronting the Rejection Patterns Visualizing of Whose Ideas WeWent With Showing It Works Without The Others Build a Track Record Create a Patience Raindance Amplify Ideas of Others
- 16.
- 17. @maaretp http://maaretp.com A bonusrock… from a job interview this week ☺ * Turning a failure into a learning blog post
- 18. @maaretp http://maaretp.com #function toconvert integer to English for values from 0 to 999
- 19. @maaretp http://maaretp.com Airing outthe Stale Practices Local optimum
- 20. @maaretp http://maaretp.com 2020 2016 MIATPP MostInfluential Agile Testing Professional Person #PayToSpeak #TechVoices #EnsembleTesting #EnsembleProgramming #StrongStylePairing #ExploratoryTesting #TestAutomation #ModernAgile #AwesomeTesters Maaret Pyhäjärvi (from Finland) Email: maaret@iki.fi Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)