Getting consensus around a test strategy is done best by designing it in collaboration with the team.<\/span><\/span><\/p>\n

Sometimes the most experienced person in testing or software quality is given the responsibility, They’ll put together a strategy based on best practices they feel should be followed<\/p>\n

The problem:
\n1. There is no shared sense of responsibility across the team, which makes this ‘my’ test strategy, not ‘our’ test strategy
\n2. The best practice we thought of might not always be the most appropriate
\n3. The target vision should be set, however how to get there will be an iterative process, is should evolve collectively as we move along<\/p>\n

I prefer to set a target vision of where we want to be. The steps to get there will be taken:
\n1. Collaboratively
\n2. One step at a time
\n3. And the approach will evolve as we test and learn<\/p>\n

Improving your quality engineering processes is going to an ‘evolution’, don’t make it a ‘revolution’ !<\/p>\n

Just an hour left in the panel discussion I’m joining to tall about ‘Communicating Test Strategies’ followed by my talk on Transformation and the role of test leadership at\u00a0#tmatlc2020<\/a><\/p>\n

#RedefiningSoftwareQuality<\/a>\u00a0#QualityTransformation<\/a>\u00a0#TestStrategy<\/a>\u00a0#AgileTransformation<\/a><\/p>\n<\/div>\n<\/div>\n<\/div>\n