Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

!!! 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

  1. POC feature development is second priority to committed feature/tech debt development efforts. 
  2. Dependencies on other projects for POC functionality should be clearly communicated as POC development
  3. POC (only) related defects cannot block the release
  4. POC release notes should include details of functionality available, known issues, and known limitations
  5. Integration and test resources are primarily for the committed features and should not be used for POC until primary functionality is complete OR blocked
  6. POC issues are not the primary topic at PTL or TSC meetings
  7. POC development can waive "product completeness" requirements - like S3P, Localization/I18N
  8. POC development must comply with license scans and vulnerability fixes
  9. POC may be promoted to fully supported feature prior to the end of the release with approval of the TSC
  • No labels