-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wg-platforms community blog: PEMM Leveling Workshop Case Study #753
Open
TGPSKI
wants to merge
1
commit into
cncf:main
Choose a base branch
from
TGPSKI:tpate-add-pemm-workshop-case-study-red-hat
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+66
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
66 changes: 66 additions & 0 deletions
66
website/content/en/blog/2024-09-18-platform-engineering-maturity-model-workshop.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
--- | ||
title: 'Accelerating Platform Engineering Value: Introducing PEMM Leveling Workshop' | ||
slug: platform-engineering-maturity-model-workshop | ||
date: 2024-09-18 20:04:00 -0700 | ||
author: Tyler Pate | ||
categories: | ||
- Article | ||
tags: | ||
- WG Platforms | ||
- Community Contribution | ||
--- | ||
|
||
As organizations navigate the complexities of modern technology infrastructure, **platform engineering** has emerged as a critical discipline for driving efficiency and scalability. With the [**Platform Engineering Maturity Model (PEMM)**](https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/) being a relatively new concept, leveraging it effectively positions practitioners at the forefront of industry innovation. At the same time, our community continues to develop best practices for linking PEMM concepts to business value. Connecting our investment into PEMM methodology with clear business value is critical for buy-in with decision makers. | ||
|
||
In this case study, I'll demonstrate how I used the PEMM as tool to unify multiple teams following an internal restructuring at Red Hat. I'll demonstrate additional potential for the Platform Engineering Maturity Model (PEMM) to add value, connect teams, and align leadership with common terminology and goals. | ||
|
||
* [PEMM Leveling Workshop Template: Google Docs](https://docs.google.com/document/d/1h_ZoX89ScG0m10VxT5p7wwLlHMnVEv6RmrygvSLsnh4/edit?usp=sharing) | ||
|
||
## Workshop | ||
|
||
### Objectives | ||
|
||
* **Align Leadership with Platform Goals**: Secure buy-in from decision-makers for adopting the `platform-as-a-product` mindset and implementing PEMM within Red Hat. | ||
* **Unify Diverse Teams**: Bring together platform teams under a common framework to enhance collaboration and streamline efforts post-restructuring. | ||
* **Establish a Shared Vocabulary**: Develop a common language among teams to improve communication and understanding of platform engineering practices. | ||
|
||
### Highlights | ||
|
||
**Context**: Following an internal restructuring at Red Hat, there was a need to align newly co-located platform teams and ensure that leadership was on board with industry trends, best practices, and termninology. | ||
|
||
**Duration**: A focused, one-hour interactive session, designed for maximum impact. | ||
|
||
**Preparation**: Teams independently assessed their maturity levels using a 1-4 scale, documenting their insights in a shared [Google Doc](https://docs.google.com/document/d/1h_ZoX89ScG0m10VxT5p7wwLlHMnVEv6RmrygvSLsnh4/edit?usp=sharing) prior to the workshop. This self-assessment aimed to foster genuine reflection and prepare teams for in-depth discussions. | ||
|
||
**Ranking System**: I chose to use a numeric scale for ranking, as opposed to the headline text for each level in the PEMM. This small change brought simplicity and effectiveness in facilitating meaningful dialogue, and was especially beneficial for participants new to the PEMM concept. | ||
|
||
### Key Strategies | ||
|
||
#### Independent Self-Assessment | ||
|
||
By encouraging teams to self-evaluate their maturity levels, I enabled engagement and cross-team understanding, rather than enforcing strict adherence to PEMM criteria. | ||
|
||
#### Collaborative and Inclsuive Format | ||
|
||
During the workshop, team leaders presented their PEMM rankings and provided context and reasoning for their assesment. Teams were called on individually for each PEMM category, giving all participants a voice and room to be heard. This approach promoted transparency and built trust across teams. This strategy avoided a drawn-out review of all five categories at once, allowing for focused discussion and feedback. | ||
|
||
##### Interactive Dialogue | ||
|
||
An open Q&A session after each PEMM ranking presentaion allowed participants to exchange ideas, ask probing questions, and offer constructive feedback, fostering a collaborative environment. | ||
|
||
### Outcomes | ||
|
||
* **Accelerated Value Delivery**: I enabled efficient implementation of platform initiatives and effective communication with stakeholders by unifying platform teams under the PEMM framework. | ||
* **Leadership Alignment**: I secured buy-in from decision-makers, aligning them with our platform engineering objectives and communicating the value of the `platform-as-a-product` approach. | ||
* **Enhanced Collaboration**: We established a shared vocabulary and understanding among teams, breaking down silos and promoting synergy in our post-restructuring operations. | ||
* **Educational Impact**: We successfully introduced PEMM concepts to team members unfamiliar with the framework, expanding our organization's collective expertise in the cutting-edge aspects of platform engineering. | ||
|
||
## Next Steps | ||
|
||
Building on the workshop's success, I conducted a follow-up session focused on **platform user personas**. This session aimed to deepen our understanding of user needs and align our platform capabilities accordingly, further accelerating value delivery and solidifying `platform-as-a-product` mindset with key stakeholders. | ||
|
||
I will be writing a follow-up blog on the **PEMM User Personas Workshop** to share insights and outcomes from this session, with associated templates and resources for the community. | ||
|
||
## Conclusion | ||
|
||
This case study illustrates the significant impact that embracing new frameworks like PEMM can have on an organization. By applying PEMM during a critical restructuring phase, I not only aligned our platform teams and leadership but also positioned internal Red Hat teams at the forefront of platform engineering thought and practice. The workshop demonstrates how organizations can utilize the Platform Engineering Maturity Model to drive change, new approaches, and innovation in their platform engineering practices. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can remove this from here since we're already linking to the same document under the Highlights->Preparation section.