...
# | Objective | How Achieved | Participant Preparation required | Action items out |
|---|---|---|---|---|
| 2 | Requirements ToC Outline agreement sufficient to start building repo. Additional changes can be accommodated through bug reports later (10 min) . | Herb to present his proposal. (see documentation page) group discussion | review the proposals from on documentation page comments | Herb to create the skeleton files with the ToC in the repo |
| 3 | Review JIRA Backlog. Participants should be comfortable that they understand the backlog of tasks for our project ( 15 10 min) | Walk through the JIRA backlog to check for completeness Prioritize and Assign | review that the project scope in the vnfrqts Project charter has been reflected in the vnfrqts Epics and | create / update any appropriate JIRA items |
| 43 | Review project milestones due this month: (10 15 min) M2 - 8/3 M3 - 8/14 | as a group Review Milestone Checklist: M2 Checklist M3 Checklist | review the M2 and M3 checklists and definitions prior to meeting | confirm this project has no APIs. AI to answer: After Functionality Freeze, no new visible functionality is to be added to the current OPEN-O release. AI to answer: The team is using the complete Linux Foundation environment (build, Jenkins, Gerrit, FOSS, Automated Unit Test, Nexus). |
| 45 | Develop Sprint definition. Participants should be comfortable with an achievable development sprint scope ( 30 20 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 that suitable JIRA tasks are already in place to support this scope. review the SPRINT-1 backlog proposal in JIRA | |
| 5 |
4. Any other Business? (5 min)