I second this. Offering the right questions depending on the different stages of the evolution of a project could be a major contribution that this group can bring into successful planning of governance readiness.
I would be interested in working this a bit more out. Some initial ideas:
- We could differentiate different “starts”: For example a project that begins with less than 5 persons and without monetary compensation in mind (at least in the beginning) might have different governance concepts to think about than a well-funded start-up with more then 20 employees or similar.
- From these different starts we could define different levels that can be reached during the evolution. Some metrics that come to mind to define these levels are a growing importance (usage / number of installations / critical applications etc.), the growth of “community” (users, contributions, third-party usages etc.), growth of business, growing dependencies etc.
Without having too many details already, a matrix that offers different levels for different starts and the most important questions regarding governance readiness for each level/status would be something abstract but also pretty useful I can imagine.