Version Control and Team Tools
Intro to Python Programming Grades 9–12 3-day lesson 26 deliverables Show students how saving Python versions with clear notes helps a team recover from mistakes. Students compare changes in a ferry fare app, improve vague notes and find the version that caused a failure. They save and compare their own changes, restore working code and choose team tools for different jobs.
● Instant download · Lifetime access · Editable & print-ready
Print + digitalPDF, PowerPoint, Word & Google
Answer keysA key for every page
Built-in assessmentExit tickets + lesson quiz
45-minute daysEvery day planned and timed
A short coding level practices this lesson in CodeGrove, our code lab that runs in the browser. Students write the program, run it and check it, with no account and nothing to install. Use it with the lesson or as practice later.
Open the levelWhat does this lesson cover?
Students can lose working code when they change a program without recording what changed. This lesson gives them practice comparing saved versions and using clear notes to choose what to restore.
The lab on Day 2 has an online version that uses CodeGrove, our in-browser code lab, in the Version Steps level. It practices saving three versions of a ferry fare app with change notes in History, comparing them with Show changes and restoring the version that works. Every online version comes with a paper version, so no internet is needed. CodeGrove is free, with no accounts or sign-ins.
Version Steps
Students add a bike fee to the ferry fare app, write a note for each of three versions, find the version that stops on Saturday and pick the version to restore.
Everything that's included
00 Start Here
- READ FIRST: every file in the lesson and when you use it
- Teacher Guide and Pacing: the plan for each day, what to print and how to grade
- Skills map: which standards each day teaches
01 Present
- One editable PowerPoint deck for all three days, 28 slides, with speaker notes
- Slide script: the speaker notes, printed
- Bell ringers: a short warm-up for each day
02 Student Handouts
- Guided notes: one packet for all three days, in PDF and editable Word. Students fill in the blanks during the slides, with the word bank on the page
- Vocab slip: the lesson's words and what they mean, on one page
03 Labs
- Version Steps: students add a bike fee to the ferry fare app, write a note for each of three versions, find the version that stops on Saturday and pick the version to restore
04 Activities
- Version Timeline: students mark the change on four version cards of a ferry fare app, write a clearer note for each, find the version that broke the app and pick a team tool for four jobs
- Bake Sale Versions: students write a change note for three versions of a bake sale app, pick the version to restore and pick team tools
05 Assessment
- Exit tickets: quick questions that show who needs more help
- Lesson quiz: 10 multiple-choice questions and 2 written answers about all three days
06 Answer Keys
- 5 answer key files: a key for each day (its bell ringer, notes and exit ticket) and the activity and lab keys, plus the quiz key
Digital: Google Forms™ + Google Slides™
- 4 Google Forms™ of the exit tickets and the quiz, ready to copy into your Drive
- The multiple choice grades itself, and you grade the written answers
- A Google Slides™ copy of the deck, with the same slides and speaker notes, for Google Classroom™
- Give a Form that asks students to read code only on school-managed Chromebooks in locked mode, and use the paper version on other devices
Online: CodeGrove
- CodeGrove, Version Steps level: the online version of the lab on Day 2
- Every online version has a paper version, so no internet is needed
- Free to use, with no accounts or sign-ins
Why teachers love this lesson
Change notes must explain the changeStudents replace vague version notes with clear accounts of what changed. A teammate can use those notes to follow the code's history.
Students practice recovering from a mistakeThey compare fare app versions, identify the broken change and select the working version to restore.
Print and digitalEvery page is a print-ready PDF, and the Google Forms™ and Google Slides™ let you teach the same lesson in Google Classroom™.
Real online activitiesStudents can use CodeGrove, our in-browser code lab, on a computer or tablet, and every online version has a paper version that works with no internet.
A key for every pageEvery day has its own answer key, and every written question has a sample answer and what to look for.
Every day fits a 45-minute classEach day's plan is timed activity by activity against real reading and writing speeds.
What Teachers Say
Be the first to review this
Reviews help me a lot, and they help other teachers pick the right resources for their classes. It takes about a minute.
Leave a reviewQuestions teachers ask
How do I get the files after I buy?
Instant download right after checkout: PowerPoint and Word files you can edit, print-ready PDFs, and links that copy the Google Forms™ and Google Slides™ into your Drive.
Can I buy the whole unit or course instead?
Yes. This lesson is part of the Unit 7 bundle and the complete Intro to Python Programming course. Both cost less than buying the lessons one at a time.
Is this AP Computer Science?
No. It is a full-year, non-AP intro to Python course for grades 9 to 12. For AP, see our AP Computer Science A and AP CSP courses.
What should students know before this lesson?
Students know print() and variables.
What formats are the files in?
Every page is a print-ready PDF. The slides are an editable PowerPoint and the guided notes an editable Word file. The exit tickets and the quiz also come as Google Forms™, and the deck as Google Slides™.
Which standards does it cover?
Written for Florida's Foundations of Programming course (9007210). The skills map in the lesson shows which standards each day teaches.