Mar 24 - Apr 7
...
, 2014
Executive Summary
Overall Status
Sprint status is goodexcellent. The Product team prioritized and completed the following themes and tasks for Sprint 128 comprising 31 points. These themes included - Addressing Technical addressing technical debt, community support post release , and design discussion for new feature development - Direct, Admin GUI and Testing gaps. 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. The After the start of the sprint, the team pulled in additional tickets totalling 36 points. Additional bringing the total committed points to 45; additional tickets pulled in included code cleanup and regression suite cleanup. The . 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 work working on a ticket related to the Direct feature for 5 points, but could not complete it. The team also worked on WebLogic 12c(12.1.2) installation, but could not complete the task. These tickets may slide over to the next sprint or will be added to the backlog.
Burndown
final team velocity for Sprint 128 was 31 points.
Burndown
Sprint Themes and related tickets for Sprint 128:
- Community Implementation support
- Worked with the VA team on their 4.2.1 deployment in their development environment
- Supported several meetings and email exchanges
- Support and testing efforts continued with NIST, discussed several topics and compared interpretations of specifications
- Transport test cases passed from NIST to SUT. Test from SUT to NIST failed, but issue seems to be on the NIST side, NIST does not seem to accept the xsi:type = "CE" attribute value Email sent to NIST explaining the issue.
- Responded to forum posts - http://www.connectopensource.org/developer-resources/forums
- Worked with the VA team on their 4.2.1 deployment in their development environment
- 4.4 Release
- New Features for next release
- Direct enhancements discussion and planning(CONN-951)
- The team discussed Direct feature and approach for implementation, documented notes and created functional and technical stories-
- Discussed new implementation guide for edge protocols - https://connectopensource.atlassian.net/wiki/x/BQDV
- Discussed goals - https://connectopensource.atlassian.net/wiki/x/oAGD
- Requirements draft is here - https://connectopensource.atlassian.net/wiki/x/lwGD
- Design approach draft - https://connectopensource.atlassian.net/wiki/x/KwGD
- Epic for these enhancements - CONN-381, that includes all the technical and user stories.
- Design will be updated iteratively as user stories are completed
- Administrative GUI enhancementsdiscussion and planning (CONN-938)
- The team discussed Admin GUI feature, documented notes and created functional and technical stories.
- Epic for these enhancements - CONN-48, that includes all the technical and user stories.
- Discussed gaps in test coverage and came up with a list of tasks(CONN-993)
- The tickets created per this discussion are in the CONN-1008 epic.
- Direct enhancements discussion and planning(CONN-951)
- Bug 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)
- 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)
- Made updates to the wiki page - /wiki/spaces/CONNECT4/pages/10584090
- 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)
- Discussed gaps in test coverage and came up with a list of tasksResearched and analyzed 4.2 installation on WebLogic 12c(12.1.2) (CONN-895)
- New Features for next release
- Ongoing Custodial Agent Duties
...
JIRA Planning Board of Committed User Stories for Sprint
...