CAPM Practice: Determine how to prepare and execute task management steps

Collective code ownership means any team member can modify any part of the codebase. It prevents knowledge silos, eliminates bottlenecks when specialists are unavailable, and distributes quality responsibility across the whole team.

**Why not A:** Collective code ownership is an XP/agile engineering practice describing how a development team shares responsibility for the codebase — it is not a legal or intellectual property concept. Corporate IP ownership is a separate matter governed by employment agreements and has no bearing on this practice.

**Why not B:** Assigning each module to a single gatekeeper-developer is the opposite of collective code ownership — it creates individual silos and bottlenecks. If that specialist is unavailable, work on their module stalls, which is precisely the risk collective ownership is designed to eliminate by distributing knowledge across the team.

**Why not C:** Storing code in a shared repository accessible to all employees is a version-control configuration, not collective code ownership. Repository access alone does not empower team members to modify any part of the codebase freely; collective ownership is a team norm and cultural agreement about responsibility, not a storage setting.