cgd3sm

=Sam McIlmunn=


 * clips** - none presented - 0%


 * personal report** - this is a good report. I can see how you arrived and fit in. I can also see some of the problems that arose. What you are lacing is a final: so what? section which looks forward. Think: what does this mean for the next time I join a project team, or the next time I am in a team and a new member joins? Just take a single issue from the project and reflect upon it. After a short while you learn how to foresee issues and prevent problems (not entirely, but better than repeating the same ol' car crash each time.) O, good start, and try to look deeper and longer next time. - B1 (62%)


 * QA Plan** - the QA plan is a good copy of the QA document, but does not show such as timings, target audiences, data analysis approaches, actions planned, etc. A plan should say all these things too - D (32%)


 * roll-out plan** - this is Ok as a plan, but not really as a working plan - it is better if it shows what was planned and what happened together. I suppose you need to get into a package that will help you with Gantt and PERT style diagramming. DO look these up (they are in MS Project, but that's a huge product jsut to get a few blobs-and-lines out of). But, thanks for the little bit of chat at the end of the dates list. So, more work in presenting this and using it as a working plan, but good you had a detailed plan to an extent. B2 (57%)


 * QA data presentation** - this is not clearly presented, but is subsumed in the analysis report - do show the actual real data, even as scans. However, the data can be 'seen', if not in its entirety - D (35%)


 * QA data analysis** - I like the bit about not gathering-in the forms. You need to hover over and make sure this happens. After all, the prupose of testing is NOT testing, it is FEEDBACK on testing. The analysis is OK and shows some useful insights. Get more data and make sure you present it as provably having been done. B1 (62%)