DoAssignment study guide

B2.3 · Reflect on individual and team progress

Learn to reflect on individual and team progress through clear examples and targeted practice.

Ontario Grade 12 Computer Science

Software Development

ICS4U study topic aligned to expectation B2.3

In a computer science project, completing tasks is only part of the work. B2.3 asks you to reflect on individual and team progress: to look carefully at what has happened, recognize what is working or challenging, and decide what to do next. Reflection is not simply saying that a project went well or poorly. It connects observations to evidence and uses them to guide a useful next step. You can apply this in a short classroom activity as well as in a larger group project.

What you will learn

Describe individual progress using specific evidence from the work.
Reflect on team progress by considering both shared results and how members contributed.
Use reflection to identify a realistic next step for yourself or the team.

1. Review what progress means

A useful starting point is the project goal or the work your team agreed to complete. Progress is the difference between what was intended and what has actually been accomplished so far. The review can include completed work, work still in progress, and obstacles that affected the work.

Reflecting on individual progress means considering your own contribution and learning. Ask what you completed, what you learned or improved, and what was difficult. Reflecting on team progress means considering the shared work: what the team has accomplished, how members coordinated, and what is affecting the group’s ability to continue.

ICS3U experience with programming projects can help you recall how tasks and contributions may differ. The aim here is not to judge people’s worth or assign blame. It is to understand progress accurately enough to choose a constructive next step.

Compare the work completed with the intended work.
Consider individual contributions and shared team progress separately.
Describe challenges as part of the work, not as a judgment of a person.

2. Make reflection specific and useful

Begin with an observation: what did you or the team actually do? Add evidence that supports it. Evidence might be a completed feature, a test case the group discussed, a task that remains unfinished, or a meeting decision. Be precise about what the evidence shows; one completed feature does not prove that every part of the project is complete.

Next, interpret the evidence. What does it suggest about progress, learning, or collaboration? Keep the interpretation fair. For example, if a task is unfinished, possible explanations include unclear requirements, an underestimated task, or a dependency on other work. Do not claim to know the cause unless you have a basis for that claim.

Finally, identify a next step. It should respond to what you noticed and be clear enough to act on. An individual might ask for feedback on a particular section. A team might clarify who will complete a remaining task. A useful reflection can also recognize effective practice, such as checking in regularly, and decide to continue it.

A simple structure is observation, interpretation, and next step. It is a guide for thinking, not a formula that guarantees a successful project. A reflection is more useful when it includes both what is going well and what needs attention.

Support observations with concrete evidence.
Separate what you know from what you are guessing.
End with a realistic next step that follows from the reflection.

3. Reflect on individual and team progress together

Individual and team reflection are connected, but they are not interchangeable. A team may have made progress even if one member’s task is still incomplete; another member may have helped with testing or clarified a requirement. Likewise, a person may have learned a great deal while the team still needs to coordinate its remaining work.

When considering your own progress, be specific about your role. Instead of writing “I helped,” describe the contribution and what it enabled. If you encountered a difficulty, explain what you tried or what support would help. Honest reflection is not the same as self-criticism: it can acknowledge a limitation while identifying a way forward.

When considering team progress, pay attention to shared outcomes and collaboration. Ask whether members understand the current status, whether responsibilities are clear, and whether the team has discussed obstacles. A fair reflection recognizes contributions without assuming that every member did the same work.

Share reflections respectfully. Focus on actions, work, and next steps rather than labels about people. If team members see progress differently, compare the evidence and clarify what remains to be done. This keeps reflection focused on improving the work.

A person’s progress and the team’s progress can differ.
Describe contributions and obstacles without assigning unsupported blame.
Use respectful discussion to clarify the team’s shared picture of progress.

4. Turn reflection into a next step

A reflection is not complete merely because it describes the past. Use it to decide what to continue, change, or ask about. A next step can be small: revise one part, seek clarification, review a teammate’s work, or agree on who will take responsibility for a remaining item.

Check that the action follows from the evidence. If the group found that a requirement was misunderstood, a reasonable next step is to clarify it before continuing. If a task is complete but has not been checked, the team might agree to review it. Avoid promising an outcome you cannot know in advance.

During an ongoing project, revisit the reflection after more work has taken place. New evidence may show that the next step helped, or that the team needs a different response. This makes reflection an ongoing way to understand progress, rather than a final rating of the project.

Choose an action that responds to the evidence.
Keep the action clear and achievable.
Revisit progress when there is new information.

Worked example

Reflecting on an individual contribution

A student agreed to create a settings screen for a team program. The screen is drafted, but two choices do not yet save correctly. The student has not asked for feedback. Write a balanced individual reflection and a next step.

State the evidence
The student should name the actual status: the screen is drafted, and two choices do not save correctly. This is more informative than saying only that the task is nearly finished.
Interpret fairly
The reflection can recognize that the draft is progress while noting that saving behavior remains unfinished. It should not assume why the choices fail or imply that the whole task is complete.
Choose a next step
A reasonable action is to ask a teammate to review the saving behavior, then use that feedback to decide what to revise. This addresses the known gap and gives the student a clear action.

Answer: I drafted the settings screen, but two choices do not yet save correctly. I have not asked for feedback, so I do not know whether the issue is in my approach or in how the choices are connected to the rest of the program. My next step is to ask a teammate to review those two choices and then revise the screen based on what we find.

Check: The reflection names completed work, an unfinished part, a limit in what the student knows, and a next step that responds to the evidence.

Worked example

Reflecting on team coordination

A team has completed a draft of its program’s main screen. At a check-in, members realize they have different ideas about what the screen should show. Write a team reflection and a next step.

Recognize progress
The team has a draft of the main screen, so it can acknowledge that shared work is complete to this point.
Name the challenge
Members have different ideas about the screen’s contents. The reflection should describe this difference without blaming a particular member.
Agree on a response
The team can compare the ideas with the project’s intended purpose and agree on what the screen should include before continuing. This directly addresses the lack of a shared understanding.

Answer: We completed a draft of the main screen, but our check-in showed that we do not share the same understanding of what it should show. We should compare our ideas with the project’s intended purpose and agree on the screen’s contents before adding more details. Then we can update the draft to reflect that decision.

Check: The reflection includes a team accomplishment, a specific coordination challenge, and a next action that helps members share an understanding.

Worked example

Reflecting when progress is uneven

A team has completed and reviewed one feature, while another agreed feature is not started. One member says the team is doing well because the reviewed feature works; another is concerned that work is behind what the team intended. Prepare a fair reflection.

Include both observations
The team should recognize that one feature is complete and reviewed while another agreed feature has not started. Both observations matter to an accurate picture of progress.
Avoid an unsupported conclusion
The completed feature is evidence of progress, but it does not show that all intended work is complete. The team can acknowledge the concern without claiming a specific cause for the unfinished feature.
Identify a constructive next step
The team can clarify what remains for the unstarted feature and agree who will take the next action. This makes the status easier to review later without pretending the feature is already underway.

Answer: We completed and reviewed one feature, which is a clear achievement. The other agreed feature has not started, so we have not completed all the work we intended to do. We should clarify what remains for that feature and agree who will take the next action. We can then review progress using the new information.

Check: The reflection balances achievement with unfinished work and proposes a next step without inventing a reason for the delay.

Common mistakes and how to avoid them

Writing “Everything went well” or “The project was bad” without examples.

Correction: Name a specific result or challenge and explain what it suggests about progress.

Treating an unfinished task as proof that a team member did not contribute.

Correction: Describe the task’s status and discuss what is known. Contributions and causes should not be assumed.

Listing difficulties without deciding what to do next.

Correction: Choose a realistic action that responds to the difficulty or seek clarification about what is needed.

Making the individual reflection and team reflection identical.

Correction: Consider your own work and learning separately from the team’s shared results and coordination.

Lesson summary

Reflection means reviewing actual progress, interpreting evidence, and deciding on a useful next step.
Individual reflection considers your contribution and learning; team reflection considers shared work and collaboration.
Be specific, fair, and respectful. Separate observations from guesses.
Use reflection to decide what to continue, change, clarify, or review.

Check your understanding

Question 1

A student writes, “I made progress because I finished the menu draft, but I still need feedback on whether it matches the team’s plan.” What makes this reflection useful?

It includes evidence of completed work and identifies a specific next need.
It proves that the entire program is complete.
It identifies a teammate as responsible for the remaining work.
It avoids mentioning any unfinished work.

Show answer and explanation

It includes evidence of completed work and identifies a specific next need.

The student names a concrete contribution and a remaining question. The statement does not claim that the whole program is complete or assign blame.

Question 2

A team has completed one feature, but another agreed feature is not started. Which reflection is most balanced?

The team is finished because one feature works.
The team made progress on one feature, and another agreed feature remains; the team should clarify its next action.
The team made no progress at all.
One member must be responsible for the unfinished feature.

Show answer and explanation

The team made progress on one feature, and another agreed feature remains; the team should clarify its next action.

This response recognizes both the completed work and the unfinished work, then proposes a constructive action without guessing why the task remains.

Question 3

Which next step best responds to a team discovering that members understand a screen’s purpose differently?

Continue building separate versions without discussing the difference.
Decide that the first idea mentioned must be correct.
Discuss the intended purpose and agree on what the screen should show before continuing.
Record that the project has failed and stop reviewing progress.

Show answer and explanation

Discuss the intended purpose and agree on what the screen should show before continuing.

The team’s evidence is that members do not share an understanding. Agreeing on the intended contents addresses that coordination challenge.

Key terms

Individual progress: What a person has contributed, learned, or still needs to work on.
Team progress: The shared work completed so far and how the team is coordinating its work.
Evidence: A specific observation or result that supports a statement about progress.
Reflection: A considered review of progress that uses observations to guide a next step.

Continue through ICS4U

View the complete ICS4U Ontario Grade 12 Computer Science curriculum and lessons

About this lesson and its review

Published by DoAssignment. This reviewed lesson follows Ontario Grade 12 Computer Science (ICS4U), expectation B2.3. It is a study resource, not an official curriculum publication.

Before publication, content is checked for structure, mathematical or chemical notation, calculations, course boundaries, and readability. Errors can still occur, so corrections are welcomed.

Official curriculum reference

Report a correction or ask a question