PROPOSAL
!!! This is a shared scratch pad for the definition of the term POC !!!
Definition - What does Proof of Concept (POC) mean?
A proof of concept (POC) is a demonstration, the purpose of which is to verify that certain concepts or theories have the potential for real-world application. POC is therefore a prototype that is designed to determine feasibility, but does not represent deliverables.
Proof of concept is also known as proof of principle.
POC should be equivalent to "Tech Preview"
Guidelines
- Every POC has a named sponsor for the feature whom acts as spokesperson at all checkpoints/meetings
- POC feature development is second priority to committed feature/tech debt development efforts.
- Dependencies on other projects for POC functionality should be clearly communicated as POC development
- POC (only) related defects cannot block the release
- POC release notes should include details of functionality available, known issues, and known limitations/incomplete features
- Integration and test resources are primarily for the committed features and should not be used for POC until primary functionality is complete OR blocked
- POC issues are not the primary topic at PTL or TSC meetings
- POC development can waive "product completeness" requirements - like S3P, Localization/I18N
- POC development must comply with license scans and vulnerability fixes
- POC may be promoted to fully supported feature prior to the end of the release with approval of the TSC
- POC features may be withdrawn from the release at any time with notification to the TSC from the sponsor