teams:rebased_scrum

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
teams:rebased_scrum [2026/02/15 20:17] – Added the values, principles and design principles dennmansteams:rebased_scrum [2026/03/30 14:47] (current) – dennmans
Line 1: Line 1:
-====== Rebased from the 2020 Scrum Guide ====== +====== OpenScrum v2 ======
  
-This rebased version of the Scrum Guide is a remix of the November 2020 version available as a PDF [[https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf#zoom=100 | here]].  Although it is mostly the compatible practices like user stories, story points and estimation poker that have been deprecated, ownership also needed addressing, as products are often community-owned and there is no concept of a single Product Owner.  Also, team membership and The rest of the changes are to use the naming conventions that are current, industry-wide practice.  New versions of this fork can be brought out more continuously than with the original version.  +===== Rebased from the 2020 Scrum Guide ===== 
 + 
 +This rebased version of the Scrum Guide is a fork of the November 2020 version available as a PDF [[https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf#zoom=100 | here]].  Although it is mostly the compatible practices (like user stories, story points and estimation poker) that have been deprecated, ownership also needed addressing, as products are often community-owned and open products do not have a single Product Owner.  Also, team membership varies widely both in number and in role.  The rest of the changes are to use the naming conventions that are current, industry-wide practice.  New versions of this fork can be brought out more continuously than with the original version.  
  
 ===== Purpose of the OpenScrum Guide ===== ===== Purpose of the OpenScrum Guide =====
  
-Scrum was developed in the early 1990s. The first version of the Scrum Guide was written in 2010 by Jeff Sutherland and Ken Schwaber to help people worldwide understand Scrum. The Guide has evolved since then through small, functional updates. OpenScrum was first mentioned in [[https://scholarworks.indianapolis.iu.edu/server/api/core/bitstreams/a39adc65-1e80-41fb-b270-0b8fe393e58b/content| Purkayastha (2014) - OpenScrum: Scrum methodology to improve shared understanding in an open-source community.]] In 2026 a community of Agilists decided to fork and re-base Scrum to have a community-owned and updated version for use in current project setups including [[wp>FLOSS]] development with voluntary contributors in collectives and cooperatives.  This is OpenScrum.  +Scrum was developed in the early 1990s. The first version of the Scrum Guide was written in 2010 by Jeff Sutherland and Ken Schwaber to help people worldwide understand Scrum. The Guide has evolved since then through small, functional updates. OpenScrum was first mentioned in [[https://scholarworks.indianapolis.iu.edu/server/api/core/bitstreams/a39adc65-1e80-41fb-b270-0b8fe393e58b/content| Purkayastha (2014) - OpenScrum: Scrum methodology to improve shared understanding in an open-source community.]] In 2026 a community of Agilists decided to fork and rebase Scrum and remix it with the [[https://ica.coop/en/cooperatives/cooperative-identity | Rochdale Principles]] and the [[https://openlibrary.org/books/OL1850361M/Governing_the_commons |Design Principles for Governing the Commons]] to have a community-owned and updated version for use in current project setups including [[wp>FLOSS]] development with voluntary contributors in collectives and cooperatives.  This is OpenScrum.  
  
 ===== Version ===== ===== Version =====
-14th February 2026 - OpenScrum v2.0.1+18th February 2026 - OpenScrum v2.0.2
  
 ===== OpenScrum Definition ===== ===== OpenScrum Definition =====
Line 16: Line 18:
  
   * The owners order the work for a complex problem into an issue list.   * The owners order the work for a complex problem into an issue list.
-  * A team of contributors turns a selection of the work into a build during a milestone. +  * A team of contributors turns a selection of the work into a build during a sprint. 
-  * The contributors and the community members inspect the results and adjust for the next milestone.+  * The contributors and the community members inspect the results and adjust for the next sprint.
   * Repeat   * Repeat
  
Line 46: Line 48:
  
 Adaptation becomes more difficult when the people involved are not empowered or self-managing. A Scrum Team is expected to adapt the moment it learns anything new through inspection. Adaptation becomes more difficult when the people involved are not empowered or self-managing. A Scrum Team is expected to adapt the moment it learns anything new through inspection.
- 
-<code> 
-  The following is a direct copy of the Scrum Guide or has not been adapted yet: 
-</code> 
  
 ===== OpenScrum Values ===== ===== OpenScrum Values =====
Line 89: Line 87:
 Cooperatives work for the sustainable development of their communities through policies approved by their members. Cooperatives work for the sustainable development of their communities through policies approved by their members.
  
-==== Design Principles for Governing the Commons ==== +<code> 
- +  From here is a direct copy of the Scrum Guide or has not been adapted yet: 
-From //Governing the Commons//, Ostrom, Elinor (1990) +</code>
- +
- 1.   Clearly defined boundaries +
- 2.   Congruence between appropriation, provision rules and local conditions +
- 3.   Collective-choice arrangements +
- 4.   Monitoring +
- 5.   Graduated sanctions +
- 6.   Conflict-resolution mechanisms +
- 7.   Minimal recognition of rights to organize +
- +
-For commons that are parts of larger systems: +
- +
- 8.   Nested enterprises: The design principles for commons need to appear in multiple layers of the larger systems. +
  
 <code> <code>
  • teams/rebased_scrum.1771183030.txt.gz
  • Last modified: 2026/02/15 20:17
  • by dennmans