Sprint 100 Progress Summary

Owned by Former user (Deleted)
Last updated: Apr 21, 2013 by Michael PafumiVersion comment
3 min read

January 28 - February 10, 2013

Executive Summary

Overall Status

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

Burndown

Cumulative Flow

Progress

Sprint Themes

The Product team pointed and prioritized the following themes and tasks for Sprint 100, comprising 43.5 points. The team pulled in an extra 1.5 points during the sprint and completed 45 of the 45 total points for this sprint.

Proposed Themes:

  • Complete Release Testing
    • Re-verification tests (performed on JDK 1.7 11)
    • Interop tests
    • GUI testing
    • Prioritize and address issues as necessary for RC2/GA
  • Perform Final Transaction Performance Benchmark test
  • Release Documentation
    • RTM completion
    • Test Summary completion (including final Benchmark Performance test results)
    • SAD completion
    • SIAM completion
    • Release notes completion
    • Draft webinar / blogs materials (Business & Technical)

Proposed Tasks:

  • Further FIPS work
    • Continue Working with CMS and any other interested partners
  • Work with ONC VLER Support on their IV&V Testing outcomes from the Beta tag
    • Prioritize and address any issues per published procedure
      • GATEWAY-3390 - Fails to run on IBM WebSphere Application Server V8.x - Closed
      • GATEWAY-3404 - CONNECT Consumer Preferences Profile GUI - Patient search throws exception - Closed
      • GATEWAY-3405 - CONNECT Deferred Queue Manager GUI - Process Queue and Search Queue functionality throws exception - Closed
      • GATEWAY-3406 - CONNECT Universal Client GUI - Attempts to access the deployed application throw exception - Closed
      • GATEWAY-3349 - Initialization of Hibernate framework throws java.lang.NullPointerException - Closed
  • Smoke Test CONNECT 3.3.1.3 with JDK 1.7 11
  • Began work on HIMSS 2013 Interoperability Demo materials

Sprint in Context

The next release of CONNECT intends to include the features listed below, which were approved by the CONNECT change control board and the Federal Health Architecture Managing Board.

1. CONNECT adopters shall have the ability to increase throughput targeting increased numbers of PD, QD, RD, AD, and DS transactions

2. CONNECT adopters shall have the ability to exchange and process large payload sizes of up to 1 GB

3. CONNECT adopters shall have the ability to run on additional application servers such as WebSphere and WebLogic to meet their environment needs

4. CONNECT adopters shall have the ability to get more comprehensive performance logging and metric data (counts and duration) using improved logging in CONNECT

5. CONNECT adopters shall be able to determine the state of a transaction across messages in order to better troubleshoot and analyze the operation of CONNECT and their trading partners

6. CONNECT adopters shall have the ability to minimize deployment load by supporting a lightweight gateway which allows smaller server footprint and use of system resources and allows the federal partners to maximize the use of their custom-built adapters.

7. As a CONNECT user, I need CONNECT to integrate with and support the Direct Project specifications
See this page for details on the features for CONNECT 4.0.

Related Files