cgd3mm


 * Max McIlmunn**


 * clips** - none presented - 0%


 * personal report** - this is a good blow by blow account of what happened, when and why. It is good to be able to see what the development meant from within, but you do need to take some time to stop and think about what this means for your future roles in later development projects. You need to stop and reflect: why did that happen? this then helps you look forward and say how do I ensure the future is better? So, good, but needs that bit more insight - B1 (60%)


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