cgd1ti

Tomas Iversen


 * clips** - these are well selected and well presented; there is ever an issue with in-game clips that they can be dark, so you may need to do some photoshopping in later projects. But, overall, good work - B1 (63%)


 * personal report** - a strong report. The issue on software not doing what it should do is annoying, but not atypical. The issue of being misdirected is annoying and probably relates to this being the first run of the module pair (not an excuse, just a feature of any new system, so watch for this kind of thing in the future). The report continues in a kinda non-reflective way. What you need to ask is: what would I do different next time? what might go wrong? what can I do to prepare for this? The idea is to be better prepared for poop-happens next time (to put it in crudely, but clearly) for every development will have problems. So, a good recount, but little refelection - B2 (55%)


 * QA Plan** - this is an outworking of the QA plan, but needs quite a bit more evidence of it having been planned as well as done (but more of that later in the testing report, I expect.) You should have shown more visibile consideration of who will test, when they willt est, what they will test, how you will act upon feedback, etc. So, some evidence, but not a lot - D (32%)


 * roll-out plan** - this is much better. With a major, totally-thought-out project you will get more and more detail to such a plan. but this shows a good depth of thought, and a clarity of rpesentation which shows coverage of major aspects of the development. It reflects the fact that the team, while not perfect in tis planning, was never overwhelmed by events, but reacted well to them. A good piece of work, even perhaps an examplar of how to keep a lot of detail in a small place - A (72%)


 * QA data gathering** - a very clear presentation of this work. Not too many words. Goo to see how the three different testing scenarios are presented: as you show, just be honest and make the most of what you find. The data analyses are good. I like that you have presented both qualitative (words) and quantitative (numbers) analyses, and not tried to over-read into the data gathered. Thanks for the scans too as extra proof. A strong piece of work - A (71%)