Generalize the maturity model pattern - #536
Conversation
Sorry, something went wrong.
…ity model from the self-assessment of the teams.
rrrutledge
left a comment
There was a problem hiding this comment.
This is great! We need a way to have this idea of the pattern and then specific instances of implementations of the pattern that people can lift and reuse for themselves.
Sorry, something went wrong.
| Teams sharing InnerSource learnings run into misunderstandings as they are not | ||
| aware of their respective level of InnerSource adoption. | ||
| * Teams sharing InnerSource learnings run into misunderstandings as they are not aware of their respective level of InnerSource adoption. | ||
| * Teams believe that "it's all about migrating to a shared software development [forge](https://en.wikipedia.org/wiki/Forge_%28software%29)" (GitLab, GitHub, or Bitbucket being well known examples of such forges). |
There was a problem hiding this comment.
Just remove this line. It's too specific.
Sorry, something went wrong.
There was a problem hiding this comment.
You mean just the line 30, right?
Interestingly the fits the discussion around what qualifies "ThinnerSource" in slack :)
Sorry, something went wrong.
There was a problem hiding this comment.
Yes, line 30 🙂
Sorry, something went wrong.
Co-authored-by: rrrutledge <rrrutledge@users.noreply.github.com>
|
@dicortazar I would love to get your input on the changes to this pattern, given that you were one of the original authors. |
Sorry, something went wrong.
By generalizing the marity model pattern we hope to allow for other orgs to list themselves as adopters of this pattern, even if they may be using a maturity model that is different from the one proposed in this pattern.
At the same time we think that providing a maturity model as part of this pattern has its merits, as it allows readers to understand in greater depth what this goals of this pattern are.
Key changes