Versions Compared

Key

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

...

  1. Assemble/Welcome (5 min) 


3Develop Sprint definition

#

Objective

How Achieved

Participant Preparation required

Action items out

2Review JIRA Backlog. Participants should be comfortable that they understand the backlog of tasks for our project ( 15 min)

Walk through the JIRA backlog to check for completeness

review:

vnfrqts Project charter

vnfrqts Epics

vnfrqts User Stories

vnfrqts bugs

SPRINT-1 JIRA board


3Review Wiki Updates (15 min)

Robert Reilly to discuss tutorial videos

review

VNFRQTS Contributors and Committers Processes

tutorial videos added


4Develop Sprint 2/3/4 themes. Participants should be comfortable with an achievable 2 week development sprint scope ( 30 min)

as a group select a minimum set of functionality to complete within the

next two weeks

based on seed contributions

propose a minimal "getting started" sprint scope.

ensure

two week Sprint Cycles remaining in the release : proposal


Sprint #Completion dateProposed Theme
1August 15  .html documentation draft with seed content
2August 29Table of requirements  published  (for use by other projects/ VNFs) 
3Sept. 12Align with ONAP API definitions (after M3  milestone) 
4Sept. 24Align scope with Amsterdam release & Platform E2E Use cases / Scrub for Trademarks etc. 
5October 10Amsterdam Bug resolution
6October 24Amsterdam Bug resolution


{Then proceed to Beijing Release planning} 




Review

Team Internal Milestones

Ensure that suitable JIRA tasks are already in place to support this scope.

...

develop the user stories and tasks for Sprint 2 themes.

   5. Any other Business? (5 min)