Computer Science
Grade 2
20 min
Collaborative Coding Reflection: What We Learned
Reflect on the collaborative coding experience and share what was learned about teamwork and coding.
Tutorial Preview
1
Introduction & Learning Objectives
Learning Objectives
Name one thing that went well in their team project.
Name one thing they could do better next time.
Explain why sharing ideas is important.
Listen to a partner's reflection.
Use 'I' statements to share their feelings about the project.
Identify a 'bug' and how the team fixed it.
Remember building our amazing coding projects together? 🤔 Let's think about our adventure!
We will talk about our teamwork. We will share what was fun and what was tricky. This helps us become super coders! 🌟
Real-World Applications
Building a big LEGO castle with friends
Playing a team sport like soccer ⚽
Making a group drawing or painting 🎨
Baking cookies with family 🍪
2
Key Concepts & Vocabulary
TermDefinitionExample
Teamwork 🤝Working together with friends to make one thing.You add the code for jumping. Your friend adds the code for running.
Sharing Ideas 💡Telling your ideas to the team so everyone can hear.Saying, 'Let's make the cat character purple!'
Listening Ears 👂Hearing what your friends say and thinking about their ideas.Your friend says, 'Let's add a sound.' You listen and say, 'Great idea!'
Helping Hand 👋Helping a teammate who is stuck on their code.Your friend can't find the 'repeat' block. You point to it on the screen.
Reflection 🤔Thinking back on what you did and what you learned.Saying, 'It was fun when we made the rocket fly!'
Bug Fix 🐞When the team finds a mistake in the code and fixes it toge...
3
Core Syntax & Patterns
Two Stars and a Wish ⭐⭐🌠
Say two things you liked. Say one thing you wish was different.
Use this to share your thoughts. It helps us be kind and helpful.
Think, Pair, Share 🤔➡️🧑🤝🧑➡️🗣️
First, think by yourself. Next, talk with a partner. Then, share with the class.
This helps everyone get a chance to think and talk about the project.
Kind Words Only ❤️
We talk about the code, not the person. We use nice words.
Always be a kind teammate. Say 'we' instead of 'you' when talking about mistakes.
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
A bug makes your character disappear. Your team needs to check the 'hide' block, the 'move' block (in case it went off screen), and the 'size' block (in case it's zero). What is a good way to share the work?
A.Each person checks one different block at the same time and shares what they find
B.Everyone watches one person check all three blocks
C.Argue about which block is definitely the problem before looking
D.Delete all three types of blocks from the code
Challenging
In your project, you learned that you must put the 'say hello' block before the 'jump' block to make the character talk then jump. What is the BIGGER lesson about coding here?
A.The 'jump' block is not very important
B.The order of the code blocks matters a lot
C.'Say hello' blocks always cause problems
D.You should always use 'say hello' before you use 'jump'
Challenging
Team A has one 'Coder' and one 'Idea Person'. Team B has two people who both code and come up with ideas together. After the project, which team is likely to have learned more about ALL parts of making a game?
A.Team A, because everyone has a clear job
B.Team B, because both partners get to try everything
C.Both teams will learn the exact same amount
D.Neither team, because they should have worked alone
Want to practice and check your answers?
Sign up to access all questions with instant feedback, explanations, and progress tracking.
Start Practicing Free