/
Sprint 118 Progress Summary

Sprint 118 Progress Summary

Owned by Deepthi Rodrigues (Unlicensed)
Last updated: Nov 04, 2013Version comment

Sprint Review + Planning

Oct 21 - Nov 4, 2013

Executive Summary

Overall Status

Sprint status is excellent. The Product team had pointed and prioritized the following themes and tasks for Sprint 118 comprising 16 points.The team completed 15 points.

The team also added a couple of tickets into the sprint later in the sprint for further investigation that are In Progress and will be carried over into the next sprint. 

Burndown

Sprint Themes:

  • Testing improvments
    • Regression automation (remainder tickets - pick one each sprint) (CONN-642)
    • Run interoperability test results between 4.2 and 3.2 and 3.3 environments on the GFE environment(CONN-652) 
  • Support community with Release 4.2 deployments and questions
    • CMS , DoD
    • NIST test cases (CONN-657)
      • Understanding what it would take to set up NIST testing tools environment internally on CONNECT.
    • Bug fixed related to expired certificate and CONNECT builds failing (CONN-667)
      • Release notes updated
    • Bug related to SAML PurposeOfUse (CONN-647,CONN- 651)
    • Bug related to a security CCHIT test case (CONN-645)
    • Bug related to Merlin Crypto package classes and properties jar files(CONN-646)
    • GUI Binaries for 4.2 (CONN-648)
  • Direct enhancements (CONN-655, CONN-656)
    • Latest instance of Direct RI 3.0.1 set up. 
    • Lessons learned documented as well as high level analysis/discussion into how CONNECT can be extended to include the RI features from a technical standpoint.
  • Start deeper research of potential issues identified in the Fortify security scan results(CONN-611)
  • Static code analysis improvements (CONN-45)
    • Fix FindBugs High issues(CONN-661)

Prioritized JIRA Planning Board of Committed User Stories for Sprint 118

(https://issues.connectopensource.org/secure/RapidBoard.jspa?rapidView=1&view=planning&versions=visible)


Related Files