Materials

• CNTT_BTM_Key_Metrics 2020_v0.1.pptx

Attendance

• speedwyre
• Jonne Soininen
• Shiby Parayil

Topics

• Business | Technical Metrics
• Had 1 meeting so far, meeting every 2 weeks
• Initial approach
• Identify key metrics and data sources
• What do we need?
• What do we have?
• What are the gaps (for 2020)?
• What can we automate or semi-automate?
• Service WS Strategy & Tactics?
• In Flight Initiatives
• Key Metrics Targets for 2020 Strawman (ppt)
• First Clear Target is Contribution Metrics 
• Measure contributions by CNTT community participants
• Comprehensively by segments (by company, by individual)
• Review LFN bodies of work for ideas on business case metrics
• Contributed: NFV TCO analysis
• Compute, Network Intensive
• Low, High Traffic
• Sensitivity based on # VNFs and # of VNF releases
• Identified Tools
• Bitergia, GitHub, and Dev Analytics
• Identified Data Sources
• GitHub, Wiki, Jira?
• Surveys
• Approach
  • Step 1 - Identify key metrics and data sources
    • What do we need?
    • What do we have?
    • What are the gaps (for 2020)?
  • Step 2 - Ask questions and hypothesize what will create insight
  • Step 3 - Segment and extrapolate information
  • Step 4 – Identify actions take

Notes

("AI" = Action Item)

• Work with LFN on tool they have is it named Dev Analytics? Jim will know which tool to use. LFN wants to move here over.
• AI - speedwyre add priority column, and publish CNTT Key Metrics next version.
• AI - Rick Tennant check on status of Dev Analytics LFN tool. Preference is to use it.
• When we use GitHub has inbuilt tools.
• AI - allow comment on ppt
• AI - Shiby Parayil to work with internal team to get approval to use all or part of TCO analysis for CNTT,
• AI - Shiby Parayil to work with CNTT WS leads to normalize to CNTT approaches.
• Arpit's analysis was TCO savings of 50%.