Agenda Topics:

Scope of Work Stream:
- Define community strategies that align with Common NFVI mission, objectives & outcomes
  - Discussion: Do individuals feel our strategies are well known and understood?
- Review & assess community success measures for required action(s)
  - Discussion: How do we measures overall success?
  - Discussion: Does the broader community agree on our measures?
- Ensure compliance within the community to policies, process, & principle
  - Discussion
    - Onboarding
    - Organizational Structure and Workstreams
    - Governance and Technical Work Stream Nominations and Selections
    - Voting and Approval
    - Relationship to GSMA and LFN
How to Leverage WS Contributors?
- Discussion
  - Creating documentation
  - Project management and coordination
  - Systems Implementation
  - Testing Development
  - Code Development
  - Other?
CNTT Technical F2F Work Shop (January 2020)
- Priorities & Topics Covered (Draft)
- Please direct feedback to work stream leads noted in the link above.

Notes:

Scope

Proliferating workstreams and insufficient people to work on all of them Beth Cohen
- 3 delivery teams - RM, RA, RI/RC
- Supply vs. Demand - reduce scope(pacing) OR add resources
Teams not focused on the workstream at hand Rabi Abdel
- Could adopt a 6 mo release cycle to sync with ONS AND shift to bi-weekly meetings
Is there a better way to structure the process and workflow? speedwyre
Summary Mark Cottrell
- Cadence is an opportunity
- Recruitment from the edge (not carriers, new members)
  - Former user (Deleted)
    - Near edge - surge of resources post-Paris
    - E.g. using E/// as example, more engaged now than 3 weeks ago.
    - RA and RI and RC activities spinning up at same time makes for some slowdown.
    - Taking folks awhile to get drawn into conversation.
    - There is a want to engage more but need time to gel. "Rubber still hitting the role"
- Idea - can we get a SPOC per org? Assess where org should contribute? RA, RI, RC? etc. alot of questions, e.g. 4 folks from same org. Rabi Abdel
  - Discussion - for some companies that might work, others not. More siloed companies would help, more distributed companies not so much. Mark Cottrell
  - If 3-4 months it takes to onboard, then all resources onboarded post ONS Antwerp not being effective yet in current release cycle.
  - AI - Mark Cottrell going to summarize on directions to take on this and propose.