...

• Build and Package Infrastructure 
  
• Deployments
• Dynamic configuration
• gRPC  
• GUI 
• ISSU (In-Service Software Upgrades)
  
• Lion (Localization/Internationalization)
• Orchestration
• P4
  
• Security & performance analysis  
  
• Teaching
  
• Virtualization

...

The brigade helps the community scale and take on work items. In using brigades as a work unit, the community is counting on them to execute to their plans successfully. We expect the leader and the brigade members to have the desire, motivation, and skills to make and MEET commitments to the community. Also, as part of the community, it is expected that brigades will engage with the release planning process and the sprint planning process. Specifically, we expect brigades to do the following in the different phases of the ONOS release cycle:

Planning

• The brigade lead will work with their team and the ONOS TST to define a high-level vision for their group's efforts and will document this on their brigade's wiki page.
   
• The expectation is that the lead will be working with their brigade to define a set of deliverables that the team can commit to delivering and this will be communicated in the release planning meeting.  Commit in the release planning meeting to deliverables for a release. The deliverables and requirements can come from many places in the community, or from the brigade itself. The community is counting on the brigade to deliver on its promises for the release.

Execution

• The brigade will keep a public location udpated updated with work items and status so that the brigade's work is visible to the community (a JIRA dashboard, for example).
• The lead, or the lead's delegate, will participate actively in the brigade review meeting held once a month .in order to work with other leads to solve problems and make their brigades and the brigade program better.
• If there are concerns about progress on committed deliverables or with any part of the brigade process, we expect leads to reach out and raise those concerns so that we can support you with addressing those.
• We expect that progress will be communicated in the regular sprint review meetings through creating a slide with relevant details At least one member of the brigade participates in the ONF sprint review meetings to talk about what progress has been made in the brigade over the sprint period.  Attending the meeting to talk over the slide is optional but encouraged.
  

Delivery

• The lead, or the lead's delegate, will participate in the release review meeting to show what the team accomplished for the release.  We expect relevant details to be captured in a slide.  We highly encourage that a brigade does a demo at this meeting to showcase their efforts to the community.
  

Roles, Recommendations and Requirements

...

The product owner makes sure the work of the brigade is relevant to the operator. As such, the product owner usually comes from an operator environment (AT&T, Verizon, etc..) and they have a PoC, Lab Trial, or Field Trial that has been selected by the use case steering team. The person could also come from a vendor involved in a PoC, lab trial, or field trial. It is similar to the role as defined in agile scrum. In short, they make sure the features are defined from the end user perspective, and they make sure that work is done in priority order. The product owner provides "pull" for features from the team - helping to bring the work into use in the network. One can find more information on the web about the role of a product owner. One such page is here.

Meetings

All brigade leads and mentors are asked to attend a monthly status call – the purpose of the call is to support the effectiveness of brigades by creating a place where leads and mentors can raise any concerns or blockers and where they can learn best practices and tips.  The call is currently scheduled every fourth Wednesday at 10 pacific and you Brigade leads and members come from around the world and we recognize that it is impossible to schedule meetings that will work for everyone in every time zone.  Because of this we are sensitive to asking people to attend meetings and we've tried to minimize brigade-related calls.  We strongly encourage brigades to participate in the regular sprint and release reviews however since it is important to coordinate your efforts with others in the project and it is a great opportunity to get the recognition and credit you deserve.  If a lead can't join the meetings, please find someone else on your brigade that can make the call.  You can find the meeting details on the ONOS community calendar.  If you're unable to attend this meeting, please either delegate this to another brigade member.  For other meetings, you and your brigade can decide if and when to schedule team meetings.

Brigade Leads Mailing List

If you are leading a brigade or acting as a mentor, please take an active role on the Brigade Leads mailing list.  This list is for leads and mentors of active ONOS and CORD brigades.  Discussions will focus on discussing issues, asking questions and sharing tips about running a successful brigade.  You will benefit from learning about what has worked well for other brigades and other leads can learn about the tips and suggestions you have from your experience.

Test Coverage

Test Coverage is an important aspect for stability of ONOS.  Test Coverage includes Unit Tests and System Tests. 

...

Visualization of Roles and Process

...