Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Candidate requirement proposals will be frozen on October 1st, 2020.

These requirements will be prioritized by the TSC to realistically fit within the Honolulu Release by xx

The Release Scope should be finalized during the M1 Release Planning milestone on xx January 11th, 2020.

Note:  we will no longer be using a Confluence table to track requirements. More information here.

TSC Prioritization (Ranking)

  • RANK #1 – TSC Must Have – Mandatory for the release
  • RANK #2 – Continuity  - Items continued from previous releases
  • RANK #3  – Special GO - quick wins, fully covered by involved companies
  • RANK #4 – PTL Go – items that PTLs is OK to include since team has bandwidth
  • RANK #5 – NO GO OR Not yet Reviewed by TSC – items not approved for various reasons

T-Shirt Size

New Cadence Terminology

  • Use case: High level feature that ONAP is supposed to support. Require Arch review, Req review, Impacted PTL review, all has to be GO from all the PTLs.
  • Feature: Functional change that touches multiple components (formely Functional REQuirement). Require Arch review, Req review, Impacted PTL review, all has to be GO from all the PTLs.
  • Spec: Functional change that is touching only a single project (formely Functional REQuirement). Require PTL to decide GO/NO GO, single component impact.
  • Best Practice: Design pattern recognized by the community. Must be followed by the new code associated to new container(s). The best practice owners to present their best practice to the PTLs and then to the TSC to review/to approve as best practice.
  • Global requirementBest Practice that must be applied to whole code base during a particular release (formely called TSC MUST HAVE). The best practice owners to present their approved best practices to the PTLs and then to the TSC to review/to approve as GR at M1.
  • POCPOC definition - Developer Wiki - Confluence (onap.org)
  • XS - <4 Man/Weeks;
  • S - ~6 Man/Weeks;
  • M - ~8 Man/Weeks;
  • L - ~12 Man/Weeks;
  • XL - > 12 Man/Weeks.

Honolulu Use Cases

Jira
serverONAP JIRA
columnskey,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2 /3 scorecard,m2/3 approval,m4 scorecard,m4 approvalapproval,m3 approval,status
maximumIssues1000
jqlQueryfilter=12442
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Honolulu Features

Jira
serverONAP JIRA
columnskeyREQ-456

...

,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 approval,m2 approval,m3 approval,status
maximumIssues1000
jqlQueryfilter=12472
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Honolulu Specs

Jira
serverONAP JIRA
columnskey,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2 /3 scorecard,m2/3 approval,m4 scorecard,m4 approvalapproval,m3 approval,status
maximumIssues1000
jqlQueryfilter=12441 12469
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Honolulu

...

 Best Practices Candidates

Jira
serverONAP JIRA
columnskey,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2 /3 scorecard,m2/3 approval,m4 scorecard,m4 approvalapproval,m3 approval,status
maximumIssues1000
jqlQueryfilter=12439 12470
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Honolulu

...

 Global Requirements

Jira
serverONAP JIRA
columnskey,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2 /3 scorecard,m2/3 approval,m4 scorecard,m4 approvalapproval,m3 approval,status
maximumIssues1000
jqlQueryfilter=12471
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Honolulu PoC

Jira
serverONAP JIRA
columnskey,summary,assignee,arch review,tsc priority,scope status,t-shirt size,status
maximumIssues1000
jqlQueryfilter=12440
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...