From 1b59f73dc4f2292490537504fadfcbcb85f89517 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sun, 22 May 2022 23:11:10 +0200 Subject: [PATCH 1/8] Adding first draft of InnerSource Operational Model as proposed in #367 --- patterns/1-initial/operational-model.md | 69 +++++++++++++++++++++++++ 1 file changed, 69 insertions(+) create mode 100644 patterns/1-initial/operational-model.md diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md new file mode 100644 index 000000000..fbd788802 --- /dev/null +++ b/patterns/1-initial/operational-model.md @@ -0,0 +1,69 @@ +## Title + +InnerSource Operational Model + +## Patlet + +InnerSource is key across all of the software production chain. This includes from idea to delivery to customer. This pattern defines the software development life cycle from an InnerSource perspective. + +## Problem + +InnerSource is typically focused on letting developers work together. There are several patterns focused on specific roles as the Trusted Committer or from a more organization level as the Review Committee. However, it is still not clear how all of this works together. + +This pattern aims at providing an overview to management and Chief level of how the software life cycle may be in a more InnerSource way with the goal of having a place where InnerSource principles may apply to the several people involved: from Product Owners to Contributors. + +This may be seen as well as the glue for other patterns willing to make sense from a development lifecycle perspective. + +## Story (optional) + +## Context + +The content here is often tied to the applicability of the pattern for other readers: "Do I have this same particular situation?" + +The problem initially exists at the management level where the several business units are defining their needs, tuning the product, and suggesting next steps. A general overview of this process and key moments in the chain where they can influence (e.g., POs discussions) are part of this. + +## Forces + +As the software production chain involves roles with different goals, this way of working has to be part of everyone involved. Business related people as Product Owners may be reluctant to move into a more collaborative and transparent way of producing software. And this may happen with others as well. + +## Sketch (optional) + +The following is an example of a tentative pattern solution related to this. Existing patterns are now part of this discussion for the software development life cycle. + +![OperationalModelForInnerSource](https://user-images.githubusercontent.com/469119/142229499-e05c60e8-0e8f-4f24-9578-ca05ba4cdab0.png) + +## Solutions + +The proposed solution is a simplified version of a Software Development Lifecycle. This pattern works on three main areas for the software development life cycle that are: + +a) Inception where the idea is discussed and specified (e.g., as user story), +b) Build where the developer collaboration takes place with other developers, where the user story is translated into code, and +c) usage as the moment in time the software is producing value at the final end users even in other business units or departments. + +These three main areas should at the same time comply with the InnerSource principles (transparency, collaboration, community, etc.). + +## Resulting Context + +The resulting context is that the corporation has defined and is using an operational model to work in a more transparent and collaborative way. This model can be later extended to other projects within the corporation. + +This model is useful as well to compare to other existing models in the company, and check how InnerSource this is. For further reference please check the Maturity Model Pattern. + +If applied, this model brings more transparency to any of the decision making process at the company, and it is clear to others the end-to-end process to build software. + +## Rationale (optional) + +## Known Instances (optional) + +## Status + +* Initial status + +## Author(s) + +* Igor Zubiaurre +* Daniel Izquierdo Cortázar + + +## Acknowledgements (optional) + +## Alias (optional) From 59972b4715029fb950434e9b0a9362a5df53dab6 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sun, 22 May 2022 23:15:04 +0200 Subject: [PATCH 2/8] Fixing linter issue --- patterns/1-initial/operational-model.md | 1 - 1 file changed, 1 deletion(-) diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md index fbd788802..20177bfc0 100644 --- a/patterns/1-initial/operational-model.md +++ b/patterns/1-initial/operational-model.md @@ -63,7 +63,6 @@ If applied, this model brings more transparency to any of the decision making pr * Igor Zubiaurre * Daniel Izquierdo Cortázar - ## Acknowledgements (optional) ## Alias (optional) From f64e1fc72b928857e74532d3a45dfe4dde3d2a7c Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sun, 22 May 2022 23:23:54 +0200 Subject: [PATCH 3/8] Turn into list formatting that markdown understands --- patterns/1-initial/operational-model.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md index 20177bfc0..2e5ea6f6b 100644 --- a/patterns/1-initial/operational-model.md +++ b/patterns/1-initial/operational-model.md @@ -36,9 +36,9 @@ The following is an example of a tentative pattern solution related to this. Exi The proposed solution is a simplified version of a Software Development Lifecycle. This pattern works on three main areas for the software development life cycle that are: -a) Inception where the idea is discussed and specified (e.g., as user story), -b) Build where the developer collaboration takes place with other developers, where the user story is translated into code, and -c) usage as the moment in time the software is producing value at the final end users even in other business units or departments. +1. Inception where the idea is discussed and specified (e.g., as user story), +2. Build where the developer collaboration takes place with other developers, where the user story is translated into code, and +3. Usage as the moment in time the software is producing value at the final end users even in other business units or departments. These three main areas should at the same time comply with the InnerSource principles (transparency, collaboration, community, etc.). From 0a8097ee9d168d385b4025421fbba255c0180c37 Mon Sep 17 00:00:00 2001 From: Daniel Izquierdo Cortazar Date: Mon, 28 Nov 2022 16:37:07 +0100 Subject: [PATCH 4/8] Update operational-model.md Update pattern according to @NewMexicoKid comments. Thanks! --- patterns/1-initial/operational-model.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md index 2e5ea6f6b..1612a31b2 100644 --- a/patterns/1-initial/operational-model.md +++ b/patterns/1-initial/operational-model.md @@ -1,6 +1,6 @@ ## Title -InnerSource Operational Model +An InnerSource Lifecycle Model ## Patlet @@ -10,21 +10,24 @@ InnerSource is key across all of the software production chain. This includes fr InnerSource is typically focused on letting developers work together. There are several patterns focused on specific roles as the Trusted Committer or from a more organization level as the Review Committee. However, it is still not clear how all of this works together. -This pattern aims at providing an overview to management and Chief level of how the software life cycle may be in a more InnerSource way with the goal of having a place where InnerSource principles may apply to the several people involved: from Product Owners to Contributors. +This pattern aims at providing an overview to management and Chief level of how the software life cycle may be managed in a more InnerSource way with the goal of having a place where InnerSource principles may apply to the several people involved: from Product Owners to Contributors. -This may be seen as well as the glue for other patterns willing to make sense from a development lifecycle perspective. +This may help provide a helpful framework for connecting patterns to help practitioners make better sense of InnerSource from a development lifecycle perspective. ## Story (optional) ## Context -The content here is often tied to the applicability of the pattern for other readers: "Do I have this same particular situation?" +Visitors to InnerSource patterns may often wonder about the applicability of a given pattern to their own situation. The problem initially exists at the management level where the several business units are defining their needs, tuning the product, and suggesting next steps. A general overview of this process and key moments in the chain where they can influence (e.g., POs discussions) are part of this. +As InnerSource brings a more transparent and collaborative way of working, all existing processes at any level should move into that direction. How to create paths for collaboration across silos and how this software lifecycle looks like. + ## Forces -As the software production chain involves roles with different goals, this way of working has to be part of everyone involved. Business related people as Product Owners may be reluctant to move into a more collaborative and transparent way of producing software. And this may happen with others as well. +As the software production chain involves roles with different goals, the InnerSource way of working has to be taken up by everyone involved in the software production chain. For example, business related people as Product Owners may be reluctant to move into a more collaborative and transparent way of producing software. And this reluctance may occur with other roles as well. + ## Sketch (optional) From 2ea3c7877c3c5cf6b772c17925e2245e8cb3387f Mon Sep 17 00:00:00 2001 From: Daniel Izquierdo Cortazar Date: Mon, 28 Nov 2022 18:41:06 +0100 Subject: [PATCH 5/8] Update operational-model.md Remove 1 empty line to comply with format rules --- patterns/1-initial/operational-model.md | 1 - 1 file changed, 1 deletion(-) diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md index 1612a31b2..17540c73d 100644 --- a/patterns/1-initial/operational-model.md +++ b/patterns/1-initial/operational-model.md @@ -28,7 +28,6 @@ As InnerSource brings a more transparent and collaborative way of working, all e As the software production chain involves roles with different goals, the InnerSource way of working has to be taken up by everyone involved in the software production chain. For example, business related people as Product Owners may be reluctant to move into a more collaborative and transparent way of producing software. And this reluctance may occur with other roles as well. - ## Sketch (optional) The following is an example of a tentative pattern solution related to this. Existing patterns are now part of this discussion for the software development life cycle. From bec23b2fe70e7f48e800c2cb70daab79f52691d7 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sun, 5 Jan 2025 11:24:49 +0100 Subject: [PATCH 6/8] Update patterns/1-initial/operational-model.md --- patterns/1-initial/operational-model.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md index 17540c73d..914d403df 100644 --- a/patterns/1-initial/operational-model.md +++ b/patterns/1-initial/operational-model.md @@ -28,7 +28,7 @@ As InnerSource brings a more transparent and collaborative way of working, all e As the software production chain involves roles with different goals, the InnerSource way of working has to be taken up by everyone involved in the software production chain. For example, business related people as Product Owners may be reluctant to move into a more collaborative and transparent way of producing software. And this reluctance may occur with other roles as well. -## Sketch (optional) +## Sketch The following is an example of a tentative pattern solution related to this. Existing patterns are now part of this discussion for the software development life cycle. From 918451389dc28f380baf921d4686759cf4114ecd Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sun, 5 Jan 2025 11:25:16 +0100 Subject: [PATCH 7/8] Update patterns/1-initial/operational-model.md --- patterns/1-initial/operational-model.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md index 914d403df..fa2739d3c 100644 --- a/patterns/1-initial/operational-model.md +++ b/patterns/1-initial/operational-model.md @@ -14,8 +14,6 @@ This pattern aims at providing an overview to management and Chief level of how This may help provide a helpful framework for connecting patterns to help practitioners make better sense of InnerSource from a development lifecycle perspective. -## Story (optional) - ## Context Visitors to InnerSource patterns may often wonder about the applicability of a given pattern to their own situation. From 23865d9d467a8ae93ab62d1e1d81cf330f455a18 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sun, 5 Jan 2025 11:26:48 +0100 Subject: [PATCH 8/8] Update patterns/1-initial/operational-model.md --- patterns/1-initial/operational-model.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/1-initial/operational-model.md b/patterns/1-initial/operational-model.md index fa2739d3c..7169912b1 100644 --- a/patterns/1-initial/operational-model.md +++ b/patterns/1-initial/operational-model.md @@ -56,7 +56,7 @@ If applied, this model brings more transparency to any of the decision making pr ## Status -* Initial status +* Initial ## Author(s)