An agile team of eight has just formed to build a customer portal. Two members already disagree loudly over whether to review each other's code before merging, and the sponsor is pressing for early velocity. The project manager wants to prevent these clashes from recurring. What is the BEST way to establish how the team will work together?
- AWrite a set of working agreements yourself based on best practice and circulate them for the team to follow.
- BAsk the sponsor to decide the code-review policy so the team can stop arguing and focus on velocity.
- CFacilitate a session where the team collectively drafts and agrees its ground rules, including how code review will be handled. Correct
- DLet the two members settle the code-review question privately and adopt whatever they agree.
Why A is wrong: Author-imposed rules look efficient, but a self-organising team commits to standards it helped shape; rules handed down are more likely to be ignored, and this does not resolve the specific disagreement.
Why B is wrong: Escalating to the sponsor may feel decisive, but ground rules are the team's responsibility, not the sponsor's, and outsourcing the decision removes the ownership that makes rules stick.
Why C is correct: Ground rules that the team creates together carry shared ownership, so members are far more likely to honour them; agreeing the review approach up front settles the recurring clash at its source.
Why D is wrong: Letting the pair resolve it avoids a group discussion, but ground rules affect the whole team, and a private deal between two members will not bind the other six or build collective buy-in.