Hi,
I think we need to spend sometime thinking and talking about how to track effectively our testing tasks, since we are not in a release testing mode tacking by mks, the email communication recently is not so effective.
The tasks not properly tracked:
1. For the task in email I am asking only UI captures for 10.3.0 OS for two old client for reference purpose, I believe I get UI capture files for all 10.2. to 10.3 OS, and I do not see report mention what client build is, from this morning email.
2. The sanity is for new Cisco client on BES 10 while not BES12.
Please don’t take it personally for EIM, the challenge are for our both side in such a remote, time shifted work relation, I believe my email sometime is too brief, and requests becomes scattered… and eventually I found the team lost a good tracking as what the scope, priority is…..
We can discuss this, and if you have a better idea, please put forward.
This is what I’m thinking and to suggest, the task request email from me, like the one attached in grey , SDL tester to print it out in paper, review it if any question and you can ask, then the SDL team has the full ownership to tracking till the end of tasks in request be fulfilled, including modification of the task, add/remove of content through the later email communication. This is also a good way to help testers developing their task management skills.
I will support the team in case any question or support needed, but I will not do the tracking job anymore, I will only expect to see the process in daily report, till every tasks in the original request been finished.
I have spent so much time to write email back and forward in last weeks for this, to check what is done, what is not done. I have two projects in hand, and both will be ramping up soon.