Who uses Scrum?

Obvious:

In this domain, both the problem/requirement and solution are clear. We can call it known knowns. Since things are known, we sense (get an understanding), categorize (what could be done based on sensing), and then respond (apply what is feasible for the problem/requirement). 

For example, Level 1 support projects will fall into this domain. Say, if someone calls technical support and informs them that you were unable to log in to the platform. 

The technical support then identifies the problem you are facing, categorizes them based on where they fall, and responds with the list of things that you need to do to solve the problem. 

Maintenance and support projects usually fall into this domain by which standard operations procedures and practices are applicable. We need operational thinking in this domain to optimize efficiency. 

Complicated:

In this domain, the problem/requirement is clear, but the solution isn't clear. We can call it known unknowns. Since the approach or the solution to the problem is unknown, the problem/requirement needs analysis. 

In a complicated domain, we sense (get an understanding), analyze (examine the possibilities to solve the problem), and then respond (solve the problem/requirement by applying a solution based on analysis). 

Migration and enhancement projects fall into this domain. We need project thinking in this domain for optimizing the right application of skills. 

Complex:

In this domain, both the problem/requirement and the solution are unclear. We call it unknown unknowns. In this domain, we probe (since both are unknown),  sense (get an understanding), and then respond (based on knowledge through probing). 

We need to run iterative development through continuous feedback to build it right or pivot or course-correct since it is a complex domain. New product development falls into this domain. We need to optimize learning through Product Thinking. 

Chaotic:

In this domain, the problem/requirement and solution are still unclear. But, things need action before probing. Consider the example of a fire accident in the building: and we need to put out the fire before investigating or analyzing it. 

Another typical example would be a server, or a data center going down. We work towards bringing it back to working condition first before examining the reasons for it going down.

In this domain, we act (things have to be standard first), sense (get an understanding of what and how), and then proceed with a response. 

Optimizing safety is our primal concern here, and it is achieved through survival thinking. 

 Where is Scrum Applicable?

Scrum is applicable in the complex domain where the requirements and solutions are unknown or not clear. We need to run iterative development with continuous feedback to reduce the Cost of Delay and Cost of Production. 

Sprints are safe to fail experiments where we can run experiments to uncover the problem and experiment further on the solutions. 

Scrum is all about frequent inspection and adaptation. Based on the continuous feedback on our experiments, we can continuously inspect and adapt the products that we build and provide value to the users/customers. 

The majority of Fortune 500 companies use Scrum for their product development for maximum ROI. 

With 11+ years of experience in the field, Leanpitch has successfully upskilled 90,000+ people across 12+ countries. Explore our website, Our trainers are internationally acclaimed for their insightful and experiential training.

We upskill and boost your career by providing a wide range of courses such as CSPO, CSM, ICP-ACC, etc. visit our website to learn more about all the courses we offer.