Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 14 Next »

March 11th - March 24th, 2013

Executive Summary

Overall Status

Sprint status is Excellent. The team accomplished almost all of the thematic work defined for the sprint.

Burndown

Cumulative Flow

Sprint Themes

The Product team pointed and prioritized the following themes and tasks for Sprint 103 comprising 24 points. The team completed XX of the 24 total points for this sprint.

  • 4.0 Partner and Community Support
    • SSA 4.0 install on WAS. 
      • CONN-288 - Provide support for SSA and their efforts to download and install CONNECT 4.0 into their development environment.
    • CMS-CCSQ 4.0 install on WL 11g or 12c. 
      • CONN-290 - As a CONNECT adopter, I want support installing and deploying CONNECT 4.0 successfully on Webogic 11g so that I can validate that it works in my preferred environment.CMS-OFM 4.0 install on WAS 7 JDK 1.7
    • CMS-OFM 4.0 install on WAS 7 JDK 1.7.
      • CONN-279 - As a CONNECT adopter, I want CONNECT 4.0 to be tested on WebSphere 7.x to validate whether CONNECT will work in my preferred environment. (See also CONN-313 for some additional analysis)
    • Respond to IHS re the Direct ticket. 
      • CONN-278 As a CONNECT adopter, I would like assistance installing and configuring "Direct only" for CONNECT 4
    • Community support through forum responses and guidance. 
  • 4.1 Enhancements
    • Multi-Spec QD / RD End point enhancement for DoD/SSA (pending DE&I approval) -- Was not included in sprint_._
    • Installation improvements through community engagement
    • Continued development of a robust CI and automated test environment
      • .
    • 4.1 Patch Release - patch release test and make enhancements to 4.0 available to community
      • Features and Improvements
        • CONN-303 - As a CONNECT adopter, I want CONNECT to be deployable in JBOSS, so that I can use my preferred application server for health data exchange. 
        • CONN-301 - As a CONNECT user, I want the Direct feature to work out of the box on binary installations, so I can set up Direct more easily. 
        • CONN-74- As a CONNECT adopter/developer I want a clean property file (gateway.properties) so that there is no confusion with regards to the unused properties or default values.
        • CONN-285 - As a CONNECT community member, I need Direct installation instructions to be updated to detail configuration steps, so that I can easily install and configure Direct in my environment
      • Bug Fixes
        • CONN-319 - Fix testMpi resource so it doesn't always get updated 
        • CONN-292 - CONNECTSamlAssertionValidator Logic needs review 
        • CONN-280 - PatientDB implementation does not work 
        • CONN-183 - Missing DIRECT_ERROR event in use case (Direct-A-Thon) 
        • CONN-92 - Remove NHINC_PROPERTIES_DIR environment variable 
        • CONN-40 - Audit Log Transforms (PD) throws exception in server log 
        • CONN-37 - NPI SAML attribute is not supported in CONNECT 
        • CONN-61 - GUIs deployed in the EAR (GF) cause the admin console to misbehave after restart 
      • Release prep and other tasks
        • CONN-300 - As a CONNECT Community member I would like to be notified and understand the CONNECT 4.1 release via Patch Release notes on the wiki 
        • CONN-299 - Release test plan 
        • CONN-307 – Interop testing 
        • CONN-306 – Installation testing 
        • CONN-305 – Re-verification testing 
        • CONN-304-- Regression testing
        • CONN-295 - Interop: Update harness for repeatable Ldev11 tests 
        • CONN-310 - standardize recommended java options (heap sizes, perm sizes) across installation instructions (New ticket added)

Prioritized JIRA Planning Board of Committed User Stories for Sprint 103

(https://issues.connectopensource.org/secure/VersionBoard.jspa?selectedProjectId=10140)


Related Files

  • No labels