[Pattern Draft] governance-based-project-setup #699
Conversation
As discussed in Slack previously this adds a new pattern to link our Governance Levels with information on what pre-requisits need to be fulfilled to reach the respective governance level. The pattern looks at several factors: * Knowledge needed by contributors and host team. * General advise on project structure. * Maturity levels that need to be reached. * Relevant patterns.
MaineC
requested review from
lenucksi,
NewMexicoKid,
cewilliams,
spier,
robtuley and
yuhattor
as code owners
MaineC
added
1-initial
|
This pattern resonates. So from an atomic and or reductionist view it makes sense to stand on it's own. It is useful on it's own and many groups would or could benefit. I also see stretch opportunities (taking a step back to an integrated or holistic view) with patterns that I/we (from Dojo Center) have proposed and that are in draft.
Stretch conversations can look orthogonal so I don't mean to necessarily unpack any intersection opportunities here. Given a future professional opportunity as an influencer, director or coach I would consider leveraging the patterns above together. TL/DR Very supportive and appreciative |
|
I fully agree that we need another pattern with a more holistic view to go along with this one. Thanks for your feedback, glad you find it helpful. |
There was a problem hiding this comment.
Thank you @MaineC for pushing your experiences into the open, in this case in the form of patterns!
I am just leaving some initial comments, and will do a more wholistic review at a later point.
Will already commit mini fixes that are purely formatting etc
| @@ -0,0 +1,87 @@ | |||
| ## Title | |||
|
|
|||
| Governance Level Guided Project Setup | |||
There was a problem hiding this comment.
Found that title hard to understand. Need to think about a suggestion for a better one.
There was a problem hiding this comment.
I fully agree - and: naming is hard :)
Hmm. I think I need help brainstorming here.
Something that puts "capabilities" into the title?
What this pattern does is to pull several separate patterns together into a subsystem. I'm sure there is a term for that kind of text. Maybe @kjstol or @NewMexicoKid can provide some information for that?
There was a problem hiding this comment.
Maybe something like "governance level drives maturity needs"?
There was a problem hiding this comment.
We can improve the title later. Maybe once we find further adopters of the pattern.
|
Thanks for the initial review @spier - really appreciate the input on this one. |
|
@spier I believe I addressed your comments. Is there anything left to change before this can be merged? |
spier
changed the title
…ake the link to the other pattern even more explicit (even though this means repetition)
…ty 'Structured' in the future
There was a problem hiding this comment.
@MaineC I have finally had time to fully digest your pattern here.
Only now I have actually understood what the pattern is trying to do, I think :) I have added some explanations at the beginning of the Solution section, describing my understanding if your approach.
I did wonder shortly if the content of this pattern could be merged into the "Governance Levels" pattern itself. Not sure about the pros-cons of this yet.
However as this PR has been sitting idle here for so long already, I suggest to get this merged in our repo, and decide at a later point how we want to proceed with this.
Having this fully integrated into our repo will make it easier to get more eyeballs by other readers on it.
Thank you for documenting your practical InnerSource experiences, and sharing these with us! And sorry that this review took so long
| @@ -0,0 +1,87 @@ | |||
| ## Title | |||
|
|
|||
| Governance Level Guided Project Setup | |||
There was a problem hiding this comment.
We can improve the title later. Maybe once we find further adopters of the pattern.
|
|
||
| The relevant levels of the [maturity model](../2-structured/maturity-model.md) are at least: | ||
|
|
||
| PP-1, DP-1, DC-1, RS-1, ST-1, CF-1, LS-1, OF-2, CB-2, SP-2, PA-2, RW-1, MP-1, SM-1, CL-1, RO-1 |
There was a problem hiding this comment.
It feels impractical for the readers to take the short codes from here, and look them up in the maturity model.
Unfortunately I don't have a better idea yet either. Maybe our publishing tooling (gitbook) has a solution for this. We can look at this again once we aim to get this pattern published in our book.
There was a problem hiding this comment.
I'm also quite unhappy that we can't sort of link out directly. I included the information here because I believe, it's still valuable to have that link to the maturity model steps.
Thanks so much for taking that time! (And: Happy New Year!)
What you added sounds correct!
The reason I didn't do that is the length of the patterns: I wanted to keep Governance Levels very brief and concise so it's easy to read and understand. Also I wanted to keep focus there on the business decision itself without clouding the discussion with implementation details.
Sounds reasonable to me. :)
No worries - glad to see this pattern making progress. |
As discussed in Slack previously this adds a new pattern to link our Governance Levels with information on what pre-requisits need to be fulfilled to reach the respective governance level.
The pattern looks at several factors: