[spier]

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 the goals of this pattern more easily.

Key changes

• rewrite Patlet into the 2 sentence form (1 problem + 1 solution)
• Generalize the Solution section. Separate the definition of the maturity model from the self-assessment of the teams.
• Emphasize that an org that adopts this pattern should review the maturity model and adapt it to their needs, before asking teams to do the self-assessment.
• Formatting Forces, Context, and Resulting Context as list, to allow for easier checking

[rrrutledge]

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.

[spier]

@dicortazar I would love to get your input on the changes to this pattern, given that you were one of the original authors.

[spier]

@rrrutledge if you end up working on this in the InnerSource Working Group meeting, I believe the last fix that this PR needs is some content to be added here, and one thorough end-to-end review.

As for the other PR #538 that was also modifying the same pattern:
I am opting to close #538 and add the improvement in a new PR once this PR here is merged. (I may try to merge in the changes automatically but I am expecting that it would end up with too many merge conflicts as both PRs were open for so long)

[jeffabailey]

@jritten does IBM have an example of a maturity model?

[spier]

Thank you for your help with this @jeffabailey and @rrrutledge. I needed that push to get it over the finish line :)

The updated version is now live (you might have to force-refresh. gitbook sometimes does that):
https://patterns.innersourcecommons.org/p/maturity-model