Open corbinpa opened 4 months ago
Thanks so much for opening this @corbinpa! It was great to speak with you and the other collaborators in Paris about the ideas here.
I imagine this type of publication will take on a similar lifecycle to the maturity model itself in that it will start with a skeleton and grow through dedicated working sessions both async and sync calls.
Since we are still early days with all this so some things we still want to determine from the group are:
Looking forward to working with you on this!
I find this really interesting! I hope I understand this correctly but this reminds me of the FinOps model (that I have mentioned numerous times on the Slack channel because I really like how well-designed their framework is!) that they mention the Capabilities mapped to each of the Maturity stage in which that people can take their Assessment tool to know the Maturity level of their org/team in each according Capability. So does the DORA quickcheck. Let me know if I can be of any help on this one!
We are currently looking for the first round of feedback to the tool, which focuses primarily on the format. Please review and add comments directly to the shared document that is posted here: https://docs.google.com/document/d/1PDGq3lAuqNVEWi_BSZcf9fZp6TIeWEUXqoDGmgNCWGE/edit#heading=h.kt3w0dglyxwn
This is being discussed on the 6/11/24 Platforms WG meeting at the :45 mark (need to find recording)
Thanks @corbinpa for sharing, this is an interesting topic. I've a question about the term Risk.
In my experience when I do an assessment about risks I'm used to add also probability, impacts and mitigation actions. In that case the risk is "just" one: the failure of the Platform Engineering initiative.
What do you think to change the name Risk in Fitness Assessment? Something similar to Fitness functions in software dev? https://www.thoughtworks.com/insights/articles/fitness-function-driven-development
@giulioroggero thanks for the feedback! I agree the term risk may not be the correct one, but haven't landed on an alternative yet. I'm not sure that the outcome is simply failure of the plaform initiative, rather maybe has some of the other characteristics you described (probability, impact and mitigation). In my sampling so far, what I have noticed is that the characterization as a risk to the initiative so far seems to inspire some level of action. While it is useful to know where you are from a maturity perspective, the more interesting bit is about where you are going (chart course/journey). The tool should help you think about what workstreams are needed to mature. As an example, an organization has a platform initiative without a product manager (and therefore no product orientation). This may be viewed as a risk to the initiative and depending on the needs or business priorities of the organization, an area where they may need to prioritize more investment. In that case, they may need to know the benefits of the product manager (justification), common responsibilities, necessary skills, etc.
Contribution Description
Create a tool that enables organizations to assess platform maturity based on the existing Platform Maturity Model. The tool will help organizations measure their relative risk as it relates to their platform initiative, with the aim to provide repeatable and prescriptive guidance to mature. The tool will be loosely modeled after the AWS Well Architected Framework, a survey based format, allowing for self-guided or consultative engagement.
Related Working Group (WG)
Platforms
Contribution type
Other
Why TAG App Delivery?
This fits in the TAG because it will enable organizations to measure maturity and improve App Delivery capabilities leveraging a Platform Engineering-based approach.
Related projects/technologies
This project will also align to some of the work we are doing with the CNOE open source initiative. https://cnoe.io/
Affiliation disclosure
No response
Additional collaborators
@abangser @nimakaviani @jessesanford @vsethi
Additional information
https://docs.google.com/document/d/1PDGq3lAuqNVEWi_BSZcf9fZp6TIeWEUXqoDGmgNCWGE/edit#heading=h.kt3w0dglyxwn