Attendees
Ed-FI
Certica
Headspring
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
- 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
- Estimation
- 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 - new story
- Sprint 2
- Sprint 3
- Estimated time to completion
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 Lee cannot add field Gary will comment point estimate on ticket.
Reference Material
- DI: Multi-connection board
- DI multi-connection support epic
- DI multi-connection support design document and meeting notes