CSC/ECE 517 Fall 2007/wiki3 9 pp: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
===Advantages=== | ===Advantages=== | ||
A major advantage claimed for collective ownership is that it speeds up the development process, because if an error occurs in the code any programmer may fix it. | |||
===Disadvantages=== | ===Disadvantages=== | ||
By giving every programmer the right to change the code, there is risk of errors being introduced by programmers who think they know what they are doing, but do not foresee certain dependencies | |||
===Examples=== | ===Examples=== | ||
Revision as of 08:49, 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.
Advantages
A major advantage claimed for collective ownership is that it speeds up the development process, because if an error occurs in the code any programmer may fix it.
Disadvantages
By giving every programmer the right to change the code, there is risk of errors being introduced by programmers who think they know what they are doing, but do not foresee certain dependencies