A fourth explanation to Brooks' Law - The aspect of group developmental psychology

April 04, 2019 Β· Declared Dead Β· πŸ› IEEE/ACM International Conference on Connected Health: Applications, Systems and Engineering Technologies

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Lucas Gren arXiv ID 1904.02472 Category cs.SE: Software Engineering Citations 2 Venue IEEE/ACM International Conference on Connected Health: Applications, Systems and Engineering Technologies Last Checked 4 months ago
Abstract
Brooks' Law is often referred to in practice and states that adding manpower to a late software project makes it even later. Brooks' himself gave three explanation only related to concrete task-related issues, like introducing new members to the work being done, communication overheads, or difficulty dividing some programming tasks. Through a description of group developmental psychology we argue for a fourth explanation to the law by suggesting that the group will fall back in its group development when new members are added, resulting in rework setting group norms, group goals, defining roles etc. that will also change over time. We show that this fourth explanation is important when trying to understanding Brooks' Law, and that adding the group developmental perspective might help software development organizations in managing projects.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted