Final Project Presentations

Overview

This is lesson 29 of 30 in the Infrastructure Skills Development unit. Students present their completed technological projects, explain the development and management decisions they made, and respond to constructive feedback. The lesson consolidates evidence for their technological practice and prepares students for the final review lesson.

Learning intentions

Students will:

• communicate the purpose, development and final features of their technological outcome
• explain how planning, testing, feedback and resource management influenced the project
• evaluate the outcome’s fitness for purpose in its intended physical and social environment
• give specific, respectful feedback and respond appropriately to questions

Success criteria

• I can clearly explain the issue, need or opportunity my project addresses.
• I can use evidence to explain how my outcome meets its specifications and functions in its intended environment.
• I can describe important changes made during development and justify my decisions.
• I can give useful feedback that refers to the project’s function, design and development process.

Curriculum links

• Undertake brief development to address an issue: communicate the final brief, specifications, stakeholders and reasons for developing the outcome.
• Select and use planning tools to manage the development of an outcome: explain how planning tools, goals, resources and review points were used and adjusted.
• Demonstrate understanding of the nature of technological outcomes: discuss physical and functional attributes and fitness for purpose in the intended environment.
• Undertake effective development to make and trial a prototype: use testing and stakeholder feedback to explain decisions to accept, modify or refine the outcome.

Lesson structure (120 minutes)

1. 0–10 min · Set expectations and prepare. Teacher opens the presentation expectations and assessment slides, outlines the running order, audience responsibilities and success criteria, then checks that each group has its outcome, evidence and presentation ready. Students sit with their project team, complete a final equipment check and review the presentation requirements:

• identify the issue, need or opportunity
• describe the intended user and environment
• explain the outcome and key specifications
• show planning and development evidence
• explain testing, feedback and changes
• evaluate fitness for purpose and identify next steps.

2. 10–20 min · Rehearse and peer-check. Teacher distributes the presentation feedback and evidence record and models a strong, specific feedback comment using the prompts on the presentation expectations and assessment slides. Students rehearse their presentation in teams, check timing, allocate speaking roles and use the worksheet prompts to identify one claim that needs supporting evidence.

3. 20–62 min · Presentations: round one. Teacher facilitates the first presentation block, keeping each team to approximately seven minutes: five minutes presenting, followed by two minutes for questions and feedback. Students present their projects and listen actively, recording one strength, one evidence-based question and one suggestion for each presenting team on the worksheet.

4. 62–67 min · Movement and reset. Teacher pauses for a short break, confirms the remaining order and reminds students that feedback must focus on the outcome and development decisions, not the presenter. Students reset displays, check any practical demonstration areas and prepare questions for the next block.

5. 67–109 min · Presentations: round two. Teacher facilitates the remaining presentations using the same seven-minute structure, prompting presenters to connect claims to specifications, testing results, stakeholder feedback or planning records. Students complete their feedback records and ask questions that explore function, design priorities, resources, sustainability, safety or suitability for the intended environment.

6. 109–116 min · Whole-class synthesis. Teacher uses the discussion and reflection slides to lead a discussion: “Which development decisions most improved an outcome?” and “What evidence made a presentation convincing?” Students share patterns noticed across projects and compare how different teams managed time, materials, tools, information and feedback.

7. 116–120 min · Individual exit reflection. Teacher directs students to complete the final section of the presentation feedback and evidence record before collecting it. Students write: one presentation decision they would adopt, one improvement they would make to their own outcome or process, and one piece of evidence demonstrating fitness for purpose. Teacher previews lesson 30 as the final review and completion of project documentation.

Resources

• the presentation expectations and assessment slides
• the presentation feedback and evidence record
• Completed student projects, prototypes or digital outcomes
• Student planning tools, design briefs, specifications and testing evidence
• Presentation devices, projector, speakers and adaptors
• Timer and presentation running order
• Display tables, boards or practical demonstration equipment
• Camera or school-approved documentation device

Assessment

• Formatively assess presentations for clear communication of the issue, brief, specifications, development decisions, testing and fitness for purpose.
• Use questioning to check whether students can connect physical and functional attributes to the intended social and physical environment.
• Review the feedback records and exit reflections for evidence of evaluation, justified decision-making and understanding of how planning and stakeholder feedback influenced development.

Differentiation

• Provide the presentation structure, success criteria and question prompts in advance; allow students to use cue cards, annotated visuals or a recorded section where appropriate.
• Support students who need it with sentence starters such as “Our outcome is fit for purpose because…”, “Testing showed…”, and “We changed… in response to…”.
• Permit flexible speaking roles, shared presentation, assistive technology and additional processing time for students with learning, communication or anxiety needs.
• Challenge confident presenters to compare their outcome with an alternative approach, justify which design elements were prioritised, and discuss how resources could be used more efficiently.
• For EAL learners, pre-teach key terms such as specification, stakeholder, prototype, tolerance, function, attribute, feedback and fitness for purpose; accept labelled diagrams and demonstrations alongside spoken explanation.