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 21:35] – small changes to the titles and first paragraphs dennmansteams:rebased_scrum [2026/02/18 16:06] (current) – typos dennmans
Line 7: Line 7:
 ===== 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 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.  +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 48: 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 95: Line 91:
 From //Governing the Commons//, [[https://openlibrary.org/books/OL1850361M/Governing_the_commons | Ostrom, Elinor (1990)]] From //Governing the Commons//, [[https://openlibrary.org/books/OL1850361M/Governing_the_commons | Ostrom, Elinor (1990)]]
  
- 1.   Clearly defined boundaries +  - Clearly defined boundaries 
- 2.   Congruence between appropriation, provision rules and local conditions +  - Congruence between appropriation, provision rules and local conditions 
- 3.   Collective-choice arrangements +  - Collective-choice arrangements 
- 4.   Monitoring +  - Monitoring 
- 5.   Graduated sanctions +  - Graduated sanctions 
- 6.   Conflict-resolution mechanisms +  - Conflict-resolution mechanisms 
- 7.   Minimal recognition of rights to organize+  - Minimal recognition of rights to organize
  
 For commons that are parts of larger systems: 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.+8. Nested enterprises: The design principles for commons need to appear in multiple layers of the larger systems.
  
 +
 +<code>
 +  From here is a direct copy of the Scrum Guide or has not been adapted yet:
 +</code>
  
 <code> <code>
  • teams/rebased_scrum.1771187726.txt.gz
  • Last modified: 2026/02/15 21:35
  • by dennmans