CSC/ECE 517 Fall 2007/wiki3 9 pp: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
==What is Collective Ownership?== | ==What is Collective Ownership?== | ||
Collective code ownership means that everybody is responsible for all the code; this, in turn, means that everybody is allowed to change any part of the code. Pair programming contributes to this practice: by working in different pairs, all the programmers get to see all the parts of the code. | |||
===Advantages=== | |||
===Disadvantages=== | |||
===Examples=== | ===Examples=== | ||
Revision as of 08:48, 19 November 2007
Collective Ownership and Continuous Integration
Question:Two of the important Agile methodologies that we have not said much about in this course are collective ownership and continuous integration. What are the best definitions or examples you can find? Are these widely practiced? Are they controversial? Are there adherents of other design methodologies who consider them harmful? Investigate, through the Web and through the ACM DL.
Introduction To Agile Methodologies
What is Collective Ownership?
Collective code ownership means that everybody is responsible for all the code; this, in turn, means that everybody is allowed to change any part of the code. Pair programming contributes to this practice: by working in different pairs, all the programmers get to see all the parts of the code.