cgd3cp

=Chris Parkinson=


 * clips** - none presented - 0%


 * personal report** - this is one of the better of these reports presented by the class. You show a strong attachment to events, reflecting as you go along. i like the 'this didn't happen so I did' part of the report. This shows a strong approach. Its a pity the module felt weak overall as it seemed to show a 'how not to' approach, but its best to elarn in a safe area. I'll try and make next year go better. Overall, nice reflecting, and room for more - B1 (67%)


 * 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%)