Versions Compared

Key

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

...

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

DateProjectDeliverable
1/8/18VNF RequirmentsDraft M1 Project Plan available on VNFRQTS Project Wiki
1/18/18VNF RequirmentsONAP Beijing M1 Milestone - planning process complete
2/12/18VNF RequirmentsONAP Beijing M2 Milestone - functionality freeze
3/8/18VNF RequirmentsONAP Beijing M3 Milestone - API data model freeze
3/29/18VNF RequirmentsONAP Beijing M4 Milestone - code freeze
4/19/18VNF RequirmentsONAP Beijing RC0 Milestone
5/3/18VNF RequirmentsONAP Beijing RC1 Milestone
5/17/18VNF RequirmentsONAP Beijing RC2 Milestone
5/24/18VNF RequirmentsONAP Beijing Signoff Milestone

Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

8
DateProjectDeliverableDeliverable
1/16/18Sprint 1 start

Draft M1 Project Plan available on VNFRQTS Project Wiki

M1 checklisy available before ONAP Beijing M1 Milestone - planning process complete 1/18

1/30/18VNF RequirmentsDraft M1 Project Plan available on VNFRQTS Project Wiki
1/18/18VNF RequirmentsONAP Beijing M1 Milestone
2/12/18VNF RequirmentsONAP Beijing M2 Milestone
3/8/18VNF RequirmentsONAP Beijing M3 Milestone
3/29/18VNF RequirmentsONAP Beijing M4 Milestone
4/19/18VNF RequirmentsONAP Beijing RC0 Milestone
5/3/18VNF RequirmentsONAP Beijing RC1 Milestone
5/17/18VNF RequirmentsONAP Beijing RC2 Milestone
5/24/18VNF RequirmentsONAP Beijing Signoff Milestone

Documentation, Training

Sprint 1 complete

Sprint 2 start

Draft structure of Use case and test case Descriptions available before ONAP Beijing M2 Milestone - functionality freeze 2/12

2/13/18

Sprint 2 complete

Sprint 3 start


2/27/18

Sprint 3 complete

Sprint 4 start

before ONAP Beijing M3 Milestone - API data model freeze 3/8
3/13/18

Sprint 4 complete

Sprint 5 start


3/27/18

Sprint 5 complete

Sprint 6 start

before ONAP Beijing M4 Milestone - code freeze 3/29
4/10/18

Sprint 6 complete

Sprint 7 start

Finalize complete drafts before ONAP Beijing RC0 Milestone 4/19
4/24/18

Sprint 7 complete

Sprint 8 start

Bug fixes only prior to RC1 5/3
5/8/18

Sprint 8 complete

Sprint 9 start

Bug fixes only prior to RC2 5/17
5/22/18

Sprint 9 complete

Bug fixes only prior to signoff 5/24

Documentation, Training

  • VNF Guidelines  
    • component lead - Wenyao Guan (China Mobile) 
    • Forward looking guidance
  • VNF Requirements
    • component lead - Herb Patten (AT&T)
    • VNF Conformance requirements
  • VNF  Use Cases
    • component lead - TBD
    • tutorial
  • VNF Test Case Descriptions
    • component lead - TBD
    • Description of how to test the VNF Requirements
  • Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
  • Highlight the team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...
Note
titleNote

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

...

Each project must edit its project table available at Project FOSS. This vnfrqts project is a documentation project using the LF toolchain coordinated via the documentation project. 


Charter Compliance

The project team comply with the ONAP Charter.