Attendees

NameRolePresent
Wright, Larry NIH/NCI  x
Fragoso, Gilberto NIH/NCI    x

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

NIH/NCI [C]x
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCI [C]x
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C]x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      

Agenda

Sprint Status

 

Current Sprint  Sprint 44 (November 23, 2016 – December 7, 2016)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint44

F2F Debrief

Discussion Points:

  • We felt this was a productive face to face. 
  • The ideas here will guide us for the next year.
  • We will have to do additional planning and prioritization.
  • Some of the major focus points will be on REST, DevOps, the use of micro services, and triple stores.

Decision Points:

  • Scott to submit a ticket to request a DEV VM at NCI.

LexEVS 6.4.2 (Java 1.8)

  • Timeline discussion

Discussion Points:

  • There have been several LexEVS updates recently. 
  • We want to be considerate of the churn for the clients that will need to update.
  • We need to be at Java 8 to move to Cent OS 7.
  • The browser is not running at Java 8 yet.

Decision Points:

  • LexEVS 6.4.2 branch is running on Java 8. 
  • LexEVS-2510 fix (for the API)  will be included in the 6.4.2 branch.
  • Jason will create a ticket to start Java 8 build.

Backlog grooming discussion

  • Recent grooming performed
  • Set up meeting request
    • Mandatory attendance
    • Optional attendance

Discussion Points:

  • NCI team is willing to work with us as we groom the backlog.
  • Tracy suggested sending a list of JIRA issues ahead of time to review.
  • Start with a small group of technical developers.

Decision Points:

  • Initial backlog grooming group should contain the following: Rob, Tracy, Gilberto, Kim, Cory, Scott, Craig.
    • Gilberto and Larry can be option depending on the issues we are reviewing for the current meeting.
  • Mayo team to create a wiki that contains the list of JIRA issues we want to discuss.
  • Craig to send meeting notice out.

Sprint 45 Planning

  • Prioritize F2F issues

Discussion Points:

  • We reviewed the current items queued up for sprint 45.
  • We discussed MySQL 5.6 upgrade.  Once we verify it for performance, we can upgrade when NCI Systems team is ready.
  • Larry asked to add the value set fix (loader part of the fix) to this sprint for LexEVS 6.4.1.3.

Prioritize F2F issues

Decision Points:

Craig asked how we should start prioritizing the priority 1's.  This is what prioritization the team decided (in order):

  • Tech stack and deployment stories.
  • Value set workflow management stories to support Rob/Tracy
  • REST features to support our clients.
  • DevOps, CI server and Docker
    • These are dependent upon NCI systems.
  • Tracy and Rob mentioned that the command line script functionality is suffice for now.
    • The current admin stories are "nice to have", but not necessary.

6.4.1.3 issues

Discussion Points:

  • OWL1 loader change
  • GUI updates
  • Value Set load

Decision Points:

  • We would like to add the LexEVS-2510 to 6.4.1.3.  But only the loader change for this issue.
    • There is a loader fix and and API fix for this issue.

NCI Nexus Server Migration Update

Discussion Points:

  • No updates

Decision Points:

BioMarker Discussion

Discussion Points:

  • No updates

Decision Points:

CTS2 URLs for 6.3 and 6.4

Discussion Points:

  • No updates

Decision Points:

Initial grooming

  • On Hold Issues
  • Initial Items to review

Discussion Points:

  • Initial Items to review

Decision Points:

  • On Hold Issues - We agreed to close them all (Resolved - Not Fixed).
    • The Mayo team will close these issues.
LexEVS External Users 
Team Absences

Mayo Team

  • Cory -
  • Scott - Dec 9
  • Craig -

NCI

  • Tracy
    • Dec 14-16
    • Jan 9-17
    • Feb 21-24
  • Rob
    • 12/9

    • 12/19

    • 12/23-12/27

    • 1/2/2017

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Recent CTS2 Service Related Issues (within last week)

6.4 LexEVS Related Issues

6.4 CTS2 Service Related Issues

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
 None     
       
       

 Planned Activities

Area of InterestDetails
  
  
  

Risks, Issues, Dependencies

Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

Action Item Backlog

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  on hold
281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold