Open Stack

The current workflow seems fine to me and looks like it does represents the stages as proposed?

https://wiki.openstack.org/wiki/ProductTeam/User_Stories#User_Story_Workflow



Current workflow:

1.       Proposed User Story

1.1.    New user story is submitted as a patch to repo  (gerrit-status: review)

1.1.1. Template validated, mandatory sections filled (gerrit-status: review)

1.1.2. Concept discussed on gerrit (gerrit-status: review)

1.1.3. Concept validated by user-story-owner and reviewer/core (gerrit-status: merged)

1.1.4. Initial JSON file created (available on User Story Tracker)

1.2.    Changes to existing user story is submitted as a single patch per changes to repo (gerrit-status: review)

1.2.1. Changes discussed on gerrit (gerrit-status: review)

1.2.2. Changes validated by owner and reviewer (gerrit-status: merged)

1.2.3. JSON file updated

2.       Gap and Overlap Analysis

2.1.    User-story-owner schedule meeting with technical SME and CPSL

2.2.    Prioritize features/requirements

2.3.    Identify features/requirements that requires new blueprint/spec

2.3.1. Work with SME/developer to propose and develop new blueprint/spec

2.4.    Identify existing related blueprint/spec

2.5.    JSON file updated with links to blueprint/spec for each features/requirements

2.6.    Communicate blueprint/spec with project PTL/Core

2.7.    In case of “new project”, direct to TC discussion for next step.

3.       User story tracking

3.1.    User-story-owner monitor the progress (this may cross multiple releases)

3.2.    All related blueprint/spec are tracked by the User Story Tracker

3.3.    User story is “done” when all blueprint/spec are merged.



With reference to previous email:

1.       User Story defined: This is covered in current workflow “1 Proposed User Story”

2.       User Story prepared: This is covered in current workflow “2 Gap analysis – 2.1 to 2.4”

3.       User Story ready: This is covered in current workflow “2 Gap analysis – 2.5 to 2.7”

4.       User Story implemented: This is covered in current workflow “3 User story tracking”.





-----Original Message-----
From: Arkady.Kanevsky at dell.com [mailto:Arkady.Kanevsky at dell.com]
Sent: Wednesday, November 16, 2016 1:20 PM
To: Barrett, Carol L <carol.l.barrett at intel.com>; PChadwick at suse.com; product-wg at lists.openstack.org; user-committee at lists.openstack.org
Subject: Re: [Product] Definition of Done discussion from 11/14 Team Meeting



Carol,

Implementation been accepted means that all specs and blueprints that we created for a user story have been approved by projects and appear on their list.



Agree with the rest. The amount of time and effort it will take to create new project is much much more than create and drive specs and blueprints for existing projects.

Thanks,

Arkady



-----Original Message-----

From: Barrett, Carol L [mailto:carol.l.barrett at intel.com]

Sent: Wednesday, November 16, 2016 3:01 PM

To: Kanevsky, Arkady <Arkady_Kanevsky at DELL.com<mailto:Arkady_Kanevsky at DELL.com>>; PChadwick at suse.com<mailto:PChadwick at suse.com>; product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>

Subject: RE: Definition of Done discussion from 11/14 Team Meeting



Arkady - What is the action that demonstrates the Implementation plan has been accepted?



I think for a User Story to move through the stages will take multiple releases - regardless on how we split it up.



The TC has jurisdiction over new projects.



Carol



-----Original Message-----

From: Arkady.Kanevsky at dell.com<mailto:Arkady.Kanevsky at dell.com> [mailto:Arkady.Kanevsky at dell.com]

Sent: Wednesday, November 16, 2016 9:29 AM

To: PChadwick at suse.com<mailto:PChadwick at suse.com>; product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>

Subject: Re: [Product] Definition of Done discussion from 11/14 Team Meeting



Suggest we split middle one into two:

2. User Story Prepared - Implementation plan has been established, gap

      analysis performed and accepted; all projects impacted notified/created



   3. User Story Ready - Implementation plan has been accepted, projects/specs/blueprints created and json file updated.





Two reasons. One, if we need to create a new project we need to bring it to the board.

That will take more than one release.

Two, it may take several releases before projects accept specs and blueprints.

Thus, we are in the state where user story is defined but not ready for lengthy period of time.



Thanks,

Arkady



-----Original Message-----

From: Peter Chadwick [mailto:PChadwick at suse.com]

Sent: Monday, November 14, 2016 4:11 PM

To: product-wg at lists.openstack.org<mailto:product-wg at lists.openstack.org>; user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>

Subject: [Product] Definition of Done discussion from 11/14 Team Meeting



Team - During today's meeting as a follow on to Barcelona, we entered into a (suprisingly) lively discussion around establishing a "definition of done" for user stories. Among the issues that were raised was whether the PWG considers a user story done when we provide it to the development teams or when the required deliverables are in the product.



The current consensus is that there are three stages that we need to

follow:



   1. User Story Defined - The user story is Complete & Merged into Repo,

      json file created, sent notice of the user story to other WGs and

      merged their comments

   2. User Story Ready - Implementation plan has been established, gap

      analysis performed, specs/blueprints created and json file updated

   3. User Story Implemented - Code is released that enables someone to

      achieve the user story



Pete



--

Pete Chadwick

Director of Product Management

Cloud and Systems Management

SUSE

pchadwick at suse.com<mailto:pchadwick at suse.com>

(M) +1.617.281.2847



www.suse.com<http://www.suse.com>

_______________________________________________

Product-wg mailing list

Product-wg at lists.openstack.org<mailto:Product-wg at lists.openstack.org>

http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg

_______________________________________________

Product-wg mailing list

Product-wg at lists.openstack.org<mailto:Product-wg at lists.openstack.org>

http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg

_______________________________________________

Product-wg mailing list

Product-wg at lists.openstack.org<mailto:Product-wg at lists.openstack.org>

http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20161117/21970b9c/attachment-0001.html>