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

Compare with Current View Page History

« Previous Version 4 Next »

Agenda:

  1. Assemble/Welcome (5 min) 
#ObjectiveHow AchievedParticipant Preparation requiredAction items out
2Review seed contributions. Participants should understand the general content scope and styles of the seed contributions (15 min)briefly open each of the 6 seed contributions and check the availability of word/ text format versions, check for any expected updates, etc.review the seed contributons prior to the meeting
3Identify the Gaps in EPICs and User Stories. Participants should be comfortable that the EPICs and User Stories reasonably completely represent the work of the project. (15 min)review the list of EPICs and user stories in

[vnfrqts] Release Planning (and JIRA).

Solicit additional EPICs / User Stories and volunteers to document in JIRA

review the JIRA Epics and User Stories prior to the meeting

xxx to create EPIC on yyy

aaa to create user story on bbb

4Review outputs by affected project in ONAP. Participants should be comfortable that the deliverables produced by this project are fit for the purposes of the receiving groups

Discussion with representative of projects identified in project charter as being dependent on VNFRQTS deliverables.

VNF Validation (PTL: Erik Sundelif )

VNF SDK ( PTL: Chris Donley)

VNF SDK ( Models lead: Andy Mayer)

Documentation (PTL: Greg Glover)

Integration (PTL: Helen Chen)


review:

vnfrqts Project charter

vnfrqts Epics

vnfrqts User Stories


5How do we know when we are done for ONAP release A. Participants should be comfortable that the scope of the project for release A meets the needs of Release A feature content from other platform components

Walk through the TSC approved use cases for ONAP release A.

identify corresponding VNF use cases to be fleshed out and who will generate them

review TSC Approved Use casesaaa to create user story on bbb
6How to merge Management Requirements from Open-O and from ECOMP. Participants should be comfortable with the objectives and general process for merging the documents.Discuss structure options for merged management requirements

   7. Any other Business? (5 min) 

  • No labels