Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add Agile InnerSource Dojo pattern #695

Open
wants to merge 29 commits into
base: main
Choose a base branch
from
Open
Changes from 25 commits
Commits
Show all changes
29 commits
Select commit Hold shift + click to select a range
97d082d
feat: Add InnerSource Dojo pattern
michael-basil Jun 13, 2024
e665491
feat: Add Voluntary Contribution and Prioritized Mentorship principles
michael-basil Jun 13, 2024
f15fdc2
fix: Typo
michael-basil Jun 13, 2024
e263c42
feat: Add Dojo Consortium
michael-basil Jun 13, 2024
f37c786
feat: Touch up
michael-basil Jun 13, 2024
dd011d7
Update innersource-dojo.md
billwestfall Jun 14, 2024
03305dd
refactor: Review with Nick Basil
michael-basil Jun 14, 2024
f773733
Update innersource-dojo.md
jimmanzzullo Jun 17, 2024
b6e44f1
feat: Add Maturity Model relation
michael-basil Jun 20, 2024
b56cbbf
characterize dojo function
aphor Jun 20, 2024
9c162f9
Merge pull request #1 from dojo-center/innersource-dojo_jeremy
michael-basil Jun 20, 2024
3622ca8
admit authorship
aphor Jun 21, 2024
3b1adc3
Update innersource-dojo.md
anuolu Jun 21, 2024
d6540bc
feat: Infuse Agile into the name
michael-basil Jun 21, 2024
9ac1370
fix: Typo
michael-basil Jun 21, 2024
b3e557a
fix: Test
michael-basil Jun 22, 2024
9454748
Merge pull request #4 from dojo-center/anuolu-patch-1
michael-basil Jun 22, 2024
b34c501
fix: Rename to infuse Agile
michael-basil Jun 22, 2024
da46986
fix: Typo
michael-basil Jun 23, 2024
7a68291
fix: Status start at Initial
michael-basil Jun 23, 2024
5d7b709
feat: Add Core Team and Trusted Committer patterns
michael-basil Jun 24, 2024
30d2015
feat: Add SAP Samples and Dojo Center models
michael-basil Jun 27, 2024
f8e5570
refactor: Iterate on Patlet and Problem
michael-basil Jun 28, 2024
ae73cd2
refactor: Cleanup forces and themes
michael-basil Jun 28, 2024
f12e8d0
fix:Typo
michael-basil Jul 2, 2024
e03f97a
fix: Typo
michael-basil Jul 2, 2024
35b44d8
fix: Typo
michael-basil Jul 5, 2024
3dd7d83
fix: Relative links to patterns
michael-basil Jul 5, 2024
3ece4c5
fix: Cleanup DevOps inclusion
michael-basil Jul 8, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
76 changes: 76 additions & 0 deletions patterns/2-structured/agile-innersource-dojo.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
## Title

Agile InnerSource Dojo

## Patlet

Organizations struggle with siloed knowledge and slow adaptation. Agile environments left unchecked can lead to redundant codebases feeding the desire to over-standardized practices that ultimately stifle innovation. Implementing an Agile InnerSource Dojo creates a structured learning environment which fosters improved collaboration, reduced waste, improved efficiency and promotes generative culture, supporting DevOps and scaled change initiatives.

## Problem

Agile projects, especially those using Scrum and promoting autonomy and self-organization, can unintentionally lead to silos. Similar teams across the organization may create non-uniform and redundant codebases, resulting in inefficiencies and waste. This can also lead to a compulsion to over-standardize practices, which stifles innovation, particularly in DevOps and other transformational initiatives. Symptoms include low engagement in InnerSource projects, inefficient knowledge transfer and difficulty in scaling Agile practices.

## Context

A dojo is a didactic participatory practice group, predicated on traditional martial arts dojo practices. It creates opportunities for participants to learn by doing (embodied learning), under supervision and guidance of others who have prior experience. Agile InnerSource Dojos are designed for organizations aiming to harness the power of InnerSource to increase potentials for transformation and innovation. This setting brings individuals from various backgrounds, expertise and roles to collaboratively work on shared goals, ensuring the learning journeys remain relevant, beneficial and peer supported.

## Forces

* **Lack of Awareness**: Many Agile practitioners are unaware of InnerSource methodologies and vice versa.
* **Diversity of Participants**: The Dojo involves individuals with different backgrounds, expertise and expectations.
* **Need for Safe Spaces**: Participants must feel safe to share their insights and challenges.
* **Continuous Engagement**: Ongoing participation is crucial for maintaining the Dojo's momentum and impact.
* **Knowledge Sharing**: Effective methods for sharing knowledge and best practices are essential.

## Solutions

Adopt a strategic approach to create and sustain an Agile InnerSource Dojo, focusing on clear objectives, inclusive participation and continuous improvement. This can be achieved through the following parallel efforts:

* **Define the Purpose**: Clearly articulate the Dojo's purpose and goals, ensuring alignment with broader organizational objectives.
* **Establish Social Conventions**: Develop and communicate social conventions that promote respect, inclusivity and open dialogue. Encourage members to embrace and evolve these guidelines to create a safe and supportive environment.

Check failure on line 30 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [ISC.Spelling] Did you really mean 'inclusivity'? Raw Output: {"message": "[ISC.Spelling] Did you really mean 'inclusivity'?", "location": {"path": "patterns/2-structured/agile-innersource-dojo.md", "range": {"start": {"line": 30, "column": 102}}}, "severity": "ERROR"}
* **Facilitate Regular Meetings**: Schedule regular meetings to maintain engagement and momentum. Use these sessions for open discussions, sharing insights and addressing challenges. Meetings are open for unpacking issues, with goals set by attendees.
* **Rotate Leadership**: Encourage shared leadership by rotating the facilitation role among members. This helps distribute responsibility and fosters a sense of connection.
* **Use Collaborative Tools**: Utilize tools like Jitsi Meet, Slack and GitHub for communication and documentation. Insights can be optionally shared on social channels, ensuring privacy.

Check failure on line 33 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [ISC.Spelling] Did you really mean 'Jitsi'? Raw Output: {"message": "[ISC.Spelling] Did you really mean 'Jitsi'?", "location": {"path": "patterns/2-structured/agile-innersource-dojo.md", "range": {"start": {"line": 33, "column": 51}}}, "severity": "ERROR"}
* **Encourage Voluntary Code Contribution**: Foster an environment where contributions are voluntary, allowing individuals to work on what interests them and aligning with their passions.
* **Prioritized Mentorship**: Implement a mentorship structure with Sensei (teachers) providing guidance and Senpai (senior students) supporting newer members. This dual-layer mentorship enhances skill development and community cohesion.
* **Foster a Culture of Continuous Improvement**: Regularly seek feedback to identify improvement areas, refining the Dojo's conditioning and activities accordingly.

## Resulting Context

Embracing this pattern helps InnerSource programs become vibrant, effective and sustainable. Participants will feel more connected and engaged, leading to increased knowledge sharing, innovation and collective growth.

## Related Patterns

* [Dedicated Community Leader](https://patterns.innersourcecommons.org/p/dedicated-community-leader)
michael-basil marked this conversation as resolved.
Show resolved Hide resolved
* [Core Team](https://patterns.innersourcecommons.org/p/core-team)
* [Trusted Committer](https://patterns.innersourcecommons.org/p/trusted-committer)
* [Maturity Model](https://patterns.innersourcecommons.org/p/maturity-model)
* [Circle Communities](https://patterns.innersourcecommons.org/p/circle-communities)

## Known Instances

* [InnerSource Dojo from SAP](https://www.youtube.com/watch?v=fXoVm5iTSCc)
* [SAP Samples Dojo Model (live demo) - Mindset | Agile | InnerSource](https://sap-samples.github.io/dojo)
* [SAP Samples Dojo Model (source) - Mindset | Agile | InnerSource](https://github.com/SAP-samples/dojo)
* [SAP Samples GitHub Pull Analyzer](https://github.com/SAP-samples/github-pull-analyzer)
* [Microsoft DevOps Dojo](https://innersourcecommons.org/stories/microsoft)
* [Dojo Center](https://dojo.center)
* [Source](https://github.com/dojo-center/dojo-center.github.io)

Check failure on line 58 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / lint

Trailing spaces [Expected: 0 or 2; Actual: 1]
michael-basil marked this conversation as resolved.
Show resolved Hide resolved

## Status

* Initial

## Authors

* [Michael Basil](https://www.linkedin.com/in/michaelrbasil)
* [Bill Westfall](https://www.linkedin.com/in/bill-westfall-3268494)

Check failure on line 67 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [ISC.Spelling] Did you really mean 'Westfall'? Raw Output: {"message": "[ISC.Spelling] Did you really mean 'Westfall'?", "location": {"path": "patterns/2-structured/agile-innersource-dojo.md", "range": {"start": {"line": 67, "column": 9}}}, "severity": "ERROR"}
* [Jim Manzzullo](https://www.linkedin.com/in/jimmanzzullo)

Check failure on line 68 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [ISC.Spelling] Did you really mean 'Manzzullo'? Raw Output: {"message": "[ISC.Spelling] Did you really mean 'Manzzullo'?", "location": {"path": "patterns/2-structured/agile-innersource-dojo.md", "range": {"start": {"line": 68, "column": 8}}}, "severity": "ERROR"}
* [Jeremy McMillan](https://www.linkedin.com/in/jeremymcm)
* [AnuOlu Balogun](https://www.linkedin.com/in/anuolu)

Check failure on line 70 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [ISC.Spelling] Did you really mean 'Balogun'? Raw Output: {"message": "[ISC.Spelling] Did you really mean 'Balogun'?", "location": {"path": "patterns/2-structured/agile-innersource-dojo.md", "range": {"start": {"line": 70, "column": 11}}}, "severity": "ERROR"}

## Acknowledgements

Check failure on line 72 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [ISC.Spelling] Did you really mean 'Acknowledgements'? Raw Output: {"message": "[ISC.Spelling] Did you really mean 'Acknowledgements'?", "location": {"path": "patterns/2-structured/agile-innersource-dojo.md", "range": {"start": {"line": 72, "column": 4}}}, "severity": "ERROR"}

* [Ryan Uttech](https://www.linkedin.com/in/ryanuttech)

Check failure on line 74 in patterns/2-structured/agile-innersource-dojo.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [ISC.Spelling] Did you really mean 'Uttech'? Raw Output: {"message": "[ISC.Spelling] Did you really mean 'Uttech'?", "location": {"path": "patterns/2-structured/agile-innersource-dojo.md", "range": {"start": {"line": 74, "column": 9}}}, "severity": "ERROR"}
* [Guilherme Dellagustin](https://www.linkedin.com/in/dellagustin)
* [Dojo Consortium](https://dojoconsortium.org)
Loading