Skip to content

pattern/change-developers-mindset #63

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.

Sign up for GitHub

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

Merged
spier merged 9 commits into from
Feb 6, 2021
Merged

pattern/change-developers-mindset #63

Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
2a2de79
Add donut: change developers mindset
dicortazar Feb 8, 2017
0b0ef0d
Minor grammatical fixes.
NewMexicoKid Mar 13, 2017
868b7c6
Update change-developers-mindset.md
NewMexicoKid May 11, 2017
6e981e5
Change file name to allow meaningful diff in #63
lenucksi May 11, 2020
7d7c637
Merge branch 'master' into pattern/change-developers-mindset
lenucksi May 11, 2020
8321ee2
Merge remote-tracking branch 'origin/master' into pattern/change-deve…
spier Feb 6, 2021
ba33aa6
reordered sections to fit Template. Removed most empty sections
spier Feb 6, 2021
34aa0cd
Point to elaborate comment on PR. Simplify Status. Some woring changes.
spier Feb 6, 2021
aefb970
Update patterns/1-initial/change-the-developers-mindset.md
spier Feb 6, 2021
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
57 changes: 26 additions & 31 deletions patterns/1-initial/change-the-developers-mindset.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,54 +8,49 @@ TBD

## 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
* 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.

## Context

* Top-down inner source support
* 3k population of developers
* Middle Management is not supporting inner source
* There's already a successful 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 is already a successful InnerSource group in the early stages.
* Code visibility is product dependent.

## 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)
* 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.
* Different teams within the company decide whether and how to proceed with InnerSource.
* No formal training exists.
* Processes are not clearly defined.

## Solution

* Showing reward/recognition of the developer team
* Formalize training
* Clarify more processes
* Give middle management specific objectives to make inner source successful
* 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)
* 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
## 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 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).