Scrum — A Value-based Process Framework
Pragmatic Value-based experience sharing about the Scrum Framework using Scrum events.
In today’s VUCA world due to increasing complexity factors and operating conditions around organizational structures and systems. We tend to hear a lot of efforts focussed on initiatives such as “Agile Transformation”, “Business Agility”, “Lean UX”, “Design Thinking” and many more amongst the industry which are embraced and instilled majorly within the software development community using many frameworks and practices right from single team to a whole gamut business of which “Scrum” is popular as per the 13th annual State of Agile survey (as per below image). Also, I firmly believe that Scrum is a bottom-up intelligence enabler for any framework prevailing amongst the market place because of its foundation based on empiricism.
Scrum is founded on empirical process control theory or empiricism. — Scrum Guide 2017
Before we deep dive into the insights about Scrum — A Value-based Framework, let us understand the definition of Scrum from the real source of truth the one and only Scrum Guide.
Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. — Scrum Guide 2017
Also noteworthy to know the below statement within the Scrum Guide about how “values” form an integral part of Scrum Framework to implement it successfully and reap real outcomes out of it.
When the values of commitment, courage, focus, openness, and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone. The Scrum Team members learn and explore those values as they work with the Scrum roles, events, and artifacts.
Successful use of Scrum depends on people becoming more proficient in living these five values. — Scrum Guide 2017
In my humble point of view and experience unless people the valuable asset of any organization are intrinsically motivated and aligned to their behavior and principles they will not sustain to it which is linked to the values. So let us quickly go through the Scrum Values which are the guiding light for realizing the true essence of Scrum Framework as described in Scrum Guide.
People personally commit to achieving the goals of the Scrum Team.
The Scrum Team members have courage to do the right thing and work on tough problems.
Everyone focuses on the work of the Sprint and the goals of the Scrum Team.
The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.
Scrum Team members respect each other to be capable, independent people.
Let us now delve further about why Scrum can be called out as “A Value-based Framework” with the help of events associated with the Scrum Framework along with values to be demonstrated by the entire Scrum Team.
Sprint
The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. — Scrum Guide 2017
Focus: To build the right things.
Courage: To build things rightly.
Commitment: To create the minimum viable increment of the customer value proposition.
Openness: To deal with the uncertainty while building the increment.
Respect: Respect the sense of purpose of all the events held within a sprint.
Sprint Planning
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The work to be performed in the Sprint is planned at the Sprint Planning. — Scrum Guide 2017
Focus: On the Goal crafted by the entire Scrum Team.
Courage: By demonstrating a readiness to adapt to the upcoming unknowns.
Commitment: Listing out the first things first for the first days of the Sprint.
Openness: To seek valuable inputs from the people associated with other units of the organization.
Respect: Respect each other’s professional experience within the organization in terms of knowledge and skills.
Daily Scrum
This is a key inspect and adapt meeting.The Daily Scrum is a 15-minute time-boxed event for the Development Team. — Scrum Guide 2017
Focus: On the daily plan identified.
Courage: To call out the impediments affecting the Goal.
Commitment: Towards achieving the Goal.
Openness: To seek help and collaborate with the other people associated with the Scrum team.
Respect: Respect the time-box of the event.
Sprint Review
A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.This is at most a four-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. — Scrum Guide 2017
Focus: On identifying the next set of things for the upcoming Sprint.
Courage: To share the ideas and risk that benefits the customer value.
Commitment: Towards inspecting the increment built by all means possible.
Openness: To share the timelines of value realization and learn from the feedback shared by the stakeholders.
Respect: Respect the contribution of work done by each member of the Scrum team during the sprint.
Sprint Retrospective
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. This is at most a three-hour meeting for one-month Sprints. — Scrum Guide 2017
Focus: On identifying the action items for improvement.
Courage: To provide constructive and candid feedback among Scrum team members .
Commitment: Towards having meaningful conversation that contributes the success of the team.
Openness: Towards self-introspection and receive feedback from fellow members within the Scrum Team.
Respect: Respect each other’s opinion about improving ways of working going forward with the help of any complementary practices (if applicable).
Finally would like to conclude this article with a quote written by The independent Scrum Caretaker, Gunther Verheyen which conveys the key message for maximizing the benefits when implementing the Scrum Framework elsewhere.
As always, I am open and eager about hearing each of your valuable thoughts and feedback to inspect and adapt in my next article.
References:
