Welcome to marcellogoccia.com

Chapter purpose

Using the standards as a professional framework

The Teacher Standards provide a useful framework for reflecting on the kind of teacher I aim to be. Although some evidence in this portfolio was developed during my professional training, this chapter is not intended as a formal assessment record. Instead, it shows how the standards continue to inform my identity, decisions and growth as a teacher.

I have not added a new set of lesson evidence here because the purpose of this final chapter is to bring the portfolio together. The links below point back to the evidence already presented in earlier chapters, showing how individual artefacts connect to broader areas of professional practice.

Teacher Standards overview

How the evidence links to the Teacher Standards

This standards map is designed as a signpost rather than a repeated evidence bank. Each row summarises what the standard shows in my teaching and links back to selected evidence already included in the portfolio.

TS1 High expectations	What it shows: I set challenging learning goals and encourage students to explain, justify and improve their answers rather than only complete tasks. Evidence links: Evidence 7.5 — FRQ Deconstruction Lesson Plan Evidence 7.3 — Peer Review Activity
TS2 Student progress	What it shows: I use evidence of learning to understand how students are progressing and what they need next. Evidence links: Evidence 7.1 — Exit Ticket: FRQ Reasoning · Evidence 7.2 — Independent FRQ Task · Evidence 3.5 — Exit Ticket Answers
TS3 Subject and curriculum knowledge	What it shows: I use secure Computer Science knowledge to explain abstract ideas clearly and connect technical concepts to examples, models and applications. Evidence links: Evidence 4.1 — Crowdsourcing Lesson Plan · Evidence 5.1 — Python Quiz Lesson Plan · Evidence 3.1 — Network Topologies Lesson Plan
TS4 Planning and teaching	What it shows: I plan learning as a sequence, moving students from prior knowledge to modelling, guided practice, formative checks and independent application. Evidence links: Evidence 2.1 — Boolean Logic Lesson Plan · Evidence 4.1 — Crowdsourcing Learning Sequence · Evidence 7.5 — FRQ Deconstruction Lesson Plan
TS5 Adaptive teaching	What it shows: I use scaffolds, modelling, vocabulary support, pair work, challenge tasks and structured exit tickets to support different starting points while maintaining challenge. Evidence links: Evidence 5.1 — Adaptive Teaching in Python Programming · Evidence 5.4 — Adaptive Exit Ticket Answers
TS6 Assessment	What it shows: I use formative assessment to make student thinking visible and to inform next teaching decisions. Evidence links: Evidence 7.1 — Exit Ticket: Lists and Program Behaviour · Evidence 7.3 — Peer Review Activity · Evidence 5.4 — Adaptive Exit Ticket Answers
TS7 Behaviour and routines	What it shows: I use routines, expectations, circulation, positive reinforcement and clear task structures to support a focused learning environment. Evidence links: Evidence 6.1 — IGCSE Algorithms Observation · Evidence 6.2 — IGCSE Data Compression Observation · Evidence 5.3 — Programming Observation Feedback
TS8 Wider professional responsibilities	What it shows: I learn from feedback, professional dialogue and observations of colleagues, then adapt those insights to my own Computer Science classroom. Evidence links: Evidence 6.4 — Observing a Colleague Outside Computer Science · Evidence 6.5 — Observing a Computer Science Colleague · Evidence 1.2 — Educational Philosophy

Professional growth

What this shows about my development

Looking across the portfolio, I can see several clear areas of growth in my teaching. I have become more deliberate in planning lessons around prior knowledge, misconceptions and progression. I have also developed a stronger understanding of how formative assessment can reveal student thinking during the lesson, rather than only checking learning at the end.

A second area of growth is my use of modelling and scaffolding. In Computer Science, students often need to understand abstract concepts, precise syntax and technical vocabulary at the same time. I have learned to use worked examples, visual models, sentence frames, peer discussion and guided questioning to make challenging learning more accessible without reducing expectations.

A third area of growth is reflection. Feedback from observations, student responses, exit tickets and colleague observations has helped me make more informed teaching decisions. I now think more carefully about how to move students from participation to precise explanation, and from completing tasks to understanding the concepts behind them.

Future professional targets

Continuing the cycle of improvement

Target 1 — Strengthen written explanations. Many students can discuss Computer Science ideas verbally, but still need support to express technical reasoning clearly in writing. I will continue using model answers, sentence frames, keyword banks and peer review to help students produce more precise explanations.

Target 2 — Make individual understanding more visible during collaborative work. Pair and group tasks are valuable, but I want to ensure that every student is accountable for their own thinking. I will use short individual checkpoints, mini-whiteboards, exit tickets and targeted questioning during active learning tasks.