Wiki

Date: June 11, 2015

Arno release retrospective material

• Cross team/project collaboration
  • The community members should continue to contribute across different projects. If there are dependencies across projects a contribution to overcome them is the best way to keep moving forward.
  • Willingness to help on-board new members (e.g. on IRC)
• Great leadership from the Functest project team who had to step forward in the past few months and manage the transition.
• Engagement with upstream communities (e.g. impact recently at the OpenStack Summit)
• Good visibility of Arno on social channels

• Arno retrospective Etherpad
• Burden on a small number of SMEs as was also highlighted in other email threads
• Should be more clear on the areas where we need resources will help our members and the broader community find the right people to have involved
• Discussed more resource needed for
  • ODL SME
    • Maybe OSGI/Karaf people to help with platform issues you see on ODL or ONOS
  • People who are in telco operations who are actively deploying applications today and can provide feedback
  • Testing competencies, with broad experience in testing for application deployment scenarios
  • Collaboration with SDOs
• More resource on training and on-boarding is needed (both for new developers & users)
  • Better project information/dashboard will be helpful for people that are new to the project

• Scope management
  • Within 2 months of project launch, there was a relatively clear idea of the Arno scope. This reduction in scope was a contributing factor in being able to deliver.
  • The communication of the Arno scope after the decision was made could have been better
  • There was not an change management process for decision making during Arno and better communication could have reduced friction

http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-11-13.01.html