Page Comparison

...

3Develop Sprint definition

#

Objective

How Achieved

Participant Preparation required

Action items out

2

Review 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

NB I added VNFRQTS-42 to Sprint-1 as it was related to moving the seed documentation into the outlines.

review:

SPRINT-1 JIRA board
	Review gerrit Directory Structure	look at Gerrit project	FYI
3	Review Wiki Updates (15 min)	Robert Reilly to discuss tutorial videos	review VNFRQTS Contributors and Committers Processes tutorial videos added
4	Develop 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 date	Proposed Theme
1	August 15	.html documentation draft with seed content
2	August 29	Table of requirements published (for use by other projects/ VNFs)
3	Sept. 12	Align with ONAP API definitions (after M3 milestone)
4	Sept. 24	Align scope with Amsterdam release & Platform E2E Use cases / Scrub for Trademarks etc.
5	October 10	Amsterdam Bug resolution
6	October 24	Amsterdam Bug resolution

{Then proceed to Beijing Release planning}

Review

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)

Versions Compared