Testing on other projects

One of my requirements for starting to work for TUI Nordic was that I was to be able to participate as a tester. For me as a project manager, testing enables me to get to learn the system and the users in a very easy and for filling way, but it also makes it possible to become a real team member. In TUI Nordic, the project manager fills the product owner role in scrum projects and since I’m a firm believer in product owners being a part of the scrum team, this is a easy way to do that. Stating that one is a team member is one thing, but if you don’t do any actual work and function as a chicken, you’re not a real team member, indifferent of how much coffee you bring the guys.

The passed week, I’ve tested a new experience with testing. We’re completing to projects at the same time and since we work with shared code, our projects are really integrated. So, I asked if I couldn’t participate as a tester of the other project. Really interesting. I can get a little bit of insight in the project manager skills of another project manager from an inside perspective, but I also learn more about being a tester. In all other projects I’ve been a tester in; I’ve known all the objectives and known the project in all details. Known what has been decided and which decisions are lacking.

The difference is huge. I’ve really learnt how important for testers to learn about all those decisions. But how? An extensive list? I don’t know. Do you?

Advertisement