Good question. I consider the product manager as the business owner of the service. The one defining the business requirements; performance, delays, cost, end service experience, scale, etc. The use case subcommittee will work with the product manager to solution the service given the platform. E.g., What VNFs, data flow, additional Microservices required given current release, features, etc. I believe OpenStack has a separation of the two as well.
At the moment, we do not have a product manager, and this subcommittee should play both roles. We can determine within the TSC whether we can just have one group or separate the two functions. It is always best to have a product manager outside the TSC with that experience. The question is whether we want to make that investment for R1. Mazin On May 29, 2017, at 4:38 PM, Stephen Terrill <[email protected]<mailto:[email protected]>> wrote: Hi Mazin, Earlier there was mention of an “product managmenet” type group related to the use cases, does this replace that? BR, Steve From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: 26 May 2017 19:38 To: onap-tsc <[email protected]<mailto:[email protected]>> Subject: [onap-tsc] Use case subcommittee Thank you to Alla, I have now posted a framework for the use case subcommittee on the wiki page. Your feedback is appreciated. I will advise the TSC next week to vote to formally establish this subcommittee. We will then do self-nomination for a lead. Mazin https://wiki.onap.org/display/DW/Usecase+subcommittee<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Usecase-2Bsubcommittee&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=EYARrhMWPGKM4AVy86AkvDRtORuqanUGIILDIsTe5Sg&s=bSksVVh6kz3KnZLCwU685h3ZVYssLwtpxFJ3lXg10VM&e=>
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
