Sprint 123 Progress Summary

Owned by Deepthi Rodrigues (Unlicensed)
Last updated: Jan 28, 2014
3 min read

Sprint Review + Planning



Jan 13 - Jan 27, 2014

 

Executive Summary

Overall Status

Sprint status is good. The Product team initially pointed and prioritized the following themes and tasks for Sprint 121 comprising 21 points. Overall the team completed 14 points for this sprint. 

While the team did start work on all the remainder tickets, the tickets were not completed. This was due to the Direct research tickets that took more time and resources than anticipated. Also for one of the regression enhancement ticket, while the work and testing was completed on CONN-615, the team was not sure that the test will run consistently and so chose to move it to the backlog for further analysis and did not take credit since it was not completed.

Note - There was also one holiday in the sprint.

Burndown

 


Sprint Themes and related tickets for Sprint 123:

  • Partner and Community support
    • Forum discussions
    • Continued work with NIST team (CONN-744)

      • Coordinated new endpoints with NIST team.

      • Updated code for Single attribute statements for multiple attributes.(just for testing purpose not included in Product)

      • Code fixed for items purposeofUse and Role(CONN-740), to include the namespace prefix for the type attribute.  Regression test creation was moved to next sprint.

      • Issues that need further discussion

        • Valid urn to be provided for AccessConsentPolicy and InstanceAccessConsentPolicy.

        • Nesting of attributes within an attribute statement vs. one attribute per attribute statement. Are both correct?

        • ReplyTo - required or optional?

        • Issues with time stamp when sending request to NIST. 
    • eHealth Exchange testing/DIL support

      • Provide DIL support team with PD,QD,RD endpoints for new DIL SUT.(CONN-747)

        •  Successfully executed responder smoke tests after the update.

      • Executed new DIL service test cases that validates if both forms(RSA and X509) are acceptable by CONNECT gateway(CONN-735)
  • Continued Testing Improvements
    • Minor update was made to G1-Patient Discovery validation test case to account for other ports.(CONN-746).
      • Validation suite was executed successfully after the update
  • Security Scan analysis and resolution 
    • Explored and researched how Fortify Software can be used to do CONNECT Security Scan/Testing (standalone and also through build) (CONN-743)
      • Fortify was successfully installed and Fortify scan was executed. Report was published.
      • Also additional research was done on how this can be integrated into CI. See ticket or details
    • Met with DoD team to discuss Fortify scan reports. 
      • Team will continue work next sprint to address the findings.
  • Direct functional enhancements
    • Updated STA Agent to use config services instead of xml file to allow for configuration changes via database.(CONN-728)
      • Was able to successfully test a happy path 
        • Send Direct email from CONNECT to another Direct RI instance.
        • Email for received by the responding Direct instance.
        • CONNECT received two MDNs (processed and dispatched) notifications.
      • Also some high level testing was done with the config services GUI.
    • Updated Maven scripts for RI config services(CONN-727)
      • Documented issues that need further discussion. see ticket for details.
    • Further research and analysis on approach is needed, this will be looked at in Sprint 124.
  • Ongoing Custodial Agent Duties
    • Created an inventory for Terremark infrastructure (CONN-738)


JIRA Planning Board of Committed User Stories for Sprint 123

Completed issues


Issues not completed in sprint

 

Related Files