Portfolio

Teaching portfolio

Chapters
Portfolio home Return to the main teaching page

Teaching Portfolio · Chapter 3

Becoming a Reflective Teacher

This chapter shows how I use lesson evidence, student responses and professional feedback to reflect on my teaching and refine the way I support students' understanding.

View evidence Read chapter purpose

Chapter purpose

Using evidence to improve my teaching

In this chapter, I focus on reflective practice. The evidence comes from an AS Computer Science lesson on network topologies, where students explored bus, star, mesh and hybrid networks through recall, diagrams, physical modelling, disaster-card scenarios, client scenario tasks and an exit ticket.

The lesson helped me see the value of active learning for making an abstract concept concrete. It also helped me identify a clear next step: students could often discuss topology choices orally, but needed more structured support to turn that reasoning into precise written explanations using Computer Science terminology.

Reflection cycle

From active learning to precise explanation

The lesson was designed to move students from prior knowledge of networks, packets and routers towards AS-level understanding of how devices are arranged and connected. Students first recalled prior knowledge, then explored topology diagrams, built physical models with string and role cards, tested failure scenarios, and finally applied their understanding to client-based situations.

This created a useful reflective sequence: planning made the abstract concept visible, classroom feedback confirmed that students were engaged and thinking, and student work showed that the next step was to strengthen written explanations through model answers, keyword banks, sentence frames and individual checkpoints.

Evidence in this chapter

Planning, feedback, classroom artefacts and student responses

I have included the main evidence items because together they tell a complete reflective story: the planned learning journey, the observed lesson, the active-learning resources, the collaborative written responses and the individual exit-ticket evidence.

Evidence 3.1

Annotated Network Topologies Lesson Plan

The planned learning sequence, including recall, modelling, disaster scenarios, client tasks and exit ticket.

 Evidence 3.2

Observation / HoD Feedback Extract

External feedback on active learning, questioning, student engagement and areas for development.

 Evidence 3.3

Scenario and Disaster Cards

Classroom artefacts used to reveal reasoning about reliability, failure points, expansion and suitability.

 Evidence 3.4

Collaborative Student Answers

Group written responses showing how students applied topology knowledge to realistic scenarios.

 Evidence 3.5

Exit Ticket Answers

Individual evidence used to check understanding and decide next steps for written explanation.

Evidence 3.1

Annotated Network Topologies Lesson Plan

An annotated AS Computer Science lesson plan showing how I planned active learning and reflection around network topology.

Evidence extract

This lesson was planned to make network topology more concrete. Students built on prior IGCSE knowledge of packets, destination addresses and routers, then moved towards AS-level understanding of how devices are arranged and connected in bus, star, mesh and hybrid topologies.

The planned sequence used mini-whiteboard recall, diagrams, physical modelling with string and role cards, disaster-card reasoning, client scenario tasks and an exit ticket. This helped students move from recognising topology shapes to analysing reliability, failure, expansion, cost and suitability.

This evidence is important because it shows reflective planning: I anticipated misconceptions, planned scaffolds for technical vocabulary, and used the lesson evaluation to identify a next step around model answers, keyword banks and individual checkpoints.

View evidence document

Network topologies lesson plan

The original evidence document is shown below in a compact preview. The reader can scroll inside the PDF or open it in a new tab.

Open in new tab
Reflective planning Active learning Physical modelling Questioning Technical vocabulary Exit ticket

Evidence 3.2

Observation / HoD Feedback Extract

Observation feedback showing how the planned active learning sequence was visible in classroom practice.

Evidence extract

The observation feedback highlighted that students were engaged during the warm-up activity and that the lesson material was clear and vivid. It also noted that students were highly engaged in the physical activity used to build a network topology and understand how data moves within it.

The feedback confirmed that students analysed what happens when a network fails, used response cards, and applied their knowledge through scenario tasks. This supports the reflective point that active learning helped students move beyond naming topologies towards reasoning about reliability, application and failure.

The feedback also helped me identify next steps: I needed to strengthen written explanation, make group roles and spaces even clearer, and check individual understanding after collaborative tasks.

View evidence document

Observation feedback

The original observation feedback is shown below in a compact preview. The reader can scroll inside the PDF or open it in a new tab.

Open in new tab
Professional feedback Student engagement Clear sequencing Questioning Collaboration Next steps

Evidence 3.3

Scenario and Disaster Cards

Classroom artefacts used to make network topology reasoning more active, concrete and scenario-based.

Evidence extract

The scenario cards asked students to choose a suitable topology for realistic situations, including a computer lab, a hospital system, a temporary classroom and an existing wired LAN that needed a new wireless LAN. This pushed students to consider suitability rather than simply memorising definitions.

The disaster cards created reasoning moments during the physical modelling task. Students had to decide what would happen if one computer failed, a cable failed, the central switch failed, the budget was limited, or the network gained many more users.

This evidence matters for Chapter 3 because it shows the design of an activity that revealed understanding. The cards helped me observe students' reasoning and later reflect on how to support more precise written explanations.

View evidence document

Scenario and disaster cards

The original evidence document is shown below in a compact preview. The reader can scroll inside the PDF or open it in a new tab.

Open in new tab
Active learning Scenario tasks Reasoning Reliability Failure points Application

Evidence 3.4

Collaborative Student Answers

Group answer cards showing how students applied topology knowledge and where written reasoning needed further support.

Evidence extract

The collaborative answer cards show students choosing topologies such as star, mesh, bus and hybrid, then identifying advantages and disadvantages. The responses show that students were able to connect topology choices to ideas such as cost, reliability, expansion and failure.

At the same time, this evidence helped me notice that some written explanations remained general or incomplete. Some students could identify a suitable topology, but needed clearer models for explaining why it was suitable using accurate Computer Science vocabulary.

This evidence is therefore useful not only because it shows student work, but because it directly shaped my reflection: active group learning was effective, but it needed to be followed by more explicit language support and individual checks.

View evidence document

Collaborative student answers

The original anonymised student-work evidence is shown below in a compact preview. The reader can scroll inside the PDF or open it in a new tab.

Open in new tab
Student work Collaborative learning Written explanation Vocabulary support Feedback-informed planning

Evidence 3.5

Exit Ticket Answers

Individual exit-ticket responses used to check understanding and inform the next teaching decision.

Evidence extract

The exit ticket gave individual evidence after the collaborative activities. The first question showed that students could identify the definition of network topology as the way devices in a network are connected.

The written question asked students to choose a topology for a school computer lab and give a short reason. The responses showed that many students could choose a suitable topology such as star, but their justifications varied in precision.

This evidence helped me decide a specific next step: I should use a model answer, a keyword bank and a short individual checkpoint so that students can move from correct choices to clearer technical explanations.

View evidence document

Exit ticket answers

The original exit-ticket evidence is shown below in a compact preview. The reader can scroll inside the PDF or open it in a new tab.

Open in new tab
Exit ticket Individual understanding Formative assessment Written reasoning Responsive next steps

Chapter reflection

What this evidence shows about my reflective practice

Looking across the evidence, I can see that active learning helped students understand an abstract topic more clearly. Physical modelling, disaster cards and client scenarios made network topology visible and gave students opportunities to reason about reliability, expansion, cost and failure points.

The evidence also shows why reflection needs student work and feedback, not only my own impression of the lesson. The observation feedback confirmed strengths in engagement, sequencing and modelling, while the collaborative answers and exit tickets helped me see that written explanations needed more precise language support.

My next step is to make the bridge from discussion to writing more explicit. In future lessons, I would provide a model answer before the scenario task, use a visible keyword bank, assign group roles more clearly, and add a short individual checkpoint after collaborative work so that I can see each student's understanding before the plenary.