PROPOSAL !!! This is a shared scratch pad for the definition of the term POC !!!- following feedback from the ONAP TSC 2019-02-07 the POC definition for Dublin

Proof of concept

Proof of concept (PoC) is a realization of a certain method or idea in order to demonstrate its feasibility,^[1] or a demonstration in principle with the aim of verifying that some concept or theory has practical potential.^{[citation needed]} A proof of concept is usually small and may or may not be complete.

POC is equivalent to "Tech Preview" or "Experimental"

...

1. Every POC has a named sponsor for the feature whom acts as spokesperson at all checkpoints/meetings
2. POC remove POC feature development is second priority to committed feature/tech debt development efforts. 
3. Dependencies on other projects for POC functionality should be clearly communicated as POC development
4. POC (only) related defects cannot block the release
5. POC release notes should include details of functionality available, known issues, and known limitations/incomplete features
6. Integration and test resources are primarily for the committed features and should not be used for POC until either
   1. primary functionality is complete 
   2. testing on the primary functionality is blocked - and cycles are available while blocker gets resolved
7. POC issues are secondary topics at PTL or TSC meetings
8. POC development can waive "product completeness" requirements - like S3P, Localization/I18N
   1. Basic documentation is expected so others can access the feature - full commercial grade documentation is not expected
9. POC development must comply with license scans and vulnerability fixes
10. POC may be promoted to fully supported feature prior to the end of the release with approval of the TSC
11. POC features may be withdrawn from the release at any time with notification to the TSC from the sponsor 
12. POC functionality is targeted for full feature in a specific future release

...