It has been a busy couple of months for the project, multiple streams of work happening at once.
Sometimes taking a step back is a really nice thing to do, allow the other members of your team take stories that you could be doing while allowing you to get the bigger picture of how everything is going to fit together. This can allow you to resolve issues found before getting more people involved meaning leaner testing times and quicker story delivery.
I tried to explain my recent example of this but it got complicated and confusing :) this is a simplified version:
A was trying to talk to B through C
B required something from C that it was not passing through
B rejected C so A could not happen.
We passed A by skipping C as it was just a middle man, but could have spent a lot of time debugging A if we hadn't seen that B didn't need the required variable (even though it was in the requirements!).
B got the variable removed by the developer.
A Could be passed without the completion of B.
As the streams of work are quite close at the moment, passing on knowledge of what the each tester is doing is quite important as shown with the example above, both parts A and B were implemented at the same time by 2 sets of people meaning communication is key :)
No comments:
Post a Comment