Analysis of the use of self-organization and subtle control in software projects
Mosquera Moya, Marlene Pilar · 2014
In recent years, the use of the Scrum methodology as a tool to organize and manage software development projects, has grown considerably among organizations. Due to its flexibility and approach to handle fast changing requirements and enabling team work and improvement, Scrum is considered by many software professionals to be the best alternative to implement their solutions.Most of the success of Scrum rests upon the concepts of self-organization and subtle control. With Scrum, teams work independently whereas control is applied indirectly and supervision and intervention are minimal.However, in spite of all the benefits and possibilities for success that Scrum offers, for many of its users not everything has been quite a happy experience. Indeed, self-organization and subtle control may be excellent principles to encourage cooperation and self-improvement, but they can also trigger dangerous situations when not applied or understood properly.Loss of authority and direction are typical risks with excessively self-organized teams, whereas discomfort and frustration are the results of too much control and intervention over the teams and their activities. Eventually, either case becomes an obstacle that jeopardizes the stability and order that shall exist within the working environment.The study helps visualize the reasons that originate such extreme situations. Through the analysis of the information obtained from Scrum users, the research shows the possible reasons why selforganization and subtle control may not function as successfully as expected, and the negative consequences that this may have over the project.The findings also reflect how people understand and apply self-organization and subtle control and how they interpret and assume their roles along the process. Other relevant issues that have been remarked during the research are the Scrum Master's and team members' approaches to handle problems such as loss of authority and excessive intervention.Additionally, the outcome of the study shows that a solid introduction and lecturing of the Scrum theory and principles are equally important to avoid further risks. The results have revealed as well, the importance of an active, constant communication and commitment among all the roles involved in the project in order to keep away unnecessary conflicts and tensions.The summary and conclusions include a brief recount of what can be improved in order to prevent that extreme self-organization and excessive control happen or at least minimize their negative impact on the success of the project.