Page History

Current Sprint - Sprint 16 (October 29, 2015 – November 11, 2015)

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint16

We reviewed the backlog and discussed how to enter exit criteria for a story/bug.  This will help everyone understand when this issues can be considered done.

We also mentioned that we will be grooming the backlog weekly, moving stories to the top based on priority.

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Recent CTS2 Service Related Issues (within last week)

LEXEVS-1296 - lbGUI cleanup script fails when no metadata is present. 

We should consider working on this issue in the next sprint as well as add exit criteria to herethe issue.

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Review decision regarding the single jar vs. a zip file

Re: Consideration of Build Impacts

We all agreed upon the proposed solution in the above link.

TODO: Mayo to create a JIRA item to capture the solution issue.

VPN and network evaluation

Craig was able to re-start this discussion between NCI and Mayo IT.  Both sides of IT are exchanging information to continue the workdiscussion.

It was also mentioned that eventually, Mayo will need access to the NCI continuous server.

There is a wiki link for agenda topics: LexEVS 6.3 and 6.4 Technical Face-To-Face Meetings

TODO: Mayo will add the following Face to Face topics to the list for our Face to Faceour list:

• Continuous server discussion Add the continuous server discussion to the list of topics.
  
  • How Mayo implemented theirs their CI server and what NCI's plan is for their own server.
• Add browser/LexEVS performance to the list of topics.
• Loaders - how to create one from scratch.  Create a simple example of a loader.
• End user approach to LexEVS
  
  • Tutorial on how to query the LexEVS API
  • Review of existing LexEVS documentation.
• REST - CTS2 REST vs additional (extensions) REST calls like bulk download.
  
  • Discuss a REST Framework that includes CTS2 and other calls (extensions).

We requested NCI to fill in any addition notes/priorities on the list of proposed topics.  This will help Mayo prepare for the meeting.

LEXEVS- 970

• OWL2  - prioritize this work

Scott suggested that we create a new story to capture the next set of OWL2 changes.

We discussed the possibility of creating an "epic" for all of the OWL2 issues/features.

TODO: Mayo to create JIRA items for the known OWL2 issues today and then close LEXEVS-970.