Home
›
Public Product Organizations
Six pillars of successful public product organizations
1
Governance
Crucial to sustainable collaborative development is a community-endorsed model for how decisions are made about the core product and its future.
Good governance allows participating public entities to trust that their invested resources and policy commitments in a specific public product will continue to serve their constituents.
2
Community of practice
A dynamic ecosystem of implementers, developers, and stakeholders that sustains a public product needs active tending and orchestration.
A public product organization must provide contexts for communication, scheduling, and knowledge sharing resources to help the community thrive.
3
Codebase stewardship
The beating heart of a dynamic public product is its codebase. A clear process for open technical collaboration through continuous integration enables the entire community to power the engine that moves the product forward.
Codebase stewards should look to the Standard for Public Code for guidance on best practices.
4
Financial model
Perhaps the most common reason public product organizations fail is due to the lack of a sustainable financial model.
Public funding, philanthropic grants, membership dues, vendor certification, and service contracts enable public product organizations to fund their activities and product development.
5
Awareness & communications
As the growth of a public product community distributes the costs and responsibilities of development and maintenance across a larger set of contributors, increasing awareness of the product’s availability, adaptability, and successful deployment is key to the ecosystem’s success.
6
Organizational structure
Public product organizations can take many forms, and will have different vehicles in different jurisdictions, but a well defined organizational structure that spells out the different processes, roles and how they relate to each other is critical for successful long-term collaboration.
Examples of public code
Foundation for
Public CodePublic Code
Product Orgs
The Standard
About
Support us
Six pillars of successful public product organizations
1
Governance
Crucial to sustainable collaborative development is a community-endorsed model for how decisions are made about the core product and its future.
Good governance allows participating public entities to trust that their invested resources and policy commitments in a specific public product will continue to serve their constituents.
2
Community of practice
A dynamic ecosystem of implementers, developers, and stakeholders that sustains a public product needs active tending and orchestration.
A public product organization must provide contexts for communication, scheduling, and knowledge sharing resources to help the community thrive.
3
Codebase stewardship
The beating heart of a dynamic public product is its codebase. A clear process for open technical collaboration through continuous integration enables the entire community to power the engine that moves the product forward.
Codebase stewards should look to the Standard for Public Code for guidance on best practices.
4
Financial model
Perhaps the most common reason public product organizations fail is due to the lack of a sustainable financial model.
Public funding, philanthropic grants, membership dues, vendor certification, and service contracts enable public product organizations to fund their activities and product development.
5
Awareness & communications
As the growth of a public product community distributes the costs and responsibilities of development and maintenance across a larger set of contributors, increasing awareness of the product’s availability, adaptability, and successful deployment is key to the ecosystem’s success.
6
Organizational structure
Public product organizations can take many forms, and will have different vehicles in different jurisdictions, but a well defined organizational structure that spells out the different processes, roles and how they relate to each other is critical for successful long-term collaboration.
Examples of public code
Foundation for Public Code
Public Code
Product Orgs
The Standard
About
Support us
Six pillars of successful public product organizations
1
Governance
Crucial to sustainable collaborative development is a community-endorsed model for how decisions are made about the core product and its future.
Good governance allows participating public entities to trust that their invested resources and policy commitments in a specific public product will continue to serve their constituents.
2
Community of practice
A dynamic ecosystem of implementers, developers, and stakeholders that sustains a public product needs active tending and orchestration.
A public product organization must provide contexts for communication, scheduling, and knowledge sharing resources to help the community thrive.
3
Codebase stewardship
The beating heart of a dynamic public product is its codebase. A clear process for open technical collaboration through continuous integration enables the entire community to power the engine that moves the product forward.
Codebase stewards should look to the Standard for Public Code for guidance on best practices.
4
Financial model
Perhaps the most common reason public product organizations fail is due to the lack of a sustainable financial model.
Public funding, philanthropic grants, membership dues, vendor certification, and service contracts enable public product organizations to fund their activities and product development.
5
Awareness & communications
As the growth of a public product community distributes the costs and responsibilities of development and maintenance across a larger set of contributors, increasing awareness of the product’s availability, adaptability, and successful deployment is key to the ecosystem’s success.
6
Organizational structure
Public product organizations can take many forms, and will have different vehicles in different jurisdictions, but a well defined organizational structure that spells out the different processes, roles and how they relate to each other is critical for successful long-term collaboration.
Examples of public code