ProductTeam/Development Proposals
Contents
User Stories
The Product Working Group discusses proposals, both, internally and externally using user stories. The user stories are created using a standard template which is located on the Product WG Repository. The process for selecting user stories that the team pursues is depicted in figure 1.1. The primary source for information on Product WG user stories is our specs page, the user story sub-pages listed here are meant to provide additional information about the team that is working on the user story (members, meeting times, etc.) and supporting artifacts for the user story that do not fit the defined template.
This taxonomy shows more details on the mapping on product WG mapping to agile terminology.
User Story Workflow
The workflow covers both the creation and prioritization of the user story. Anyone is allowed to post a user story to the draft folder in the repository.
Possible Statuses for User Stories
Draft: This is a user story that has been submitted but has not gone through additional reviews beyond fulfilling the requirements of the user story template (e.g. all mandatory sections are filled out properly).
Proposed: This user story has an assigned user story owner and is ready for feedback from the community. The user story is socialized with the cross-project team once it reaches this status and the community can leave comments using gerrit.
Tracked: This is a user story that has gone through the review phase and has one or more technical resources helping conduct gap analysis and build implementation plan (which includes component level blueprints and socialization with project teams).
Conditions For Movement of User Story
Draft -> Proposed: Requires that the required fields for the user story are filled out properly, a user story owner, and any modifications needed to enhance/clarify the user story are completed.
Proposed -> Tracked: One or more organizations have assigned technical resources to perform gap analysis and work with Product WG Cross-Project Liaisons to propose component-level blueprints needed to implement the user story.
