CCME0141 Chap.11 Production Dossier and Critical Reflection
Production Dossier and Critical Reflection
Production Dossier and Critical Reflection turn production traces into evidence of decision-making. The dossier should document the taught workflow through carefully selected screenshots and annotations, including attempts, problems, compromises and changes. A screenshot becomes useful only when the reader knows what to notice, why a decision was made and how the result was judged.
The reflection introduces the project, relates external references to practice, addresses developed learning and connects the film and game parts of the module. It should evaluate rather than retell. Strong reflection names a decision, points to evidence, compares the result with the intention and transfers the lesson into a concrete future method. Honest limits are more credible than unsupported claims of complete success.
What this chapter covers
- 01
Evidence selection
- 02
Screenshot annotation
- 03
Research sources
- 04
Decision evaluation
- 05
Critical reflection
- 06
Future practice
Worked example · free
Reflect on a deformation repair
- 1Show the failed bend and identify the visible symptom.
- 1Annotate the incorrect vertex influence and topology relation.
- 1Show the corrected pose under the same view.
- 1Evaluate what improved and what remains unresolved.
- 1State how future testing will begin earlier. The mark allocation shown here is not an official university assessment scheme.
Key terms
- Production dossier
- A structured record of workflow evidence, decisions and development.
- Critical reflection
- An evidence-based evaluation of choices, outcomes, limits and later action.
- Reference practice
- An external work or method used transparently to inform a creative decision.
Production Dossier and Critical Reflection FAQ
What review can test whether the dossier and reflection are ready?
Print or view the dossier as a reader would and label the claim made by every selected image. Each item should identify the stage, decision, relevant evidence and result without requiring a live explanation from the maker. Remove interface screenshots that merely prove software use, and replace them with comparisons that reveal a change in form, method or outcome.
Check that annotations distinguish observation from interpretation: first state what visibly or audibly changed, then judge it against the project intention or technical criterion. Build at least one complete evidence chain from initial aim through problem, alternative, action, result and next practice. Confirm that failed tests are included only when they changed the method.
Audit references for accuracy and explain what each source contributed rather than placing citations beside generic influence claims. Read the critical reflection separately. Highlight sentences that only describe activity and revise them to identify a criterion, evidence and consequence. Keep claims proportional to the test; a small audience check can reveal confusion but cannot prove a universal response.
Connect film and games practice through a concrete transferable method such as iteration, attention, handoff, deformation testing or delivery verification. Then compare the dossier, reflection, render and editable project file for consistent terminology and version identity. Verify page order, legibility, captions and file names.
Ask a peer to reconstruct one decision using only the submitted evidence and note where context is missing. The work is ready when the artefacts do more than display effort: they allow another reader to follow why a choice changed, how the outcome was judged and what the maker will do differently in future practice.
What makes a screenshot useful evidence?
It should prove a problem, choice or change and retain enough interface or artefact context to make the relation understandable. The annotation then identifies what the reader should notice, why it mattered and what action followed.
How is reflection different from description?
Description tells the reader what happened. Reflection evaluates why a decision was made, how the result compared with the intention, what limitations remain and how the evidence will change later practice. Both may appear, but evaluation carries the learning.
How should I use external references?
Name the relevant feature or method, explain how it informed a specific decision and show where the project adapted or rejected it. Listing an admired work without a connection to process does not demonstrate research-led practice.
Assessment move
Build the dossier during production rather than reconstructing it near the deadline. Create sections for the taught workflow and place each selected image beside a short annotation that names the stage, attempted decision and visible result. Keep comparisons that explain why the artefact changed. Remove duplicate interface screenshots that add no new claim.
When a problem is unresolved, state its boundary and what would be tested next. Maintain accurate references and explain how each external source influenced a formal, technical or conceptual choice. For the reflection, allocate space according to the prompt: a concise project introduction, purposeful external references, learning outcomes developed and a final connection between film and game practice.
Draft from evidence chains rather than memory. Use a sentence sequence of decision, evidence, evaluation and next action. Replace vague growth claims with observable changes. Check that the dossier, reflection, render and project file describe the same final version and terminology.
Finish by identifying one transferable practice, such as earlier deformation testing or clearer team handoffs, and explain how it will alter the method used in the next project. This closes the practice-based research loop.