Collaboration Practice Test

Students collaborate on a game design project about exploring an underwater city. Talia programs movement and collision, Bruno creates art assets and animations, and Keisha writes dialogue and mission objectives. They communicate through a shared folder for assets, a weekly planning call, and short messages when something blocks progress. During integration, Talia says the new animation file breaks the game’s loading screen.

"The file name doesn’t match what the game expects," Talia explains.

Bruno responds, "I renamed it to stay organized, but I didn’t realize it was referenced elsewhere."

Keisha suggests, "Let’s document naming rules so this doesn’t repeat."

They agree to restore the expected name, add a simple naming guide in their shared notes, and confirm the fix together. The game runs smoothly at the next playtest, and the team earns praise for cohesion.

In the described project, how did the team resolve the conflict over the renamed animation file?

A student, Eleni, joins an online open-source community improving a beginner-friendly coding tutorial site. The community divides work through an issue board, reviews changes publicly, and uses a forum for longer discussions. Eleni picks a task: rewrite an unclear lesson so novices understand it without feeling overwhelmed. She collaborates with Drew, who edits for clarity, and Sora, who checks that examples match the lesson’s goals. Eleni posts, “I’m simplifying the wording and adding a short practice question—please critique the tone.” Drew replies, “This reads smoother, but one paragraph still assumes prior knowledge.” Sora adds, “The example should be shorter and consistent with earlier lessons.” When Eleni feels frustrated, she writes, “I thought I already fixed that,” and the thread grows tense. A moderator steps in: “Let’s be precise and kind—quote the exact sentence, propose a revision, and explain why.” Following that structure, Eleni revises the paragraph, Sora adjusts the example, and Drew confirms the final text is approachable. The community merges the update, and new users comment that the lesson finally “clicks.” In the described project, how did the team resolve the tense disagreement during the review process?