Jump to: navigation, search


Revision as of 21:42, 28 September 2015 by Kaizen (talk | contribs) (Product WG Cross Project Liaisons)

OpenStack Product Working Group


new IRC meetings https://wiki.openstack.org/wiki/Meetings/product-team
past IRC meetings http://eavesdrop.openstack.org/meetings/product_working_group/2015/
F2F Aug2015 https://etherpad.openstack.org/p/productwg-liberty-midcycle-meetup  
F2F Feb2015 https://etherpad.openstack.org/p/kilo-product-management-midcycle
F2F Sep2014 https://etherpad.openstack.org/p/paris-product-meeting
Subscribe to the Mailing List
Mailing List Archives


We will support the OpenStack developer community in their desire to build open-source cloud software that reflects the needs of the various markets adopting the platform by creating user stories that reflect the voice of the end-users/operators. These user stories will focus on items that have traditionally been harder to implement based on the need for cross-project coordination and significant development time (spanning multiple releases). Finally, the team will also focus on sharing regular updates on directional insights for the platform (gathered from key members from the development community) in the form of a multi-release roadmap. The ultimate mission is to create a focus on areas that are high-impact and remove barriers to adoption/operation/scale of OpenStack clouds.

Who we are

The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

The group aims to **improve the quality of the delivery process, the delivered product, and the product experience for operators and end users**.


The objectives of this working group, based on the mission, are therefore to:

Collect Feedback and Aggregate Requirements

This group will collect (and aggregate) user, admin, customer, and operator requirements. The group should also interface with and gather data from, the other groups collecting requirements for specific verticals, markets, or user segments (e.g. Operators, Win The Enterprise, Personas, NFV/Telco, End Users/App Developers, etc.)

User Story Planning and Prioritization

Develop a repeatable, transparent, process for prioritization of user stories along with creating/tracking components level blueprints/specs associated with the user story on a per-release cycle basis. The criteria for the process along with the results should be clearly communicated with the community and our end-customers.

Multi-release Roadmap

Generate a multi-release roadmap based on the aggregated data and resulting themes/requirements. The roadmap will be socialized, transparently, to community stakeholders for agreement and approval. After a roadmap has been established/approved, the OpenStack community will be notified of the results, the drivers for the decision, and its impact over multiple releases to consumers (and developers) of the platform.


Due to the large number of work-items/objectives the team requires establishing a workflow, identifying stakeholders/partners, providing a means to track progress against user stories, and ensuring routine interlocks with other members/groups in the community. The Product WG has established sub-teams/roles to divide tasks to ensure timely completion of our objectives.

Sub-Teams / Roles

Roadmap Release Team

The roadmap release team consists of CPLs and other members of the Product WG. This team has a dedicated sub-page which includes more information.

Product WG Pilot Phase

This section covers key items that we will work on to integrate the Product team with other teams; PTLs, TC, and other User Committee working groups.

☑ Form a rough draft workflow for user story planning and prioritization
☑ Present initial multi-release roadmap at the Liberty summit
☑ Run through pilot user story list with the Cross Project team
✅ Conduct gaps analysis, partner with developers, and present specs/blueprints in project meetings
✅ Build user story tracker and share with community
✅ Engage in operator and design summit sessions to gather and share feedback, respectively
✅ At the Tokyo summit, present the multi-release direction for L through N releases