During a conversation today my friends, software project managers and scrum masters in Pune, asked me about my voyage from Indian Air Force to software development and the motivation to adopt Scrum for managing projects. The most motivating instance for me to dive in this new role is that I have served Indian Air Force for almost 20 years and -Jeff Sutherland, the creator of Scrum was a fighter pilot in US Air Force. So I can proudly mention it as an ‘Air Force effect’. :-)
More on this in future…..
Let’s move further to see what are the domains best suited for Scrum:
- Simple domain: The domain where everyone can see cause and effect, scrum may be used but not the best fit. For example, if we want to reproduce the same product over and over again, a well-defined assembly-line process would be a better fit than Scrum.
- Sense
- Categorize
- Respond
- Complicated domain: Complicated domains need good practices dominated by experts. For example, code optimization/query optimization for better performance, Scrum can be applied here but not the best option.
- Sense
- Analyze
- Respond
- Chaotic domain: In such domains due to crisis there exists need to act immediately, a rapid response.
- Act
- Sense
- Respond
- Complex domain: Such domain is the domain of emergence and need creative and innovative approaches. Such domains are best suited for applying Scrum framework.
Situation-appropriate approach:
- Probe
- Sense
- Respond
- Domain in Disorder: Disorder domain when it is not clear which of the other domains one is in. Time is to interpret and act accordingly.
- Break down the situation into constituent parts
- Assign each to one of the other four domains.
1.
Simple
2. Complex
3. Complicated
4. Chaotic
- Interrupt-Driven Work: Domain with the frequent change such as support requests is not meant for Scrum. Kanban is the best suited for such domains. We will discuss on Kanban in near future.
Situation-appropriate approach:
- Visualize
- Limit work in process
- Manage flow
No comments:
Post a Comment