Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

  1. Good
    1. The four day F2F session have been productive.
    2. Great opportunity for meeting everyone F2F.
    3. Perfect opportunity for collaboration, co-creation and knowledge sharing session.  
    4. Discussed product evolution and improvement in ONAP.
    5. Overall the F2F session resulted in faster turnaround for resolving open design/development issues.
  2. Improvements
    1. Encourage the team to hold F2F session for Dublin release.  
      1. Start the F2F Session when the use case are approved.
      2. Engineer/architecture/requirement discussion before development start.
      3. Encourage frequent but shorter F2F session for ONAP initiative.  (1-2 day or 2 - 3 session F2F)
    2. With some new members joining the ONAP community a introductory ONAP session is helpful which provides more context for the capability and/or project overview is being presented.
    3. Provide a user guide on the new capabilities being delivered as part of the CDS initiative.
      1. Read docs format
    4. Environment being ready and stable earlier in the development cycle
      1. Expected E2E to work test case execution.
    5. Instance feedback- Rocket Chat??-- for the CDS initiative / Controller – Instance feedback.
      1. Engineering
      2. Development
      3. Testing
  3. Do the partners want to do this again for Dublin?
    1. Yes- the partners found the meeting productive and encourage more frequent and shorter session for Dublin planning and delivery release. .


        NOTE: ONAP Community Members include AT&T, Bell Canada,  AMDOCS, IBM, TechM, and Huawei.

  • No labels