Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Sprint Review + Planning



 

Jan 27 - Feb 10, 2014

 

Executive Summary

Overall Status

Sprint status is excellent. The Product team initially pointed and prioritized the following themes and tasks for Sprint 124 comprising 48 points. Overall the team completed 44 points for this sprint. The 4 points that were not completed were additional tickets pulled into the sprint for which the coding was complete but regression tests/QA was not completed.

The team completed all the tickets related to the theme for this sprint which was Security Scan Analysis and Resolution.

Burndown


Sprint Themes and related tickets for Sprint 124:

  • Partner and Community support
    • Forum discussions
    • CMS Production Support
    • DoD testing
    • Continued work with the NIST team
      • A new CONNECT system was set up for NIST testing to separate it from the machine used for DIL testing, thereby providing the team with greater flexibility as we continue to support both efforts.(CONN-799)
      • Had a follow-up discussion with NIST. Pending issues
        • NIST to fix Reply-To so that it will  be sent.
        • Attribute statement nesting. Open question with spec factory. CONNECT has not made any changes yet, we do have a backlog to allow for a single nested attribute statement. At this point it seems that NIST would need to fix to accept both flavors - single attribute statement with all attributes nested as well as support each attribute within its own attribute statement.
    • Community Implementation support
      • Release 4.2.1 rebranding.(CONN-798, CONN-783, CONN-772
  • Continued Testing Improvements
  • HIEM was removed from the codebase (CONN-771)
  • Infrastructure improvements
    • Ability to tag and generate binaries from any branch specified (CONN-786) which helps simplify the release process for binaries generation. 
    • Infrastructure migration for Terremark (CONN-778)
      • GFE cleanup of configurations and servers 
      • Inventory management and documentation
  • Security scan analysis and resolution(CONN-669,
    • This was the primary focus in Sprint 124. The team addressed all the Critical and HIgh tickets for Fortiy.
    • Wiki page with details -  Fortify Install notes
    • Some of the issues identified by the Fortify scan were fixed in code and some of these were addressed with documentation.
    • Log4j logging 
  • Direct functional enhancements
  • Bugs that were fixed
    • Extract slots always gets one last value from the slots list (Adapter) (CONN-484)
    • SAML Assertion AuthzDecisionStatement resource is passed from the adapters to the external parties 'as is', failing the DIL test MA-1092_AuthzDecisionStatement_Resource(CONN-612)
  • Ongoing Custodial Agent Duties
  • CONNECT 4 Blogs and Forum posts


JIRA Planning Board of Committed User Stories for Sprint 124

Completed issues



Issues not completed in sprint

 

Related Files

  • Sprint 124 code tag

 

  • No labels