Content deleted Content added
→History: "Canonical" though it may be - if that's the best source, then it doesn't appear to be notable enough to warrant here. It was a one off april fools joke. |
request clarification →Weaknesses |
||
Line 17:
* Projects experience a higher failure rate due to the decentralized nature of and volume of communication between members of the team.<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 |date=March 1981 | volume=24 | issue=3 | pages=106–113 | first=Marilyn | doi=10.1145/358568.358571}}</ref>
* Risky shift phenomenon{{snd}} 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 |date=March 1981 | volume=24 | issue=3 | pages=106–113 | first=Marilyn | doi=10.1145/358568.358571}}</ref>
* Simple tasks are made more difficult by open communication channels.{{Clarify}}{{citation needed|date=June 2014}}
==Rival concepts==
| |||