It's important to separate the project lifecycle from the release lifecycle. It usually takes 2+ releases for a project to move from 'incubation' to 'mature'. However, you probably want to have an MVP for each release defined during the planning phase (before the M1 milestone). What is the minimum functionality this project can deliver and still be part of the release? You can add stretch goals in case the team has extra time. In a date-driven release, though, the two levers a project team has are scope and quality, so it helps to understand up front what features/functions can be jettisoned if the team starts to fall behind.
Chris From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com] Sent: Thursday, April 20, 2017 5:12 AM To: Stephen Terrill; SULLIVAN, BRYAN L; Christopher Donley (Chris); onap-tsc at lists.onap.org Cc: Ed Warnicke Subject: RE: Updated TSC Charter On MVP and text in below email from Bryan, Clarification as to what an MVP is as the target for the end of the incubation phase. Believe, that's where we need to some element of Product Management. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill Sent: Thursday, April 20, 2017 12:32 AM To: SULLIVAN, BRYAN L <bs3131 at att.com>; Christopher Donley (Chris) <Christopher.Donley at huawei.com>; onap-tsc at lists.onap.org Cc: Ed Warnicke <eaw at cisco.com> Subject: Re: [onap-tsc] Updated TSC Charter Hi, Thanks for the comments Bryan. On responding comment in the "incubation" and MVP definition and that is on the proposed addition of "That is (or can be) used in a production environment". The use in a "production environment" is also subject to whatever additions and support is required. I can agree that MVP is subject to the same question in that its very subjective. Its not obvious to phrase in a non-subjective way, but we could remove MVP and go with "Project has resources, but is recognized to be in an early stage of development and not generally considered suitable to a production environment." I'm ok with the contributor clarification. Best Regards, Steve. From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L Sent: 19 April 2017 19:12 To: Christopher Donley (Chris) <Christopher.Donley at huawei.com<mailto:Christopher.Donley at huawei.com>>; onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Cc: Ed Warnicke <eaw at cisco.com<mailto:eaw at cisco.com>> Subject: Re: [onap-tsc] Updated TSC Charter Chris, Not sure I can post to the TSC list, but here are some comments in the draft: * Each project will have its own code repositories (one or multiple),... o The concept of an umbrella project may address this, but that's an overhead that should be optional. It may be more effective in some cases for projects just to have multiple repos. * A Contributor is someone who contributes code or other artifacts to a project, and reviews the contributions of others. Contributors are not necessarily from Member companies. o We should encourage and recognize all forms of contribution, especially reviews. IMO contributors may provide *no* code but still contribute valuable advice on architecture, quality, testability, or other contributions of a non-code/artifact nature. * Committer rights for a project are earned via code contribution ... o The potential pool of committers should go beyond just code contribution, given the merit of their other types of contributions * (description of Incubation phase) Project has resources, but is recognized to be in early stages of development, having yet to achieve a MVP (Minimum Viable Product) that is (or can be) used in production environments. o Clarification as to what an MVP is as the target for the end of the incubation phase. * Other editorial items Thanks, Bryan Sullivan | AT&T From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris) Sent: Wednesday, April 19, 2017 8:45 AM To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Cc: Ed Warnicke <eaw at cisco.com<mailto:eaw at cisco.com>> Subject: [onap-tsc] Updated TSC Charter Dear TSC, On behalf of the Charter drafting team, please find attached an updated version of the TSC Charter incorporating your suggestions and feedback from the last review. We have attempted to highlight the open issues that need a decision from the TSC. We are sending this draft with the intention that you review it in preparation for discussion and voting during our next TSC meeting. Chris, Steve, Ed, Lingli, Alla, and Phil ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170420/1558ddd4/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4909 bytes Desc: image001.png URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170420/1558ddd4/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 7337 bytes Desc: image002.jpg URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170420/1558ddd4/attachment-0001.jpg>
