Sprint Review | Date | Demo Schedule | Sprint Health (Current Active Sprint) |
---|---|---|---|
20.3.2 |
| Data Use PI 20.3 Demo Schedule | Scope change is due to the tickets that were brought in from last sprint. |
Question | Response | Dashboard Gadget | |
---|---|---|---|
1 | Did the team complete all of last sprint Goals? Explain any goals that did not complete. |
|
|
2 | Does the team have any blockers? |
| Blocked Tickets
|
3 | Are there any dependencies that are delayed for the last sprint? | The UMM-Var 1.7 work in the CMR is taking a little longer than originally anticipated, but it looks like it will be in SIT by Tuesday or Wednesday morning. That should be OK, for search to be able to complete its tickets. | Delayed Dependencies |
4 | What work related to PI Objectives will you be working on in the upcoming sprint? |
| Upcoming PI Work OBJECTIVES:
|
5 | Which objectives are (on/off) track for the PI, or moving (faster/slower) than expected? | 1 CMR ticket is complete and the other is in a pull request. 2) EDSC is starting to lag behind on the harmony integration. |
Note: Include a Version Report Gadget for each JIRA project in the Team Board. |