Skip to content
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

Suggestion: Include some "default" / example blueprints in "Recommendations / Scenarios" of Chapter 1 #491

Open
webchick opened this issue Jun 4, 2024 · 1 comment

Comments

@webchick
Copy link
Contributor

webchick commented Jun 4, 2024

There's a part at the end of Chapter 1 that describes recommendations based on real-world scenarios, for example:


An OSPO is established without proper alignment with organizational goals

Recommendation: Align the OSPO with organizational goals by establishing a clear mission, setting measurable objectives, fostering cross-departmental collaboration.


Which... yes, sure, that makes sense, but... HOW? :D

Desired:

"Here are some starter metrics which other OSPOs have had good results with in demonstrating business impact:

  • Foo
  • Bar
  • Baz

These should be customized to your specific organization."

and/or:

"Don't miss Chapter X where we talk all about metrics and measuring OSPO impact."

@webchick
Copy link
Contributor Author

webchick commented Jun 4, 2024

Same deal with Scenarios 2-4:


Scenario #2
An OSPO is seen as a separate silo within the organization

Recommendation: Integrate open source practices into various departments, demonstrating the value that open source brings to achieve shared organizational objectives.


Yepppp... makes sense, but once again, HOW??! :D

Desired:

"Read this (link)case study(/link) by Mega OSPO Inc on how they've managed to resolve this scenario by fooing their bazzes with bars."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant