New team + new people + new product = *lots of things*Such as:
· New views and old views
· Various personalities
· Different ways of *doing things*
· Various habits
· Various definitions
· Potential confusion
These *things* can be extrapolated to a degree that, while I do not wish to focus on it, may cause a great deal of stress to a team. Hopefully (before, or at least when it hits the fan) once realized, the need for reassessing and defining the strategy becomes evident.In our case, it indeed became evident.
The test manager now oversees people from several different teams/products. The products differ as much as the people/personalities do.Not only are the people/products/personalities different, but the overall release season was, well, to put it mildly – yikes!
We knew we needed to make some changes, to the degree that we have control over them, within our testing department. We needed a new strategy.The test manager began to construct the strategy, and brought in a few of us to assist with the nuts and bolts of it. We went back and forth for some time on the wording of it. (I know it is hard to believe that I would argue over words/meanings/possible assumption(s) J) We eventually got the initial strategy together and it is something I feel I can stand behind.
Once we completed that, the test manager did a pretty cool thing, in my opinion. He sent an email to whole team with the following three questions:· Who are we?
· What do we do?
· Why is it valuable to the company?
A few people answered. It would have been *better* in my eyes, if everyone had, but it made me realize something. While the team may be made up of differing people/personalities, we really *need* to be, initially in the same book, close to being in the same chapter, and ultimately landing on the same page when it comes to our mission.
While thinking on this, I found a darn good blog post from Scott Barber: Business Value of Testing: Bugs ≠ Mission.
I have forwarded the link to blog post to my test manager/team.
Quote: “So, to all you testers I ask: “Do you *really* know your mission, do you have a task posing as a mission, or do you just do what you do because that’s what testers do?””