While re-reading, I felt like this topic was introduced in a bit of a confusing way for me.
This note captures & groups together what I find myself citing from the topic.
Context
Maturity/Capability are mental models. They are also operational models. They include frameworks and heuristics used for decision making around engineering projects.
Just to be clear
❌ Maturity model = bad
✅ Capabilities model = good
1. Maturity Model
Fixed mindset, focused on getting to a mature state then declaring yourself “done” with a journey.
It usually sounds like “we’ve achieved CI/CD & don’t plan in investing in that again”
Same energy as the guy who says “I finished FIFA” or other sports games💀
Very prescriptive & linear:
Every team’s told to use the exactly sets of technologies and process.
There’s tradeoffs here, giving teams absolute freedom can very quickly become inefficient. Defining sensible defaults is a good place to start.
1a. Vanity metrics
Measuring vanity metrics tends to be common when operating in a maturity models environment.
Quite a number of friends have asked me for books that touch on the topic of how Artificial Intelligence & Machine Learning are impacting our daily lives, and I always recommend the same bunch of books, just making them public now.