Hi, Alla – based on your suggestion on the call today I uploaded the draft use case selection criteria from my email to the wiki: https://wiki.onap.org/display/DW/Use+case+goals+and+selection+criteria
I already added a criteria of ‘impact on core development’ based on Oliver’s comments below. Community – please feel free to contribute to this page. Ranny. From: [email protected] [mailto:[email protected]] On Behalf Of SPATSCHECK, OLIVER (OLIVER) Sent: Monday, August 21, 2017 9:05 AM To: Vladimir Yanover (vyanover) <[email protected]>; Jason Hunt <[email protected]>; Alla Goldner <[email protected]> Cc: [email protected] Subject: Re: [onap-tsc] R2 use cases planning Just to be clear it’s development resources – people writing actual code. Let me also try to separate resources a bit: 1. There are core development resources. People which write, integrate and test code which is part of the platform. 2. There are developers which work on particular use cases (e.g. building VNFs, configuring ONAP, … ) but are not directly involved in the platform development. 3. There are architects/planers/coordinators supporting 1. + 2. To work of technical debt we have to protect 1.). 2.) is somewhat self regulating. If somebody wants a particular use case s/he usually provides 2.) but typically still expects the community to support 1.) which is where the problem starts. Generally 3.) can come up with good ideas at a much faster pace than 1.) can handle so 3.) is rarely a bottleneck. (I never had a project where there was a shortage of good ideas.) So unless we see a huge influx of new 1.) for Beijing that is what we need to manage carefully. So use cases which do not require any 1.) work can be done now by anybody. E.g. if you can do a 5G use cases without involvement from 1.) who is stopping you? Just do it! That’s the self serve concept Mazin mentioned. However, use cases which require lots of 1.) work will just add rather then remove technical dept. Hope that helps! Oliver p.s. FYI good and entertaining books on that topic are “The Phoenix Project” and “Creativity Inc.” From: <[email protected]<mailto:[email protected]>> on behalf of "Vladimir Yanover (vyanover)" <[email protected]<mailto:[email protected]>> Date: Friday, August 18, 2017 at 5:42 AM To: Jason Hunt <[email protected]<mailto:[email protected]>>, Alla Goldner <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] R2 use cases planning what is this resource that should be managed
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
