[Nicolas Fränkel posted the link to proggit today] There are two initiatives that spring to mind (and I'm sure I've come across more, but can't recall them right now).
1. Make a README - https://www.makeareadme.com/ 2. Keep A Changelog - http://keepachangelog.com/ *I have a feeling there are things to pick out of those, that are maturity-model centric, and worth adding to the APMM. * Generally, I like this initiative. Sorry I'm a couple of years late to the party! My first proper job was in 1989, and I was told of the CMM <https://en.wikipedia.org/wiki/Capability_Maturity_Model> in week one. Of course, as a dev org we were not ranked anywhere on it and didn't fit anyway. CMMI <https://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration> came some years later with the same realization for the company I was in at the time. By 2001 or so, CMMI had Agile aspects retrofitted Agile (it was claimed). We would gradually see other less prominent maturity models come into being, and none at all would rule the industry. Perhaps thankfully. Instead I think we worry about methodologies. SAFe <http://www.scaledagileframework.com/> and LeSS <https://less.works/> worry me, and I mourn the fact that there feels like there is less XP going on now than there was in the early 2000's. I digress... -ph
