Sprint Review | Date | Demo Schedule |
---|---|---|
20.2.1 |
| Data Use PI 20.2 Demo Schedule |
Question | Response | Dashboard Gadget | |
---|---|---|---|
1 | Did the team complete all of last sprint Goals? Explain any goals that did not complete. | One issue for the additive model didn't get completed because our developer lost their internet connection several times this sprint. |
|
2 | How did things go last sprint (WIP, scope change, blockers, etc)? | We are carrying over 1, 3 point ticket. Everything we brought in was completed. Brought in improvements UMM-S 1.6.1, UMM-G 1.3.1 for OPeNDAP, and documentation. Blocked Issues -
|
NOTE: This gadget reflects the current active sprint. Blocked Tickets
|
3 | Are there any anomalies affecting the team's velocity? (i.e, unplanned staff outages, new personnel, OPs issues, etc). Provide details regarding any major OPS issues. | One of our developers lost internet connection several times this sprint. We completed more than what was committed. | Note: This link opens the JIRA Velocity Report in a new browser tab. |
4 | Which objectives are (on/off) track for the PI, or moving (faster/slower) than expected? | All of our objectives are on track. |
Note: Include a Version Report Gadget for each JIRA project in the Team Board. |
5 | What will you be working on in the upcoming sprint? (Include any contract deliverables) Provide plan for any spillover work not finished in current sprint. | EDSC-2718 is the only one that is getting carried over. | Goals - PI Objective Sprint Goals:
Maintenance/Bugfixes Incomplete Work
Upcoming Work OBJECTIVES:
MAINTENANCE:
Contract Deliverables
|
6 | Has the schedule shifted for any of your dependencies (either giver or receiver)? If yes, please list. | No. | Upcoming Dependencies OPEN:GIVER:RECEIVER: |
7 | Do you have other concerns or questions for ESDIS or Train Leads? | No |