Home›Lesson Plans›Computer Science›Program Development · Grade 5

Planning a Program

Fifth graders learn that good coders plan before they type, from understanding the goal and breaking it down to planning the steps, then building and testing, and put the steps in order.

Grade 5Planning a Program50 minutes1 class periodCSTA / ISTEExplicit teaching4 StandardsCSTA
Start the Lesson
Assign or share this lesson
Share to Google Classroom Share to Microsoft Teams

Copy link works with Canvas, Schoology, Moodle and any other LMS — paste it in as a resource or assignment.

Lesson at a Glance

Everything you need before the bell rings

Learning Objectives

Students will be able to…

  • ✓Understand the goal.
  • ✓Break it into steps.
  • ✓Plan before coding.
  • ✓Order the steps.
Essential Question

Good code starts on paper, not the keyboard. What are the steps of planning a program, and why does planning first make building easier?

0
Lesson Phases
0
Vocabulary Terms
0
Standards Aligned
0
Interactive Task
Put in Order · Interactive

Order the Steps

Project this and put the steps of planning a program in order — tap each step from understanding the goal to testing.

🗺️ Put the steps of planning a program in orderTry it
Tap the steps in order, starting with understanding the goal.
The Lesson · Use → Modify → Create (a coding progression with Unplugged practice)

50 minutes, five moves

Tap any phase to open the teacher moves and student actions.

1

Hook — Plan First

5 min

It is tempting to start typing code right away. Why do good programmers plan on paper before they touch the keyboard?

👩‍🏫 Teacher Moves

  • Show a messy jump-in.
  • Ask what's missing.
  • Set the goal.

🎒 Student Actions

  • Think.
  • Share.
  • Get ready.
2

Use — Order the Steps

12 min

Students put the planning steps in order.

👩‍🏫 Teacher Moves

  • Send students to Order the Steps.
  • Order the steps.
  • Name each one.

🎒 Student Actions

  • Order.
  • Say.
  • Note it.
3

Modify — Plan a Mini-Project

13 min

Students plan a small program.

👩‍🏫 Teacher Moves

  • Pick a tiny project.
  • Break it into steps.
  • Write the steps down.

🎒 Student Actions

  • Pick.
  • Break.
  • Write.
4

Create — My Plan

15 min

Students make a full plan.

👩‍🏫 Teacher Moves

  • Name your goal.
  • List the steps in order.
  • Note how you will test it.

🎒 Student Actions

  • Name.
  • List.
  • Note.
5

Reflect — Measure Twice

5 min

Students reflect on planning.

👩‍🏫 Teacher Moves

  • Why plan before coding?
  • Why test at the end?
  • Complete the exit ticket.

🎒 Student Actions

  • Say it.
  • Say it.
  • Complete the exit ticket.
Standards Alignment

Built to the standards you report on

Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.

CSTA
1B-AP-11

Decompose a problem into smaller parts.

CSTA
1B-AP-15

Plan and test programs before and after coding.

CSTA
1B-AP-08

Create a plan that describes a program's steps.

ISTE
5c

Break a problem into steps to plan a solution.

Differentiation

One lesson, every learner

Multilingual Learners

ELL / EMERGING READERS
  • Step picture cards.
  • Sentence frame: “First I ___ , then I ___ .”
  • Order two steps at a time.

Support & Access

IEP / 504
  • Start with 'understand the goal'.
  • Plan one tiny program together.
  • Add one step at a time.

Stretch & Extend

GIFTED / EARLY FINISHERS
  • Plan a multi-part project.
  • Write pseudocode for each step.
  • Explain the plan to a partner.
Materials

What to gather

  • 📽️Projector / board
  • 🖼️Planning-step cards
  • 💻Order the Steps
  • 📝Planning sheets
  • ✏️Pencils
  • 🎫Exit-ticket slips
Vocabulary

Key terms — hover for a quick definition

plana description of what a program will do and howgoalwhat you want the program to accomplishdecomposeto break a problem into smaller partspseudocodeplain-language steps that describe codealgorithma step-by-step set of instructionstestto check that a program works as planneddebugto find and fix mistakes in codesequencethe order steps happen in
Evaluate

Exit Ticket

Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.

QUESTION 1
What is the first step in planning a program?
Understand the goal, so you know exactly what the program should do before you plan or code.
QUESTION 2
Why plan before you start coding?
Planning helps you break the problem into steps and catch mistakes early, so coding goes more smoothly.
QUESTION 3
Why test your program at the end?
To make sure it actually works as planned and to find anything that needs fixing.

Create: my plan.

Have students name a small program goal, break it into steps written in order, and note how they will test it, so planning becomes a habit before coding. A printable program-planning worksheet is in the Computer Science library.

Study · Flashcards

Study the key terms

Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.

🃏 Planning a ProgramFlip
Card 1
Term
Tap to flip →
Meaning
0

Nice work!

Practice · Quiz

Check your understanding

A quick self-check with instant feedback, drawn from this lesson’s key terms.

📝 Planning a ProgramQuiz
Score: 0
1 / 6
Question 1
0%

Nice work!

Practice · Worksheet

Printable worksheet

A print-and-go review sheet with a built-in answer key. Tap “Show answer key” to reveal answers, or print the clean version for students.

🖨️ Planning a ProgramPrint
Name: ________________________
Date: ____________

Part A · Write the word that matches each meaning

Word bank: algorithm, debug, decompose, goal, plan, pseudocode, sequence, test
  1. plain-language steps that describe code
  2. a step-by-step set of instructions
  3. to find and fix mistakes in code
  4. the order steps happen in
  5. to break a problem into smaller parts
  6. to check that a program works as planned
  7. a description of what a program will do and how
  8. what you want the program to accomplish

Part B · Show what you learned

  1. What is the first step in planning a program?
  2. Why plan before you start coding?
  3. Why test your program at the end?
Answer key — Part A: 1) pseudocode · 2) algorithm · 3) debug · 4) sequence · 5) decompose · 6) test · 7) plan · 8) goal
Part B: 1) Understand the goal, so you know exactly what the program should do before you plan or code. 2) Planning helps you break the problem into steps and catch mistakes early, so coding goes more smoothly. 3) To make sure it actually works as planned and to find anything that needs fixing.