Versions Compared

Key

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

...

Sprint status is excellent. The Product Team had prioritized the following themes and tasks for Sprint 146 comprising 30 31 points.Themes for the sprint included -

  • Release 4.4 general availability
  • Close completed Release 4.4 User Stories 
  • Support for the Federal Agencies Implementations (VA, CMS, DoD, SSA)
  • Support any CMS X12 Testing Activities 
  • Planning and backlog grooming for next sprint

The team completed 37 31 points during the sprint and are well positioned to meet the scheduled release date for released CONNECT 4.4 on time as scheduled. The team completed regression and interoperabiltiy testing, feature testing and successfully install tested the release candidate RC2 as well as made great progress on the documentation updates for the release. also presented a demo of the features and functions to the federal partners.

Burndown:

Sprint Themes and related tickets for Sprint

...

146:

Partner and Community support

  • Reviewed 4.4 findings with the SCQC team. Scheduled follow-up meeting with team to discuss Find Bugs and wrap-up the 4.4 testing effort.(CONN-1530)
  • Participated in discussions with Healtheway on specification compliance issues and process improvements

Next Release (4.4)4.4 made generally available on Dec 9 2014 and documentation on the wiki was reviewed. The team also demo'd the new features available to the federal partners.

Support for NwHIN CAQH Core X12 Document submission service (Feature complete)

X12 Document Submission service documentation

...

 

Other tasks post release

  • Updated Regression suite with some minor updates for better consolidation and understanding. (CONN-1538)
  • Generated and saved CONNECT messages for all supported releases for future reference (CONN-1567)
  • Updated GitHub branching to prepare for next development/release (CONN-1568)
  • Prepared for sprint 0 for next release.(CONN-1553). Completed closing all internal tickets(tasks or chores) in external facing JIRA and cataloged what should be created in new internal JIRA. Also, began review of potential user stories from release planning.
  • JIRA Planning Board of Committed User Stories for Sprint 146:

JIRA Planning Board of Committed User Stories for Sprint

...

146:

 Image Added

Image Added