From 2a2de794a12c57d461d3dd450e6600b5b4bd5916 Mon Sep 17 00:00:00 2001 From: Daniel Izquierdo Date: Wed, 8 Feb 2017 17:00:54 +0100 Subject: [PATCH 1/7] Add donut: change developers mindset Related to issue #39 --- change-developers-mindset.md | 49 ++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 change-developers-mindset.md diff --git a/change-developers-mindset.md b/change-developers-mindset.md new file mode 100644 index 000000000..64f9f5bbf --- /dev/null +++ b/change-developers-mindset.md @@ -0,0 +1,49 @@ +## Change the developers mindset + +## Context + +* Top-down inner source support +* 3k population of developers +* Middle Management is not supporting inner source +* There's already a succesfull group in the early stages +* Code visibility is product dependent + +## Problem + +* Change developer mindset, it's difficult to push developers to do things. +* Developers are resisting the change, they are in their comfort zone and it's hard to go out. +* Developer organizations maturity is high, so people are used to being in some hierarchy/rules +* Developers are formed in agile, the shift from agile is difficult + +## Forces + +* Manager are previous developers, so they like the way they were promoted and they want to proceed in similar ways +* Manager restrict where developers can spend time on +* Top-down approach to the inner source +* Different teams within the company have to decide to proceed with inner source +* No formal training +* Processes are not clear + +## Sketch (optional) + +## Solution + +* Showing reward/recognition of the developer team +* Formalize training +* Clarify more processes +* Give middle management specific objectives to make inner source succesfull +* Listen to manager complaints and fears and count on them + +## Resulting Context + +* Use of the several projects across the several development teams +* Collaboration within the same developer team (mentorship and so on) + + +## Rationale (optional) + +## Known instances (optional) + +## Status +Pattern Idea / Donut + From 0b0ef0d35f7f80c908d50c38dc17266132be1b46 Mon Sep 17 00:00:00 2001 From: Tim Yao Date: Mon, 13 Mar 2017 08:33:17 -0500 Subject: [PATCH 2/7] Minor grammatical fixes. --- change-developers-mindset.md | 42 ++++++++++++++++++------------------ 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/change-developers-mindset.md b/change-developers-mindset.md index 64f9f5bbf..fcb3cd729 100644 --- a/change-developers-mindset.md +++ b/change-developers-mindset.md @@ -2,42 +2,42 @@ ## Context -* Top-down inner source support -* 3k population of developers -* Middle Management is not supporting inner source -* There's already a succesfull group in the early stages -* Code visibility is product dependent +* Top-down InnerSource support exists. +* 3k population of developers. +* Middle Management is not supporting InnerSource. +* There's already a successful InnerSource group in the early stages. +* Code visibility is product dependent. ## Problem -* Change developer mindset, it's difficult to push developers to do things. -* Developers are resisting the change, they are in their comfort zone and it's hard to go out. -* Developer organizations maturity is high, so people are used to being in some hierarchy/rules +* How do you change developer mindset? It's difficult to push developers to do things. +* Developers are resisting the change, they are in their comfort zone and it's hard to get them to go out of it. +* Developer organization's maturity is high, so people are used to being in some hierarchy/rules. * Developers are formed in agile, the shift from agile is difficult ## Forces -* Manager are previous developers, so they like the way they were promoted and they want to proceed in similar ways -* Manager restrict where developers can spend time on -* Top-down approach to the inner source -* Different teams within the company have to decide to proceed with inner source -* No formal training -* Processes are not clear +* Managers are previous developers, so they like the way they were promoted and they want to proceed in similar ways. +* Managers restrict what developers can spend time on. +* Top-down approach to the InnerSource. +* Different teams within the company have to decide to proceed with InnerSource. +* No formal training. +* Processes are not clear. ## Sketch (optional) ## Solution -* Showing reward/recognition of the developer team -* Formalize training -* Clarify more processes -* Give middle management specific objectives to make inner source succesfull -* Listen to manager complaints and fears and count on them +* Show reward/recognition of the developer team that is engaged in InnerSource. +* Formalize training. +* Clarify more processes. +* Give middle management specific objectives to make InnerSource successful. +* Listen to manager complaints and fears and counter them. ## Resulting Context -* Use of the several projects across the several development teams -* Collaboration within the same developer team (mentorship and so on) +* Use of the software from several InnerSource projects across the several development teams. +* Collaboration within the same developer team (mentorship and so on). ## Rationale (optional) From 868b7c6518e99b94cda1fd0bc0c20898abcf37ee Mon Sep 17 00:00:00 2001 From: Tim Yao Date: Wed, 10 May 2017 19:28:11 -0500 Subject: [PATCH 3/7] Update change-developers-mindset.md Cleaned up the pattern idea --- change-developers-mindset.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/change-developers-mindset.md b/change-developers-mindset.md index fcb3cd729..8a5ab5b38 100644 --- a/change-developers-mindset.md +++ b/change-developers-mindset.md @@ -1,10 +1,11 @@ -## Change the developers mindset +## Title +Change the developers mindset ## Context * Top-down InnerSource support exists. * 3k population of developers. -* Middle Management is not supporting InnerSource. +* Middle management is not supporting InnerSource. * There's already a successful InnerSource group in the early stages. * Code visibility is product dependent. @@ -13,16 +14,16 @@ * How do you change developer mindset? It's difficult to push developers to do things. * Developers are resisting the change, they are in their comfort zone and it's hard to get them to go out of it. * Developer organization's maturity is high, so people are used to being in some hierarchy/rules. -* Developers are formed in agile, the shift from agile is difficult +* Developers are formed in agile, the shift from agile is difficult. ## Forces * Managers are previous developers, so they like the way they were promoted and they want to proceed in similar ways. -* Managers restrict what developers can spend time on. -* Top-down approach to the InnerSource. -* Different teams within the company have to decide to proceed with InnerSource. -* No formal training. -* Processes are not clear. +* Managers restrict what developers can spend time on, perhaps because of KPIs they have to meet and their belief in the best way to meet those. +* The approach to the InnerSource initiative is top down--it is supported by top management. +* Different teams within the company decide whether to proceed with InnerSource. +* No formal training exists. +* Processes are not clearly defined. ## Sketch (optional) @@ -36,14 +37,13 @@ ## Resulting Context -* Use of the software from several InnerSource projects across the several development teams. -* Collaboration within the same developer team (mentorship and so on). - +* Software from several InnerSource projects is used across the several development teams. +* There is improved collaboration within the same developer team (mentorship and so on). ## Rationale (optional) ## Known instances (optional) ## Status -Pattern Idea / Donut +Pattern Idea From 6e981e5b5794691407ec0e9181b7ae6dc4d89065 Mon Sep 17 00:00:00 2001 From: Johannes Tigges Date: Mon, 11 May 2020 16:14:29 +0200 Subject: [PATCH 4/7] Change file name to allow meaningful diff in #63 --- change-developers-mindset.md => change-the-developers-mindset.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename change-developers-mindset.md => change-the-developers-mindset.md (100%) diff --git a/change-developers-mindset.md b/change-the-developers-mindset.md similarity index 100% rename from change-developers-mindset.md rename to change-the-developers-mindset.md From ba33aa61246e0a1abcff8a58dda6785d5b565904 Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 11:48:20 +0100 Subject: [PATCH 5/7] reordered sections to fit Template. Removed most empty sections --- .../change-the-developers-mindset.md | 24 ++++++++++--------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/patterns/1-initial/change-the-developers-mindset.md b/patterns/1-initial/change-the-developers-mindset.md index 8af9ebab8..d4d92baf4 100644 --- a/patterns/1-initial/change-the-developers-mindset.md +++ b/patterns/1-initial/change-the-developers-mindset.md @@ -1,13 +1,10 @@ ## Title + Change the developers mindset -## Context +## Patlet -* Top-down InnerSource support exists. -* 3k population of developers. -* Middle management is not supporting InnerSource. -* There's already a successful InnerSource group in the early stages. -* Code visibility is product dependent. +TBD ## Problem @@ -16,6 +13,14 @@ Change the developers mindset * Developer organization's maturity is high, so people are used to being in some hierarchy/rules. * Developers are formed in agile, the shift from agile is difficult. +## Context + +* Top-down InnerSource support exists. +* 3k population of developers. +* Middle management is not supporting InnerSource. +* There's already a successful InnerSource group in the early stages. +* Code visibility is product dependent. + ## Forces * Managers are previous developers, so they like the way they were promoted and they want to proceed in similar ways. @@ -25,8 +30,6 @@ Change the developers mindset * No formal training exists. * Processes are not clearly defined. -## Sketch (optional) - ## Solution * Show reward/recognition of the developer team that is engaged in InnerSource. @@ -40,12 +43,11 @@ Change the developers mindset * Software from several InnerSource projects is used across the several development teams. * There is improved collaboration within the same developer team (mentorship and so on). -## Rationale (optional) +## Known Instances -## Known instances (optional) +TBD ## Status -Pattern Idea * Initial * Old status: Unproven From 34aa0cd10100b333dfe36de17407dba4b296ccea Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 11:58:40 +0100 Subject: [PATCH 6/7] Point to elaborate comment on PR. Simplify Status. Some woring changes. --- patterns/1-initial/change-the-developers-mindset.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/patterns/1-initial/change-the-developers-mindset.md b/patterns/1-initial/change-the-developers-mindset.md index d4d92baf4..ab4e22518 100644 --- a/patterns/1-initial/change-the-developers-mindset.md +++ b/patterns/1-initial/change-the-developers-mindset.md @@ -11,21 +11,21 @@ TBD * How do you change developer mindset? It's difficult to push developers to do things. * Developers are resisting the change, they are in their comfort zone and it's hard to get them to go out of it. * Developer organization's maturity is high, so people are used to being in some hierarchy/rules. -* Developers are formed in agile, the shift from agile is difficult. +* Developers are formed in Agile, the shift from Agile is difficult. ## Context * Top-down InnerSource support exists. * 3k population of developers. * Middle management is not supporting InnerSource. -* There's already a successful InnerSource group in the early stages. +* There is already a successful InnerSource group in the early stages. * Code visibility is product dependent. ## Forces * Managers are previous developers, so they like the way they were promoted and they want to proceed in similar ways. * Managers restrict what developers can spend time on, perhaps because of KPIs they have to meet and their belief in the best way to meet those. -* The approach to the InnerSource initiative is top down--it is supported by top management. +* The approach to the InnerSource initiative is top down - it is supported by top management. * Different teams within the company decide whether and how to proceed with InnerSource. * No formal training exists. * Processes are not clearly defined. @@ -50,10 +50,7 @@ TBD ## Status * Initial -* Old status: Unproven -* Old status: Pattern Idea ## See Also -This pattern has been moved for discussion at -https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/63 +* For further improvements of this pattern, please als review these [comments from the ISC Fall Summit 2017](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/63#pullrequestreview-67393334). From aefb97091a843590c9dea7523127e742c1b39e6d Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Sat, 6 Feb 2021 12:05:43 +0100 Subject: [PATCH 7/7] Update patterns/1-initial/change-the-developers-mindset.md --- patterns/1-initial/change-the-developers-mindset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/1-initial/change-the-developers-mindset.md b/patterns/1-initial/change-the-developers-mindset.md index ab4e22518..654325cb5 100644 --- a/patterns/1-initial/change-the-developers-mindset.md +++ b/patterns/1-initial/change-the-developers-mindset.md @@ -53,4 +53,4 @@ TBD ## See Also -* For further improvements of this pattern, please als review these [comments from the ISC Fall Summit 2017](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/63#pullrequestreview-67393334). +* For improving this pattern even further, please also review these [comments from the ISC Fall Summit 2017](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/63#pullrequestreview-67393334).