Closed-loop feedback control with Scrum
Scrum has its roots in ‘new product development’ [1] and empirical process control, but is mostly known for its impact on the world of software (product) development. Under ‘new product development’ we understand all work to create, deliver and sustain products.
As Scrum enters many other domains of society, it is most helpful to keep in mind that Scrum, in a broader sense, is a simple framework that supports people in addressing complex challenges (in often complex circumstances). New (software) product development surely falls into this category of work, but there are many more complex endeavors for which people are looking at Scrum nowadays.
It is quite essential to understand what the empirical approach is that Scrum intends to implement through its rules and roles. It is quite essential to understand how Scrum is designed to tackle complexity, in order to grasp the depth of the rules and roles and achieve more with Scrum, more successfully tackle your challenges.
Some characteristics of the process of new product development will helps us understand what complexity entangles. These characteristics can be transposed to many other problems, helping us to acknowledge their complexity and unpredictability.
