Ancient Egypt | Project Based Learning
Students work in pairs to design a simple interactive coding project about Ancient Egypt. Using block-based coding or unplugged coding cards, they create a mini digital exhibit or paper-based algorithm that teaches one fact about Ancient Egypt through sequence, events, and debugging. The lesson emphasizes project-based collaboration, creativity, and computational thinking.
| Term | Definition |
|---|---|
| Sequence | The order of steps in a program. |
| Event | Something that makes a program do something, such as a click or key press. |
| Debugging | Finding and fixing mistakes in code. |
| Algorithm | A set of steps used to solve a problem or complete a task. |
| Project-based learning | Learning through creating a project that solves a problem or answers a question. |
Show a simple example of an Ancient Egypt coding project or describe the task. Explain that students will create a mini interactive exhibit teaching one Ancient Egypt fact using code.
Listen, ask questions, and choose a partner.
Guide students to select one topic such as pyramids, pharaohs, the Nile, or mummification. Model how to write a sequence of steps on the planning sheet.
Brainstorm ideas, choose a topic, and sketch the steps, characters, or slides for their project.
Circulate, coach students on sequencing, events, and simple debugging. Prompt partners to divide roles such as coder and tester.
Create their interactive exhibit or unplugged algorithm, adding at least one event and one piece of informational text or narration.
Ask students to run their project with a partner and check for clear instructions, correct order, and accurate Ancient Egypt facts.
Test the project, identify problems, and revise code or steps.
Invite a few pairs to briefly demonstrate their project and explain one coding choice and one Ancient Egypt fact.
Present or turn and talk about what they built and what they learned.
End with a quick reflection: students share one coding skill they used and one Ancient Egypt fact they learned. Reinforce that programmers plan, test, and improve just like historians and problem-solvers.