Applying systems thinking to enterprise implementations of Scrum

The organizational structures, roles, and responsibilities in Scrum are very different than those employed in the traditional hierarchical organization that employs program and project-management concepts to deliver products. Scrum eliminates the need for functional departments and flattens the organization by providing only three roles: product owner, Scrum Master, and developers. Scrum also eliminates the need for detailed project planning and scheduling, and instead employs empirical process control concepts to iteratively deliver new increments of functionality as market, customer, and end user priorities dictate:

Figure 4.17 – Identified elements involved in an enterprise Scrum implementation

In the previous section, you learned how to begin to assess the elements that could potentially impact a project-to-product development team transformation. In this section, you will learn how...