Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sprint status is excellent. The Product team prioritized and completed the following themes and tasks for Sprint 129 comprising 38 points. These themes included - addressing technical debt, community support post release and design discussion  begin work for new feature development - Direct, Admin GUI and Testing gaps. During . The team also supported and participated in the CONNECT CCB to understand priorities and high level requirements from the federal partners.

A few tickets were added during the course of the sprint some support related tickets for VA, DoD and Triple-I install were moved out early due to additional time required for pre-requisites - infrastructure or related paper work. After the start of the sprint, the team pulled in additional tickets bringing the total committed points to 45; additional tickets pulled in included code cleanup and regression suite cleanup. Three tickets totaling 9 points were removed from the sprint due to outside constraints preventing the team from working on these.  The team also started working on a ticket related to the Direct feature for 5 points, but could not complete it. The final team velocity for Sprint 128 was 31 points.for tasks that the team thought necessary to address to support either development of the new features or support the community, this brought the sprint point total to 41. These include - an issue found with event logging (CONN-1045) that was discovered as part of the Admin GUI feature. Also research into the HeartBleed bug and its impact was included(CON-53, 1059). A small bug was also notificed in the DocQuery adapter that was fixed(CONN-1061).

The team completed 40 points this sprint. The only ticket that was not completed and will be moved over to the next sprint isCONN-952(Supporting VA with 4.2.1 upgrade). This ticket was not completed since VA moved their CONNECT development work over to the next week .

Burndown

Sprint Themes and related tickets for Sprint 129:

  • Community Implementation support
  • Plan for 4.4 Release 
    • New Features for next release
      • Direct enhancements discussion and planningenhancements 
        • As a CONNECT developer I want to analyze Direct functionality and design an approach to creating test scripts in order to have functional level testing coverage of Direct (CONN-
        951
      • Regression test update - RequestResponseContentTypeTest - Document Retrieve - Description update(CONN-948)
      • Investigated and tested large payload for Administrative Distribution and it was working as expected, no code changes were needed.  (CONN-931)
      • Investigated and tested Event logging in the context of Patient Discovery Deferred response logging extra events, no code changes were needed(CONN-331)
      • Corrected setup and tear down scripts for regression suites(CONN-951)
      • Fix PatientDiscoveryInternalErrorMessageIdTest deferred response test case .(CONN-529)
      • After executing the Passthru Test cases using JMX code, some of the transactionIDTest test cases are failing.(CONN-1000)
      • Researched and analyzed 4.2 installation on WebLogic 12c(12.1.2) (CONN-895Bug fixes and other improvements this sprint
        • Investigate how to create secured Mock NwHIN services (CONN-978) -/wiki/spaces/CONNECTWIKI/pages/13467724
        • Remove HIEM interfaces from regression suites (CONN-953)
        • Remove HIEM related properties from various soapUI Property files. (CONN-995)
            • Created a story plan for Direct service that defines the Main and Alternate paths to determine the acceptance criteria for the service.(CONN-1022)
              • This will be refined further as more development work is accomplished and should help out with test/regression scripting as Direct is being enhanced.
            • Analyzed and researched options to test Direct from a regression perspective (CONN-1031)
              • Created a POC to confirm how SOAPUI 4.5.x with the Java Mail jars and can be leveraged.
              • Separate mail accounts can be created for automated testing both in Receiving STA and Sending STA so that it will be independent of other direct testing
              • Separate email accounts from the Sending STA (CONNECT Direct) for Incoming and outgoing mail servers so that CONNECT pollers will be independent of other CONNECT Direct instances
              • Separate Recipient email account in the Receiving STA (amazon Direct RI instance) so that the testing can be automated
              • Analyzed how event logs could be used to test Direct as well as how Direct can be performance tested
          • Refactor Direct as a service (CONN-997)
            • Create and expose interfaces via java + web services to process direct messages. Implemented sendDirect and ReceiveDirect as web services to help with testing and integrate with mail servers. 
          • Create Direct configuration services in the CONNECT tech stack (CONN-998)
            • Implemented Spring/Hibernate Direct configuration services as part of CONNECT to enable changing Direct config settings through the Admin GUI(CONN-1034)
            • Inject services into the wsdls (CONN-1033)
        • Administrative GUI enhancements 
          • Created a backing bean to pull the data from a mock service that demonstrates the remote gateways the local gateway communicates with, including number of transactions (CONN-1028, CONN-1023)
          • Create the Admin GUI page/xhtml for displaying the information from the backing bean(CONN-1027)
        • Bug fixes and other improvements this sprint
        • Adding missing sender/receiver values to event logging to help display number of transactions in Admin GUI(CONN-1045)
        • Fixed bug related to Doc Query Adapter pre-pending extra prefix to ExtrinsicObject Home(CONN-1061)

    • Ongoing Custodial Agent Duties

    ...

    JIRA Planning Board of Committed User Stories for Sprint 120

    ...

    Tickets not completed


    Related Files

      Sprint 128 129 code tag