Computer Science
Grade 3
20 min
Project Planning
Project Planning
Tutorial Preview
1
Introduction & Learning Objectives
Learning Objectives
Define what a project plan is and why it's important for teamwork.
Identify the key parts of a simple project plan: Goal, Tasks, and Roles.
Explain how collaboration helps make a computer science project better.
Create a simple, step-by-step plan for a small coding project with a partner.
Use 'if/then' thinking to plan for events in a project, like a button click.
Give and receive helpful ideas (feedback) to a teammate about a project.
Follow a shared plan to complete a task with a group.
Have you ever tried to build a giant LEGO castle with a friend? 🏰 What happens if you both start building without a plan?
Today, we'll learn how to make a 'project plan,' which is like a recipe or a map for building cool things on the co...
2
Key Concepts & Vocabulary
TermDefinitionExample
Project PlanA list of steps and ideas that tells a team how to make something. It's like a recipe for your project!For a game about a jumping frog, the plan might say: 1. Draw the frog. 2. Code the 'jump' button. 3. Add a background.
CollaborationWorking together with others on a team to share ideas and get things done.You draw the character on the computer, and your friend codes its movements.
GoalThe big idea you want to achieve. It's what your project will be when it's all finished.Our goal is to make a game where a rocket flies to the moon.
TaskA small job or step in your project plan that needs to be done.A task could be 'Choose a color for the spaceship' or 'Record a 'blast off' sound.'
RoleThe special job...
3
Core Syntax & Patterns
The 'First, Then, Next' Plan
List your tasks in the order they need to happen.
Use this to make sure you don't try to make a character move before you've even drawn it! Always think about what needs to be done first to avoid problems.
The 'Who Does What?' Chart
[Task Name] -> [Team Member's Name]
Make a simple chart or list to give everyone a special job (a role). This makes sure all the work gets done and no one is left out.
The 'If/Then' Check-in
IF [we finish a task], THEN [we show our team].
This is a rule for teamwork. After you finish your part, check in with your group to make sure it works with their parts. This helps find problems early!
4 more steps in this tutorial
Sign up free to access the complete tutorial with worked examples and practice.
Sign Up Free to ContinueSample Practice Questions
Challenging
Your team is making a game with many different, unique monsters. The plan is to have each of the four team members design and code one monster. What is the main advantage of this plan?
A.The game will be finished in one day
B.All the monsters will look and act exactly the same
C.It makes sure only one person is the boss
D.It allows for more creative and different kinds of monsters in the game
Challenging
Your team's plan is: 1. Code the player to jump. 2. Add platforms. 3. Test if the player can land on the platforms. You test it and the player falls right through the platforms. What part of your plan was most likely missing a step?
A.The plan to test the game
B.The plan to add platforms
C.The plan to make the player jump
D.step about making the platforms solid so the player can't pass through them
Challenging
A team is making a virtual pet. The plan has two parts: Part 1 is to draw the pet. Part 2 is to code the feeding button. The team decides to do both parts at the same time. What problem might they have?
A.The coder might finish before the art is ready to be put into the game
B.The artist might use the wrong colors
C.The computer might run out of battery
D.The feeding button will be too small
Want to practice and check your answers?
Sign up to access all questions with instant feedback, explanations, and progress tracking.
Start Practicing Free