universal operations Commons: 3/5

Scrum Detailed Variants Scrumscale Less Safe

Also known as:

1. Overview

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. It is a popular agile methodology that emphasizes collaboration, incremental delivery, and continuous improvement. The framework is built on empiricism, meaning that decisions are based on observation, experience, and experimentation [1]. The primary problem that Scrum addresses is the inherent complexity and uncertainty of modern product development. By working in short, iterative cycles called Sprints, teams can regularly inspect their progress and adapt their plans based on feedback from stakeholders [2]. Scrum was first introduced in 1995 by Ken Schwaber and Jeff Sutherland and is officially defined in the Scrum Guide [2].

2. Core Principles

  1. Empirical Process Control: Scrum is founded on the principles of empiricism, which asserts that knowledge comes from experience and making decisions based on what is known. The three pillars of empirical process control are transparency, inspection, and adaptation [2].

  2. Self-Organization: Scrum teams are self-organizing and cross-functional, with the autonomy to choose how to best accomplish their work [2].

  3. Collaboration: Scrum promotes a high degree of collaboration among team members and with stakeholders, ensuring that everyone is aligned and working towards the same goal [1].

  4. Value-Based Prioritization: The Product Owner is responsible for prioritizing the work in the Product Backlog based on its value to the customer and the organization [2].

  5. Time-boxing: All Scrum events are time-boxed, creating a regular cadence for the team and ensuring that a consistent amount of time is dedicated to planning, inspection, and adaptation [2].

  6. Iterative Development: Scrum follows an iterative and incremental approach. The product is built in a series of short, consistent cycles called Sprints, at the end of which a potentially shippable increment of the product is delivered [1].

3. Key Practices

  1. The Sprint: The heart of Scrum is the Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created [2].

  2. Scrum Events: Each Sprint contains five events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. These events are designed to enable transparency, inspection, and adaptation [2].

  3. Scrum Artifacts: Scrum defines three artifacts: the Product Backlog, the Sprint Backlog, and the Increment. These artifacts are designed to provide transparency and to enable inspection and adaptation [2].

4. Application Context

Scrum is best utilized for complex projects where requirements are not fully understood or are likely to change. It is not suitable for simple, predictable projects with well-defined, stable requirements. In terms of scale, Scrum is originally designed for a single team, but can be scaled to multiple teams with frameworks like Scrum@Scale, LeSS, and SAFe [3, 4, 5]. Scrum has its roots in software development, but its application has expanded to various other domains, including IT, marketing, and R&D.

5. Implementation

Successful implementation of Scrum requires a genuine commitment from leadership to embrace the agile mindset, the formation of a dedicated and cross-functional team, and a clear and prioritized Product Backlog. Getting started involves selecting a pilot project, providing the team with the necessary training, and appointing a Scrum Master. Common challenges include resistance to change, the lack of a clear Product Backlog, and difficulty with the concept of self-organizing teams. Key success factors include having a dedicated and empowered Product Owner, a strong and experienced Scrum Master, and a committed and collaborative team.

6. Evidence & Impact

Scrum has been adopted by a wide range of organizations, including Gillette, Toyota Connected, and Akbank. The adoption of Scrum has been shown to lead to increased productivity, faster time to market, improved product quality, and enhanced team morale. A 2019 report by the Standish Group found that agile projects are three times more likely to be successful than waterfall projects.

7. Cognitive Era Considerations

The cognitive era presents significant opportunities to augment the Scrum framework with AI and automation. AI-powered tools can automate repetitive tasks, analyze data to provide insights, and create realistic simulations for training. However, it is important to strike the right balance between human and machine intelligence, as the core principles of Scrum, such as collaboration and creative problem-solving, remain uniquely human. In the future, we can expect to see the emergence of new roles, such as the “AI Scrum Master,” and the development of new tools that are specifically designed to support the use of AI and automation in Scrum.

8. Commons Alignment Assessment (v2.0)

This assessment evaluates the pattern based on the Commons OS v2.0 framework, which focuses on the pattern’s ability to enable resilient collective value creation.

1. Stakeholder Architecture: The pattern defines clear roles and responsibilities for the core delivery team and the Product Owner, who represents business and customer stakeholders. However, it lacks a formal architecture for engaging a wider set of stakeholders, such as the environment or future generations, whose rights and responsibilities are not explicitly defined within the framework. The focus remains on the value exchange between the organization and its immediate customers.

2. Value Creation Capability: Scrum excels at creating economic and knowledge value by focusing on delivering the highest-value features first and fostering continuous learning. While it builds project resilience and social value within the team through collaboration, its capability to generate broader ecological or systemic social value is not inherent. The framework is agnostic to the nature of the value being produced, making it a powerful tool whose output is entirely dependent on the goals set by the Product Owner.

3. Resilience & Adaptability: Resilience and adaptability are at the very core of this pattern, representing its greatest strength. The iterative cycle of Sprints, combined with continuous feedback loops (Daily Scrum, Sprint Review, Retrospective), allows teams to thrive on change and adapt to complexity. This structure ensures the system maintains coherence under the stress of changing requirements and market uncertainty.

4. Ownership Architecture: The pattern’s concept of ownership is focused on process and product, not on equity or formal stakeholder governance. The Product Owner ‘owns’ the backlog, and the team ‘owns’ the Sprint Backlog and the process for creating the increment. This defines ownership as clear responsibility and stewardship over components of the value creation process, but it does not address the distribution of monetary or non-monetary equity that results from it.

5. Design for Autonomy: Scrum is highly compatible with distributed systems and promotes team autonomy, a key prerequisite for DAOs and AI-augmented workflows. Its low coordination overhead, managed through defined events and roles, allows teams to self-organize effectively. The clear, prioritized backlog can be interpreted and acted upon by autonomous agents, provided the tasks are well-defined.

6. Composability & Interoperability: The pattern is explicitly designed for composability, as evidenced by scaled frameworks like Scrum@Scale, LeSS, and SAFe, which combine Scrum with other patterns to manage larger, more complex systems. It interoperates well with technical practices from Extreme Programming (XP) and governance models like Holacracy. Its modular nature allows it to be a foundational building block in a larger organizational value-creation system.

7. Fractal Value Creation: Scrum’s value-creation logic is inherently fractal. The core empirical loop of transparency, inspection, and adaptation applies to the daily work of a developer, the cycle of a Sprint for a team, the release cadence of a product, and the strategic pivots of an entire organization (as seen in Scrum@Scale). This allows the fundamental principles of adaptive value creation to be applied consistently at multiple scales.

Overall Score: 4 (Value Creation Enabler)

Rationale: Scrum is a powerful engine for adaptive value creation and learning, making it a strong enabler for commons-based projects. Its emphasis on team autonomy, iterative feedback, and composability aligns well with the principles of resilient systems. However, it scores a 4 instead of a 5 because it is fundamentally a process framework, agnostic to the type of value being created. It lacks a built-in stakeholder architecture beyond the immediate project, and its ownership model is procedural rather than equitable, requiring integration with other patterns to form a complete value creation architecture.

Opportunities for Improvement:

  • Integrate a formal stakeholder mapping and engagement model (e.g., a ‘Commons Council’) into the Sprint Review process to include non-obvious stakeholders.
  • Explicitly define ‘Value’ in the Product Backlog to include metrics for social and ecological well-being, not just economic or functional utility.
  • Combine the pattern with distributed ownership models (e.g., co-operative or tokenized equity) to ensure the value created is distributed fairly among all contributing stakeholders.

9. Resources & References

Essential Reading:

  • The Scrum Guide: The official guide to Scrum, written by its co-creators, Ken Schwaber and Jeff Sutherland.
  • Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland.
  • Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum by Craig Larman and Bas Vodde.

Organizations & Communities:

  • Scrum.org
  • Scrum Alliance
  • Scaled Agile, Inc.

Tools & Platforms:

  • Jira
  • Trello
  • Miro

References:

[1] Scrum.org. (n.d.). What is Scrum? Retrieved from https://www.scrum.org/resources/what-scrum-module

[2] Sutherland, J., & Schwaber, K. (2020). The Scrum Guide. Retrieved from https://scrumguides.org/scrum-guide.html

[3] Scrum@Scale. (n.d.). The Scrum@Scale Guide. Retrieved from https://www.scrumatscale.com/scrum-at-scale-guide/

[4] Atlassian. (n.d.). The Large-Scale Scrum (LeSS) framework. Retrieved from https://www.atlassian.com/agile/agile-at-scale/less

[5] Wikipedia. (2023, May 23). Scaled Agile Framework. Retrieved from https://en.wikipedia.org/wiki/Scaled_Agile_Framework