True or False: Using Scrum ensures that adding more resources to a project proportionally increases the value delivered.

The statement is false because it posits a linear, predictable relationship between adding resources (people) and delivering value, which is contrary to the principles of Scrum and the nature of complex work. In complex environments, adding more people to a team does not guarantee a proportional increase in value. Instead, it often leads to diminishing returns due to increased communication overhead, coordination complexity, and integration challenges. This phenomenon is famously described by Brooks's Law, which states that adding manpower to a late software project makes it later. The Scrum framework is designed to address this complexity. The Scrum Guide explicitly recommends small team sizes to optimize communication, focus, and agility. A larger team can become less productive as more time is spent on alignment and coordination rather than on value-creating work. Value in Scrum is maximized through empiricism—inspecting and adapting based on feedback—and by a focused, self-managing team delivering a Done Increment, not by simply increasing the number of team members. Why the "True" Option is Wrong: The "True" option is incorrect because it fundamentally misunderstands the nature of complex product development. It assumes a mechanistic model where inputs (people) directly and proportionally determine outputs (value). This ignores the non-linear dynamics of team collaboration, the exponential increase in communication pathways as a team grows, and the empirical process control that is at the heart of Scrum. Scrum does not "ensure" such a proportional increase; in fact, its guidelines on team size are designed to prevent the negative consequences of this flawed assumption.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org.

Reference: Page 5, Section "The Scrum Team".

Quote/Paraphrase: The guide states, "The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people... In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product." This directly contradicts the idea that simply adding more people is beneficial, instead advocating for small, cohesive teams to maintain productivity.

2. Brooks, F. P. (1995). The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition. Addison-Wesley Professional.

Reference: Chapter 2, "The Mythical Man-Month".

Quote/Paraphrase: Brooks's Law is a foundational principle in software engineering, taught in reputable university computer science programs. It posits that communication overhead and the complexity of dividing tasks increase as more people are added to a team. The number of communication channels increases with the formula n(n-1)/2, where n is the number of people. This non-linear increase in overhead means that adding people can slow down a project rather than speed it up, directly refuting the claim of a proportional increase in delivered value.

3. Massachusetts Institute of Technology (MIT) OpenCourseWare. (2013). 6.170 Software Studio, Lecture 1: Introduction.

Reference: Course materials discussing the challenges of software engineering.

Quote/Paraphrase: Reputable university curricula, such as MIT's Software Studio course, introduce students to the inherent complexities of software development. These courses teach that software engineering is not like manufacturing and that adding more workers does not scale linearly. They explicitly cover concepts like Brooks's Law to explain why simply increasing team size is an ineffective and often counterproductive strategy for increasing output or value. This academic consensus supports the conclusion that the statement is false.