Mission Statement
Characteristics of a good mission statement (according to the internet) 
- Succinct
- Memorable
- Distinctive
- Has Longevity
- Motivating
Some Industry Examples
"Our mission is to organize the world's information and make it universally accessible and useful." – Google
"Bring inspiration and innovation to every athlete* in the world. *If you have a body you are an athlete." – Nike
"We strive to make the world healthier and more sustainable through innovation." – Phillips
"To give shoppers the most compelling shopping experience possible." – Nordstrom
'To reinvent how people share knowledge, tell stories, and inspire their audiences to act." – Prezi
"To put people at the center of enterprise software." – Workday
"To build the world's most convenient, secure, cost-effective payment solutions." – Paypal
'To connect the world's professionals and make them more productive and successful." – LinkedIn
"Our mission is to unlock the potential of human creativity — by giving a million creative artists the opportunity to live off their art and billions of fans the opportunity to enjoy and be inspired by it." – Spotify
Brainstorming for Our Mission Statement
"Potato" value to be communicated:
- What does "potato" bring to the table?
- What is the owrk output we chose to bring together
- Predictability and efficiency are important to high level execs
- From CNTT exec interviews
- Speed of development
- Speed and Efficiency of Deployment
- Cost savings
- Need to capture end result we hope to achieve as well as talking about journey and collective collaboration.
- Needs to be about business value
Current OPNFV value prop: "OPNFV is a project and community for Communication Service Providers (CSPs) and their supply chains focused on network transformation and collaboration to continuously improve the efficiency and predictability of consuming and deploying NFV infrastructure, VNFs, and CNFs. OPNFV does this by iterating through implementation of toolsets, automation, verification, conformance, and performance, aligned with normalized architectures, and enabling the community to drive down cost and time to revenue for network services."
Possible Drafts (feel free to edit, comment, or add your own)
"Potato" empowers the global communications industry to deploy applications and infrastructure quickly, reliably, and securely.
"Potato" exists to serve the infrastructure needs of the global communications industry through architecture alignment, integration, automated testing, and conformance programs. We power the telco cloud.
"Potato" defines, integrates, deploys, and tests the infrastructure and applications necessary for next-generation communication services.
"Potato" improves the quality and agility for on-boarding network services through architecture alignment, integration and deployment, test automation, and conformance.
"We exist to enable the telecom industry to transition to cloud with respect to our infra and applications. We do this by listening to our stakeholders, creating projects that enable them and making conformance programs."
"We exist to enable the Telco cloud ecosystem to collaboratively design and deliver new reference architectures, tools and verification programs that will dramatically reduce the complexity and cost required to deploy and operationalize cloud infrastructure and services for the world's communications network." (could also end with and services for the 5G economy."
Scope
Current OPNFV Scope statement; The scope of the Project includes software development under an OSI-approved open source license supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source software project.
Possible new one: The scope of the Project includes both software development under an OSI-approved open source license and reference documentation, requirements, and specifications under <creative commons> in order to support the mission. These include release documentation, architecture and requirements documents, testing, integration, and the creation of other artifacts that aid in the development, deployment, operation, or adoption of the open source project.
Possible deeper dive statements to drive the formulation of the full value prop
Also possible to add these to the scope statement
When we define value prop, should consider the types of work we do that isn't release artifact-based.
Note that this is taken from the OPNFV 2.0 work; need to integration anything missing from CNTT
(a) Fostering close collaboration of Communication Service Providers (CSPs) and their supply chain to integrate and build tests, tools, and components for NFV infrastructure, VNFs and CNFs which realize the stated outcomes of this mission,
(b) iterating on developing an integrated, tested, and certified open software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,
(c) contributing changes to and influencing upstream projects leveraging the reference infrastructure,
(d) building new open source components within the reference infrastructure where needed,
(e) leveraging open implementations to drive an open standards and open-source-based ecosystem for NFV solutions,
(f) supporting and maintaining the strategic framework of the Project through the technologies made available by the organization to make the Reference Infrastructure testing, certification, and deployment a success.