Sprint 105 Review / Sprint 106 Planning April 22, 2013

Sprint Resource Pages For this sprint, visit: nt+105+Progress+Summary nt+105+Progress+Summary For next sprint, visit: nt+106+Progress+Summary nt+106+Progress+Summary For information on the CONNECT 4.1 release visit: 2

Sprint 105 Summary - Cumulative Flow 3 To Do In Progress QA Done

Sprint 105 Summary - Burndown Chart 4

Sprint 105 Summary – Sprint Stats Points committed = 13 –Initial points committed – 15.5 –Ticket added for 0.5 points of effort, totaling 16 points for sprint –Ticket moved for 3 points, resulting in 13 points Tickets committed to sprint = 11 Tickets completed = 7 Points remaining (unclosed) at end of sprint = 5 Points completed in sprint (velocity) = 8 5

Sprint 105 – Themes & Tasks 4.1 Release –Binaries and source available –Complete and finalize supporting documentation 4.2 Release –CMS-OFM 4.0 install on WAS 7 JDK 1.6 testing –Design for Document Query specification version identification CONN-46 & CONN-15 Participation in the Healtheway Certification pilot Partner and Community Support 6

Sprint What We are Showing Today CONNECT 4.1 released on April –Release overview page – CONNECT 4.1 OverviewCONNECT 4.1 Overview  JBoss Application Server Support  Continuous Integration and Code Base Improvements –Significantly increased automated test case coverage and build process  Additional Improvements –For important issues resolution, see Release Notes for detailsRelease Notes CONN-355/357 – CONNECT not sending organization-id attribute statement in SAML header – necessary for certification testing –Note - Support for CONNECT 4.0 is deprecated - all users are encouraged to target 4.1 for new adoption and upgrades. 7

Sprint What We are Showing Today CONNECT 4.2  Support adopters/federal partners that want to use CONNECT with Java 6 (Feature request – CONN-350) –CONN-363 – Update codebase to use Java 6 Code changes and testing approach –CONN-365 – Push CONNECT libraries built with Java 6 to maven central Demo 8

Sprint What We are Showing Today CONNECT 4.2  Provide adopters that support both versions of the specifications(QD and RD) the service version of the incoming message so that adapters can validate/further process the request and generate the version specific response (Feature request – CONN-46) –CONN-293 – Research and analysis task related to design options (Responding) –Link to design approach- w w Discussion 9

Sprint What We are Showing Today Participation in HealtheWay pilot –CONN-317 – Pre-test setup for pilot testing (not completed) Community and Federal Partner Support –Support CMS with their planned Direct Pilot Custodial Agent Duties –Unplanned infrastructure maintenance Significant impact to sprint

Sprint Proposed Themes Continued Testing for Java 6 & Java 7 Support –Installation testing on WAS 7 /IBM SDK 1.6 –Installation testing on WL 11g / JDK 1.6 –Installation testing on WL 12c / JDK 1.7 –Installation testing on WAS 8.5 /IBM SDK 1.7 –Installation testing on JBoss /JDK 1.7 –Installation testing on GlassFish /JDK 1.7 –Smoke test on all installations Research and Write Design Approach for Multi- Specification Identification for QD/RD (Initiating) –Review design approach with technical leads from Federal Partners (conference call) 11

Sprint 106 – Other tasks Run Healtheway certification pilot test cases for a vendor gateway –Pilot extended to May 31 Other tasks –Partner and Community Support –Ongoing Custodial Agent Duties Product Backlog dProjectId=

CONNECT 4.0 Community Announcements CONNECT Awareness –Open sprint review and planning meetings  Next sprint meeting will be May 6 th –CONNECT 4.0 Blogs and Forum posts – –CONNECT User Group meeting May 21 st – Call for participation and abstracts underway 13

Questions and Discussion 14