Open Stack

Jesse - I had interpreted John's comments referring to the aligning of priorities and resources between Nova current priorities, Nova backlog specs and  Product WG user stories. He would like to unhide the hidden influencers (ie. product managers) by having us reflect our priorities and then commit to aligning the resources from our collective companies against the top priorities. Does that work for you?

On the cut-line, I was just trying to be pragmatic. We have a finite set of resources in our team and for this Pilot phase will only be able to do the gaps analysis (what you refer to below as testing to figure out what's missing), cross project coordination and tracking for a limited number of user stories. Maybe that's 3, maybe it's 5, maybe it's more. I think this is our decision based upon what people volunteer for. 

Between our call tomorrow and our time at the Mid-cycle next week, we can talk through the issues and finalize our approach to the next wave of work facing our team.

Thanks
Carol

-----Original Message-----
From: Jesse Cook [mailto:jesse.cook at RACKSPACE.COM] 
Sent: Wednesday, August 12, 2015 5:27 PM
To: Barrett, Carol L; product-wg at lists.openstack.org
Subject: Re: [Product] [OpenStack][Product WG] Next Round of User Story discussion/prioritization



On 8/12/15, 6:02 PM, "Barrett, Carol L" <carol.l.barrett at intel.com> wrote:

>Team - Good working session today! We covered 12 user stories and had 
>good discussion around how to improve/target them. Thanks to everyone!
>The etherpad for the session is here:
>https://etherpad.openstack.org/p/User_Story_Discussion_1
>
>In tomorrow’s session my proposal for our agenda is:
>*       Complete review of the remaining 7+ user stories (some will be
>developed and added tonight)
>*       Identify which user stories we want to combine and owners to
>complete that
>*       Discuss Prioritization Criteria
>o       We had defined 3 criteria and it appears that all/most of our
>user stories are meeting them
>o       So how do we rank them? Where do we draw the cut line for the
>ones we'll focus on for this Pilot cycle?

While in the general case I’m a strong advocate for prioritizing work, I think this is the bit where some care has to be taken to avoid the alienation John spoke of (especially the bit about the cut line).

What I think will be far more effective and useful is not how we prioritize them but how we test them and demonstrate what’s missing. This is extremely valuable to the community. Being able to say what’s missing is one thing, being able to show it in such a way that a dev can make a change and make that test pass is a whole nother level of value.

>*       Prioritize
>*       Discuss Next Steps and any deliverables for our Mid-Cycle work
>
>Meeting Logistics:
>8/13/15, 21:00 - 23:00 UTC
>Voice Bridgeː Access: (888) 875-9370, Bridge: 3; Passcode: 1278598
>Etherpad: https://etherpad.openstack.org/p/User_Story_Discussion_2
>
>Pls send thoughts on the agenda and add comments to the Etherpads, User 
>Stories and Tracker.
>Talk to you tomorrow.
>Carol
>
>_______________________________________________
>Product-wg mailing list
>Product-wg at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg