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
13. @maaretp http://maaretp.com
living up to 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
15. @maaretp http://maaretp.com
Dealing with Rejection
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