Project Review Reflection

Overview

In lesson 27 of 30 in Infrastructure Skills Development, students evaluate their completed technological projects against the original brief, evidence gathered during development, and stakeholder feedback. They identify successful decisions, limitations, and realistic improvements before preparing a concise individual reflection for their project evidence.

Learning intentions

• WALT evaluate a completed project against its brief and specifications.
• WALT use testing results and stakeholder feedback as evidence for judgements.
• WALT explain how planning, materials, techniques, and design decisions affected the outcome.
• WALT identify justified improvements for future development.

Success criteria

• I can compare my outcome with its conceptual statement and specifications.
• I can support my judgements with specific testing, stakeholder, or observational evidence.
• I can explain what I learned and why particular decisions were effective or ineffective.
• I can identify achievable improvements and explain how they would increase fitness for purpose.

Curriculum links

• Undertake effective development to make and trial a prototype: use testing and stakeholder feedback to evaluate fitness for purpose and explain decisions to accept or modify a prototype.
• Select and use planning tools to manage the development of an outcome: review progress, resources, goals, and planning decisions.
• Undertake brief development to address an issue: revisit the conceptual statement, specifications, stakeholders, and intended environment.
• Demonstrate understanding of the nature of technological outcomes: explain how physical and functional attributes contribute to fitness for purpose.

Lesson structure (120 minutes)

1. 0–10 min · Reconnect and set the purpose. Teacher opens the project review introduction slides with the question, “Is a completed project automatically a successful technological outcome?” and outlines the review process and expectations for respectful critique. Students silently rate their project confidence from 1–5 and record one feature they believe is successful.

2. 10–25 min · Model evidence-based evaluation. Teacher displays an anonymised project example in the worked evaluation example and models the difference between description (“the join is loose”) and evaluation (“the loose join means the product does not meet its durability specification”). Students help classify statements as description, evidence, evaluation, or improvement, then suggest stronger evidence for one statement.

3. 25–40 min · Revisit the brief and evidence. Teacher distributes the project review and reflection worksheet and directs students to gather their brief, planning tools, testing records, photographs, feedback, and prototype. Students complete the evidence inventory, highlighting each specification and locating at least one piece of evidence that shows whether it was met.

4. 40–65 min · Individual project audit. Teacher conferences with students, prompting them to consider the physical and social environment, users, resources, time management, safety, materials, techniques, and design priorities. Students complete the audit table, rating each specification as met, partly met, or not met, and justify every rating with specific evidence rather than personal preference.

5. 65–85 min · Structured peer review. Teacher places students in groups of four and displays the peer-review protocol in the peer feedback instructions: presenter, evidence-checker, questioner, and recorder; rotate roles after each review. Students present their project in two minutes, receive two strengths and one question or improvement suggestion, and record feedback that is relevant to the brief and intended users.

6. 85–105 min · Reflection and improvement decisions. Teacher models a reflective paragraph using the prompts on the reflection and improvement sections and emphasises that high-quality responses explain causes and consequences. Students write a structured reflection covering the most effective decision, one limitation and its cause, what testing or feedback revealed, and two prioritised improvements, including the resources and time each would require.

7. 105–120 min · Share, submit, and exit check. Teacher invites several students to share one evidence-based insight, then uses the plenary and exit questions to revisit the opening question and remind students how today’s reflection will inform final project documentation in lessons 28–30. Students submit the completed worksheet or photograph it for their digital portfolio and answer the exit question: “What single change would most improve your outcome’s fitness for purpose, and what evidence supports this?”

Resources

• the project review introduction slides
• the project review and reflection worksheet
• Students’ completed projects or prototypes
• Original conceptual statement and specifications
• Planning tools, such as action plans, timelines, journals, or Gantt charts
• Testing records, photographs, measurements, and stakeholder feedback
• Pens, highlighters, and sticky notes
• Digital portfolio or class learning-management system
• Timer and visible review protocol

Assessment

• During the evidence inventory and project audit, check that students refer to specifications and use observable evidence rather than unsupported opinions.
• During peer review, listen for questions and feedback connected to users, environment, function, materials, techniques, and fitness for purpose.
• Collect the reflection worksheet and exit response. Look for a clear judgement, evidence-based explanation, identification of causes, and realistic improvements linked to available time and resources.

Differentiation

• Provide sentence starters on the worksheet: “The evidence shows…”, “This decision was effective because…”, “The main limitation resulted from…”, and “To improve fitness for purpose, I would…”.
• Allow students to explain evidence orally before writing, use photographs or annotated sketches, or dictate responses using approved digital tools.
• Support students who have incomplete records by helping them reconstruct evidence from their prototype, planning documents, teacher observations, and peer feedback; distinguish clearly between observed evidence and assumptions.
• Extend confident students by asking them to prioritise improvements using impact, feasibility, time, material use, and environmental considerations, and to justify why one improvement should occur before another.