Scrum is a flexible, collaborative approach to project management that has been growing increasingly popular across various sectors. It allows for rapid development, testing, and adaptation of complex projects. However, adopting Scrum processes within an organization can be a challenging endeavor. This article will compare and contrast two popular systemic approaches to improving Scrum adoption: the ShuHaRi framework and the Vitality Model.
1. ShuHaRi Framework
ShuHaRi is a conceptual framework that is commonly used to demonstrate the progressive stages of learning towards mastery. This framework is often adopted to foster organizational understanding and skills in Scrum.
1.1 Shu (Follow the rule)
At this stage, the organization should follow all the rules and guidelines of the Scrum methodology rigidly. This includes forming cross-functional teams, organizing regular Scrum ceremonies like daily Scrum, sprints, and retrospectives, and practicing the roles of Scrum (Scrum Master, Product Owner, and Scrum Team). The main goal at this stage is to adopt Scrum procedures and practices fully.
1.2 Ha (Break the rule)
The ‘Ha’ phase of the ShuHaRi framework is about understanding the reasoning behind the rules of Scrum. Here, you start to see where and when it may be appropriate to modify or dispense with the rules as a result of experience and learning.
1.3 Ri (Create the rule)
In the ‘Ri’ phase, the organization has become proficient enough to evolve their practices beyond standard Scrum practices. This is where innovation and distinctiveness in Scrum practices are fostered based on the specific needs of the organization.
2. The Vitality Model
The Vitality Model, contrary to the ShuHaRi, focuses on the lifecycle of the entire organization rather than individuals. It advocates for resource and personnel flexibility in order to facilitate a smooth Scrum transition.
2.1 Setup (Infrastructure)
The Vitality model begins with setting up the infrastructure. This includes having a clear vision, establishing ground rules, defining the roles and responsibilities, forming dedicated Scrum teams, and investing in required technologies.
2.2 Learning
In this stage, training and adaptive learning are reinforced. The team should understand their roles, Scrum practices and appropriate technical practices. This might involve hiring a Scrum Master or Agile Coach for proper training and guidance.
2.3 Sustaining
After successful implementation, the next challenge is about ensuring sustainability. Here, an organization should institutionalize Scrum practices and ensure continuous adoption and adaptability. It’s also crucial to foster a culture of continuous learning and improvement.
These two models, while having their unique approaches, can be complementarily used to foster Scrum adoption. The ShuHaRi approach can be beneficial for teams on a more operational level while the Vitality Model may offer a strategic perspective, looking at the bigger picture of the Scrum adoption process.
In summary, for successful Scrum adoption, it’s essential to have a strong foundation in theory, initially sticking to the rules of Scrum, but ultimately being able to understand and adapt them to the particular context of the organization. The choice between these two systemic approaches or a combination of both may depend on where the organization currently stands in its Scrum adoption journey and its unique context.
Practice Test
True/False: Systemic approaches for helping organizations improve their Scrums adoption include the Scrum@Scale and Large Scale Scrum (LeSS) framework.
- Answer: True
Explanation: Scrum@Scale and Large Scale Scrum (LeSS) are systemic approaches designed to scale Scrum for use in large and complex organizations, thus supporting Scrum adoption.
Single Select: Which of the following is not typically a systemic approach for helping organizations improve their Scrum adoption?
- a) Scrum@Scale
- b) Large Scale Scrum (LeSS)
- c) SAFe ScrumXP
- d) Waterfall method
Answer: d) Waterfall method
Explanation: The Waterfall method is a traditional project management approach not designed to improve Scrum adoption. It’s linear and sequential, unlike the iterative Scrum framework.
True/False: A systemic approach to improving Scrum adoption requires changes to the entire organizational structure.
- Answer: True
Explanation: Systemic approaches to improve Scrum adoption often require changes that affect the entire organization, as these approaches focus on integrating Scrum principles and practices across all levels.
Single Select: The systemic approach of Scrum@Scale is based on whose theories?
- a) Frederick W. Taylor
- b) Jeff Sutherland
- c) Henry Gantt
- d) Eliyahu M. Goldratt
Answer: b) Jeff Sutherland
Explanation: Scrum@Scale was created by Dr. Jeff Sutherland, the co-creator of Scrum. It’s designed to scale productivity, deliverinnovation, and reduce time-to-market.
True/False: Only large organizations can adopt the LeSS framework for Scrum adoption.
- Answer: False
Explanation: Although Large Scale Scrum (LeSS) is designed to scale Scrum to larger organizations, small-to-mid-sized organizations can also adopt LeSS if they work on large and complex projects, or simply wish to adopt its principles.
Single Select: The goal of adopting a systemic approach to Scrum is to:
- a) Eliminate the need for Scrum Masters
- b) Make every team member a Product Owner
- c) Save cost on project management software
- d) Integrate Scrum principles and practices at all levels
Answer: d) Integrate Scrum principles and practices at all levels
Explanation: The aim of adopting a systemic approach to Scrum is to align the organization to Scrum principles and practices, ensuring agility, productivity, and value delivery at all levels.
True/False: When adopting Scrum@Scale, an organization should create a “Scale-free” architecture.
- Answer: True
Explanation: When adopting Scrum@Scale, an organization should create a “scale-free” architecture. This allows teams to work on separate parts of the system without being blocked by other teams, enhancing productivity and scalability.
Single Select: The main difference between LeSS and Scrum@Scale is:
- a) Only LeSS requires a Scrum Master
- b) Scrum@Scale is specifically designed for software development
- c) LeSS focuses on scaling up Scrum teams, while Scrum@Scale focuses on scaling the Scrum framework itself
- d) Only Scrum@Scale recommends developing a “scale-free” architecture
Answer: c) LeSS focuses on scaling up Scrum teams, while Scrum@Scale focuses on scaling the Scrum framework itself
Explanation: While both LeSS and Scrum@Scale aim to scale Scrum, LeSS does it by multiplying Scrum teams, and Scrum@Scale scales the framework itself through coordinating multiple Scrum teams working together.
True/False: The SAFe (Scaled Agile Framework) is a Scrum-based approach.
- Answer: True
Explanation: The Scaled Agile Framework (SAFe) is a Scrum-based approach that applies Lean and Agile principles to large organizations.
Single Select: The systemic approach most suitable for an organization to improve Scrum adoption depends on:
- a) The experience of the Scrum Master
- b) The size and complexity of the organization’s projects
- c) The budget allocated for training
- d) The personal preference of the Product Owner
Answer: b) The size and complexity of the organization’s projects
Explanation: The most suitable systemic approach for an organization depends on several factors, primarily the size and complexity of the projects that the organization undertakes. This influences how Scrum can be scaled effectively.
Interview Questions
What are two examples of systemic approaches organizations might use to improve their Scrum adoption?
Two systemic approaches include the Systems Thinking approach and the Agile Transformation approach.
What is the primary focus of the Systems Thinking approach in Scrum adoption?
The Systems Thinking approach encourages viewing the organization as a whole, interconnected system. The objective is to identify patterns, interrelationships, and dependencies within the organization which can impact Scrum adoption.
How does the Agile Transformation approach assist in improving Scrum adoption?
In the Agile Transformation approach, organizations systematically transition towards Agile and Scrum methodologies. This involves comprehensive change management, training, and support to ensure that the values, principles, and practices of Agile and Scrum permeate throughout the organization.
How are the Systems Thinking and Agile Transformation approaches similar?
Both approaches appreciate the importance of taking a holistic view of the organization and understanding that successful Scrum adoption involves more than just implementing new practices – it requires changes in attitudes, beliefs, and values.
How are the two approaches different in their way of improving Scrum adoption?
Systems Thinking focuses more narrowly on understanding and improving existing relationships and interactions within the organization to optimize Scrum adoption. In contrast, Agile Transformation takes a broader perspective, aligning the entire organizational culture and strategies with Agile and Scrum.
Which approach, Systems Thinking or Agile Transformation, is best for organizations new to Scrum?
The Agile Transformation approach might be more suitable as it provides thorough, step-by-step guidance for transitioning to Agile and Scrum.
Why might an organization choose the Systems Thinking approach over the Agile Transformation approach?
An organization might choose Systems Thinking if they are already following Scrum but are having difficulties managing interdependencies and understanding the overall system.
How is Systems Thinking approach beneficial in an organization with multiple interconnected departments?
Systems Thinking helps to understand and manage impacts and dependencies among different departments. This allows for smoother Scrum implementation and reduces potential conflicts and resistance that may arise due to changes.
In the Agile Transformation approach, what roles do leadership play in Scrum adoption?
Leadership has a pivotal role in driving the Agile Transition, setting the vision, promoting Agile values & principles, removing impediments, and ensuring adequate training and resources are given to the teams.
How might the Systems Thinking approach influence the communication within a Scrum team?
Systems Thinking approach encourages open and transparent communication which is crucial for effective Scrum. By understanding the system, its relationships, and patterns, teams can better navigate and communicate about changes and impediments.
Can organizations combine both Systems Thinking and Agile Transformation approaches for Scrum adoption?
Yes, organizations can use these approaches complementarily. While Agile Transformation can provide the broader framework for the transition, Systems Thinking can add depth by optimizing interactions within the system.
How does a successful Scrum adoption impact an organization using the Agile Transformation approach?
Successful Scrum adoption using the Agile Transformation approach leads to increased flexibility, better product quality, faster delivery, improved customer satisfaction, and enhanced team morale.
How does organizational culture impact Scrum adoption in the Agile Transformation approach?
Organizational culture plays a vital role as it can either facilitate or hinder the Agile Transformation. A supportive culture is one that values collaboration, transparency, and flexibility, which align with Agile and Scrum principles.
What are some potential pitfalls of using the Systems Thinking approach?
Potential pitfalls may include resistance to change due to established patterns and relationships or a tendency to focus too much on details, losing sight of the bigger picture or overall Scrum goals.
What is an important factor to consider when choosing between the Systems Thinking and Agile Transformation approaches?
The current state of the organization, its readiness for change, pre-existing complexities, and the overall organizational culture are important factors to consider when choosing the appropriate approach.
extutorials.com