Sprint Review | Date | Demo Schedule |
---|---|---|
20.2.4 |
| 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. | yes. |
|
2 | How did things go last sprint (WIP, scope change, blockers, etc)? | 2 tickets being carried forward to the next sprint. Brought in 3 tickets and all were completed. 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. | None | 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 have been completed. |
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. | Auto Complete ACL and a design improvement issue for showing supported data formats are being 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 |