True or False: Management does not have a role within Scrum.

The statement is false. While "Manager" is not one of the three prescribed roles within a Scrum Team (which are Product Owner, Scrum Master, and Developers), management plays a critical and distinct role in an organization that adopts Scrum. The role of management shifts from traditional command-and-control to that of servant-leadership. Their responsibilities include fostering an environment where the Scrum Team can be effective, removing organizational impediments that are beyond the team's capacity to resolve, providing the necessary resources and support, and championing the principles of empiricism and agility throughout the organization. Therefore, to state that management has no role is incorrect; their role is simply different from a traditional one and is external to the day-to-day activities of the Scrum Team but essential for its success.

The option "True" is incorrect because it narrowly interprets the absence of a formal "Manager" role on the Scrum Team as a complete lack of any function or responsibility for management within the Scrum framework's implementation. The success of Scrum is heavily dependent on the active support, sponsorship, and impediment-removal capabilities of the organization's management.

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

Reference: Page 5. The guide states, "Scrum Teams are self-managing, meaning they internally decide who does what, when, and how." This principle does not eliminate the need for management but redefines its purpose. Instead of directing the team, management is responsible for creating the conditions and environment that empower the team to be self-managing. Their role is to support, not command.

2. Dingsøyr, T., Nerur, S., Balijepally, V., & Moe, N. B. (2012). A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software, 85(6), 1213-1221.

Reference: Section 4.1, "Contextual Factors". The paper synthesizes findings from numerous studies and explicitly identifies that "management support is found to be a critical success factor for agile methods adoption and practice." This directly contradicts the idea that management has no role.

DOI: https://doi.org/10.1016/j.jss.2012.02.033

3. Hoda, R., Noble, J., & Marshall, S. (2011). The impact of agile methods on software project management. In 2011 AGILE Conference (pp. 266-275). IEEE.

Reference: Section IV, "The Changing Role of the Project Manager". This research details how the roles of traditional management evolve in an Agile context. It states, "The agile PM [Project Manager] role was found to be a delicate balance of providing direction and taking a hands-off approach to let the team self-organise." This confirms that management's role changes and adapts, rather than disappears.

DOI: https://doi.org/10.1109/AGILE.2011.42