/
9.16.2020 Weekly Data Import multi-connection check-in

9.16.2020 Weekly Data Import multi-connection check-in

Sep 15, 2020

Attendees

Ed-FI 

  • @Jason Hoekstra (Deactivated) 

Certica

  • @Gary Clarke

  • @Alex Kichkailo (Unlicensed)

Headspring

  • @lee.morrow

  • @Patrick Lioi (Deactivated)

Agenda

  • Gary and Alex summarize the design decisions/changes made during Sprint 1 for Patrick's understanding

  • Gary, Alex, Patrick Unblock EDFI-396 

  • Gary and Alex open questions for Patrick from story definition?

  • Team sprint 1 review / retro

  • Team do future sprint planning

    • Estimate remaining stories

    • Commit stories to Sprint 2 

    • Rough plan and timeline for getting to done

Discussion

Sprint 1 design decisions  

Gary and Alex briefed Patrick on the below design decisions and reviewed the corresponding changes in the design document.

  • Data model should refer to ApiServers rather than ApiConnections (see EDFI-406)

  • Agent deletion behavior (see EDFI-394)

  • Alex's bug fixes

Unblocking EDFI-396

  • Gary and Patrick confirmed this is unblocked. Lee to mark story as unblocked. 

Open questions from definition

  • EDFI-398

    • Addressed two question posed by Gary in the story. Gary will update story and design doc where necessary. 

  • New scope

    • EDFI-406

    • PowerShell preprocessor work for consideration to include in a release following 1.1.0

      • Gary and Alex will develop draft design document and share with team for review / feedback. 

      • Gary to create placeholder epic in the backlog detailing the scope of work for consideration in future release.

Sprint 1 retro/review 

  • Done

    • EDFI-375

  • In Review

    • EDFI-392

    • EDFI-393 

  • Carry-over to Sprint 2

    • EDFI-394

    • EDFI-373

  • What can be improved?

    • Start using a single sprint board as the source of truth

    • Estimate remaining stories to improve ability to complete sprint scope

Future sprint planning

  • Sprint 2

    • Gary and Alex committed the below stories to sprint 2. This is all the remaining scope required for the DI 1.1.0 release. They feel confident they can deliver on the commit given Alex's bandwidth has doubled from %50 to 100% from sprint 1 to sprint 2. 

      • EDFI-394 - In development - carryover from sprint 1

      • EDFI-373 - In development - carryover from sprint 1

      • EDFI-398 - Ready for development

      • EDFI-396 - Ready for development

      • EDFI-395 - Ready for development

      • EDFI-397 - Ready for development

      • EDFI-406 - Ready for development 

  • Estimated time to completion

    • Gary estimates they will be able to be release ready by the end of sprint 2 / week 1 of sprint 3 at the latest.

Action Items

@lee.morrow to mark EDFI-396 as unblocked 
@Gary Clarke to document changes resulting from solutioning of EDFI-398 in story and design document
@Gary Clarke to create placeholder epic for PowerShell preprocessor work in the backlog detailing the scope of work for consideration in future release.
@lee.morrow to troubleshoot adding points field to DI tickets and notify Gary of outcome. If the field is added Gary will enter the point estimates. If Lee cannot add field Gary will comment point estimate on ticket. 

Reference Material