speculation
noun
1. the forming of a theory or conjecture without firm evidence.
About one year ago
I am not sure how I came to this idea but it sounded like this "why not make the test lead a rotational position instead of been assigned to one person". It sounded really risky speculation at that time. There was some uncertainties like: how my manager will react, how the developers will react and at the end I was not sure if all QAs would like it. And finally we could blow up some releases because of such change.
So I defined simple rules that were presented and everyone was excited...
Present time
After this year of testing lead rotation I can share the following observations
With time it seems like that actually the test lead role changes its meaning for us. Here is one example. When someone has an idea he doesn't need to consult the test lead. He is a test lead because we are the test leads. We all share the responsibility of the role. We even compete in the best sense of this word. We are trying and sometimes failing but this is OK - we are the lead, we are the champions.
PS: Here is something you may find interesting
noun
1. the forming of a theory or conjecture without firm evidence.
About one year ago
I am not sure how I came to this idea but it sounded like this "why not make the test lead a rotational position instead of been assigned to one person". It sounded really risky speculation at that time. There was some uncertainties like: how my manager will react, how the developers will react and at the end I was not sure if all QAs would like it. And finally we could blow up some releases because of such change.
So I defined simple rules that were presented and everyone was excited...
Present time
After this year of testing lead rotation I can share the following observations
- All QAs choose to participate
- There was no major problems in product quality because of this initiative
- Each QA learned from others and added his own touch to the role
- There is a motivational boost
- There is a feeling of equality
- Seniors saw that juniors have done well and respect them
- Juniors felt responsible and understand what seniority is
- Developers noticed the success of each QA and have positive feedback
- With simple planing the test lead role is never on vacation during release
- The team is capable of releases with few members missing without any doubts
With time it seems like that actually the test lead role changes its meaning for us. Here is one example. When someone has an idea he doesn't need to consult the test lead. He is a test lead because we are the test leads. We all share the responsibility of the role. We even compete in the best sense of this word. We are trying and sometimes failing but this is OK - we are the lead, we are the champions.
PS: Here is something you may find interesting
No comments:
Post a Comment