An agile team member frequently borrows another's password to access the development platform. A code version was modified without authorization and no one will accept responsibility. What should the project lead have done to prevent this?

Defining ground rules early in a project establishes clear expectations for team behavior, including access protocols, accountability, and ethical conduct. This proactive step would have addressed the unauthorized password sharing and code modification by setting boundaries and consequences. While checking user permissions is important, it's a technical control that might not prevent someone from giving their password away. Reviewing security policies is also crucial, but ground rules translate those policies into actionable team norms. Sharing the code of ethics is valuable for general guidance, but ground rules provide specific, agreed-upon behavioral expectations for the team.