Egoless programming: Difference between revisions

Revision as of 00:28, 8 May 2012

Revision as of 03:51, 14 February 2013

Line 13:

*open communication channels allow information to flow freely to team members

*greater conformity that helps in consistent documentation

*team members have greater job satisfaction<ref>http: name="mantei1981"//sunnyday.mit.edu/16.355/mantei-teams.pdf</ref>

==Weaknesses==

*projects take a longer time to complete

*risky shift phenomenon - programmers attempt riskier solutions to solve a software problem<ref name="mantei1981">{{cite journal | url=http://sunnyday.mit.edu/16.355/mantei-teams.pdf | title=The Effect of Programming Team Structures on Programming Tasks | last=Mantei | journal=Communications of the ACM | year=1981 | month=March | volume=24 | issue=3 | pages=106-113 | first=Marilyn}}</ref>

*simple tasks made more difficult by open communication channels