{"id":718,"date":"2021-12-05T16:30:29","date_gmt":"2021-12-05T16:30:29","guid":{"rendered":"https:\/\/be-agile.agile-world.org\/?p=718"},"modified":"2021-12-05T16:30:29","modified_gmt":"2021-12-05T16:30:29","slug":"collective-code-ownership","status":"publish","type":"post","link":"https:\/\/publicagile.org\/collective-code-ownership\/","title":{"rendered":"Collective Code Ownership"},"content":{"rendered":"

A hallmark of Agile software development teams is the notion that any developer can contribute to the code base. Collective code ownership is a practice that originated in eXtreme Programming<\/a> (XP), and one of its many benefits is that no one person can become a bottleneck when it comes to making the code better. A key component of collective code ownership is that each developer writes unit tests for their new or modified code, and that execution of those unit tests serves as an indicator that the code base is healthy.<\/p>\n

Related Media<\/h3>\n

Collective Code Ownership Video<\/h4>\n

Collective Code Ownership Podcasts<\/h4>\n

Collective Code Ownership Example<\/h4>\n

Related Subjects<\/h3>\n

CI – Continuous Integration<\/a><\/p><\/blockquote>\n