- 1 OpenStack Product Working Group
- 1.1 Meeting and Communication Information
- 1.2 Ocata Cycle Priorities
- 1.3 Mission
- 1.4 Who we are
- 1.5 Objectives
- 1.6 Methodology
- 1.7 FAQs
- 1.8 Product WG Pilot Phase
- 1.9 Sub-Pages
OpenStack Product Working Group
Meeting and Communication Information
Date, time, and IRC channel: http://eavesdrop.openstack.org/#OpenStack_Product_WG Past IRC meeting logs: http://eavesdrop.openstack.org/meetings/product_working_group/ Etherpad archives: https://etherpad.openstack.org/p/PWG_Archives Subscribe to the User Committee Mailing List Please add [Product] tag in the subject line when sending messages to the User Committee Mailing List Product WG Mailing List Archives (archive of messages sent prior to Jan. 4th, 2017)
Ocata Cycle Priorities
- Establish simplified process for user-story creation, review and analysis to enable all Work Groups/Teams to contribute and enable a wider range of feedback.
- Lead: Shamail Tahir
- Complete the User Story Tracker
- Lead: Jamey
- Support the Community transitions: Redesigned work flow and User Committee expansion
- Lead: Carol
Ocata Midcycle Planning etherpad: https://etherpad.openstack.org/p/MIL-pwg-meetup
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:
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.)
Develop a repeatable, transparent, process for prioritization of user stories; create blueprints/specs (or bug report) associated with the user story on a per-release cycle basis. The team will work within their organizations to fill any necessary resource gaps and create a tracker to track the implementation progress of the user story across projects and multiple releases. The criteria for the process along with the results should be clearly communicated with the community and our end-customers.
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.
The team requires establishing a workflow, identifying stakeholders/partners in the community, providing a means to track progress against user stories, and ensuring routine interlocks with other members/groups in the community due to the wide spectrum of items being worked on concurrently. The Product WG has established sub-teams/roles to divide tasks to ensure quality and timeliness of our collective output.
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 Cross Project Liaisons
OpenStack uses a concept called Cross Project Liaisons to facilitate communications between projects that might require collaboration/coordination with each other. The cross-project liaisons representing a certain team will co-locate with another team to become participating members and serve as the conduit between the two project teams. You can find a list of the Product WG CPLs here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Product_Working_Group
User Story Owners
The User Story Owners are members of the Product WG team who have volunteered to help manage/lead/track a user story from submission to completion. They will also help with the decomposition of the user stories into blueprints/specs, gather resources to aid with authoring/completing blueprints/specs, and work with the CPLs to ensure the "big picture"/objective associated with the user story is being taken into account since user stories will often include multiple "moving parts" in a single release and require tracking across releases.
While user stories are stored/tracked using the openstack-user-stories repo and the specs page. The user story owners maintain a sub-page for each user story to provide information on team meetings and additional artifacts.
OpenStack User Stories Core Members
The members of the openstack-user-stories-core team carefully review all changes proposed to the openstack-user-story repository (which is where the Product WG stores user stories and tracking data). The responsibilities, expectations, and process for membership in the openstack-user-stores-core team can be found here.
Series of Activities per Release
In conclusion, to achieve the various objectives, the Product WG will pursue multiple activities throughout each release. The chart below attempts to map these activities on top of the standard 6-month release schedule for OpenStack releases.
The Product WG has compiled a list of Frequently Asked Questions.
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 draft workflow for user story planning and prioritization
☑ Present initial multi-release roadmap at the Liberty summit
☑ Review user stories being pursued during the pilot with the Cross Project team [meeting log]
✅ 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
|User Stories Landing Page||Multi-Release Roadmap Sub-Team|
|Capacity Management User Story||Life-cycle Management for VMs|
|On-boarding Legacy Apps User Story||Rolling Upgrades User Story|
|Core Team Page||OpenStack User Stories Generated Page|