As I mentioned last week, in this sprint we have been working with teams within the team. It has been ok but it has also proven to create a new kind of problem. Because we are working on different features we test on different releases (not because we use the great system of branching, but because we ignore the releases that weren't meant for our specific feature.). The problem is that with every release we should update the changes in the testlog/playbook. After a while it is hard to know which risks are connected to which release. And right now I have no idea any more.
It would create a bit of overhead having different testlogs (I'm naming the document that we use to visualize risks/changes and ends up being the test report. Until it is a test report, it is a testlog.) And, if we have two different testlogs, do we merge them into one testreport at the end on the sprint? Or wait until we have done our sprint end testing and then merge everything together? Suggestion anybody?
Enough about that, today it is bwin Games summer party, so I'm off for some food and drinks and good times, see you next week!
This comment has been removed by the author.
ReplyDelete