co-cddo/cloudmaturity

Cloud Maturity Model and Assessment tool.

cloudmaturity's Issues

Self-Deployment Support and Guidance

Assumption is that eventually this will be deployed to GitHub Pages or similar. Not sure that everyone on GitHub looking to use this will want to enter data about their companies on a public site. Some probably want to deploy their own instance.

Pathway for Contributing

@chrisns I love that you're building this - will be so useful for facilitating cloud migration conversations!

Not sure of where you want to take this in the long run, but I imagine there are some things that you / core team might want to steer (e.g. questions to ask, centrally-agreed framework for migration, etc) but there may be some issues that others in the community can help with (UI components, bugfixes, case-studies / contact deets for improvements in each section).

Some suggestions:

• contributing.md guidance
• contributor-friendly issues
• vision
• roadmap
• perhaps a CDDO github project

Essentially a way to know the intent, and contribute to the direction.

Tracking of Progress over Time

As a: technology leader
I want: some way to track what has changed with cloud maturity over time
So that: I can easily see where we are progressing well, and where we aren't

At the moment, this tool provides a snapshot of cloud maturity at any given time, but there is no way to store that and compare against future results. May be as simple as a spreadsheet export, Just curious on your thoughts on how to track this!