...
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
...
- 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 2Sprint 3
- 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
- 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.
- Sprint 2
- 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.
...
- DI: Multi-connection board
- DI multi-connection support epic
- DI multi-connection support design document and meeting notes