Sprint Goals

FRMS 3.1 - Close remaining feature stories -

Status
colour Green title Allocated Complete

Status
colour Yellow title New work added

Yale Directory - Deploy to all environments and get ISO to re-scan -

Status
colour Green title Complete

TAR - Deploy TAR Changes -

Status
colour Green title Complete

YSB - Complete advanced search functionality -

Status
colour Red title incomplete

YSB - Add Advanced Search to Hamburger Menu -

Status
colour Green title DEV Complete

Status
colour Red title Not QA Complete

YPH-CEA - Identify solution for PDF Report issue -

Status
colour Green title Complete

FMP - FMS1 Update 2/6 -

Status
colour Green title Complete

YIM - Faculty Web Interface Complete -

Status
colour Green title Complete

SoA - Planning Complete -

Status
colour Green title Complete

App Manager - Deploy to Production -

Status
colour Green title Complete

Status
colour Yellow title issues identified

SDF - Complete Architecture Documentation -

Status
colour Red title incomplete

SDF - AI Mentor Studio Testing complete -

Status
colour Red title incomplete

IIIF - Goal TBD -

Status
colour Red title incomplete

FAS - 2.5.4 Feature Complete -

Status
colour Green title Complete

UI/UX - Review Figma updates -

Status
colour Red title incomplete

UI/UX - Review Poster Board -

Status
colour Red title incomplete

All planned work will be completed by 2/12, including development and testing -

Status
colour Red title incomplete

FRMS 3.1 - Close remaining feature stories

...

Update the sort on the In Progress by Due Date report -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16046

Added after the sprint started.

...

Dev Subtask

...

Planned

...

Actual

...

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16120

...

3.5h

...

General team feedback:

Checkboxes and Gherkin Method

• Devs - continue to look out. Positive feedback and helpful change

• QA - Helpful to imagine possible outcomes

What prevented us from getting the planned work done?

• Priorities changed during the sprint - YIM Application - Client needs reprioritized

• Not enough research planned for new features

  • Defects and stories

• Issues found pre-deployment - additional testing by Dev and QA in advance of deployment

• Support issues came up but tasks were not removed

• SDF Work fallen through the cracks due to team turnover - Luis handover

  • Offboarding process? Documentation as work is completed?

FRMS 3.1 - Close remaining feature stories

30m

Expand
Update the sort on the In Progress by Due Date report - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS- 16121	30m

16046

Added after the sprint started.

Add the Department Column to the Completed by Preparer report -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16045

-

Status
colour Green title Complete

Added after the sprint started.

Add the Department Column to the Completed by Preparer report -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16044

-

Status
colour Green title Complete

Added after the sprint started.

Dev: In Progress by Due Date with Comments Report - Drop-down/multi-select -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15597

Status
colour Green title Complete

In Progress by Due Date - Drop-down/multi-select -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15589

Status
colour Green title Complete

Completed by Preparer Report - Drop-down/multi-select -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15581

Status
colour Green title Complete

Proposal by Preparer Report - Drop-down/multi-select -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15559

Yale Directory - Deploy to all environments and get ISO to re-scan

Expand
Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12848 Dev: Yale Directory SPA - Several tasks created

Lessons Learned:

• Development Team - Versioning can be more complex than a simple check - make sure to estimate accordingly and share with the team.

  • Review code before estimating

• Development Team and QA - Versioning requires additional testing that we are not currently executing

• Development Team - Versioning - Post-launch cleanup of versioning needs to be planned for for Dev and QA team (smoke test)

  • Every release should include a post-launch task of version clean up

• QA Team - Prioritize stories that are ready for UAT to provide time for client changes.

Wins:

• QA team anticipated possible client feedback and helped work proactively on potential issues.

Yale Directory - Deploy to all environments and get ISO to re-scan

Expand

Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12848 Dev: Yale Directory SPA - Several tasks created initially that were closed - significant rework to ticket needed. Dev Story Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12848 8h 5h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15571 - Dev: Create GitHub Action to Publish Directory Docker Images to Harbor Dev Subtasks Planned Actual https://yaleits.atlassian.net/browse/CUS-15572 2.5h 2.5h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15573 45m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15574 45m 30m Dev: Deploy Latest Directory Image to All Environments for ISO Rescan - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15757 Dev Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15758 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15759 30m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15968 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15760 1h 1h 1h

Lessons Learned

• Process reliant on external teams & will require CAD to drive

TAR - Deploy TAR Changes - No tickets

Wins:

• Slam dunk! Fast deploy with no issues.

YSB - Complete advanced search functionality

...

Expand
See detailed breakdown and Retro Feedback: YSB 4.2 Deployment Retro

YSB: Advanced Search Hamburger Menu

CEA: Finish Print View -

Actual

Expand
CUS-14899 - PDF Export Truncating data - Defects and Bugs - 5 Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS- 14899 Closed, work continued on other tasks.	Dev Subtask	Planned

15918	8h 10m	7h
Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-

14965

15887

4h

1h 30m

6h

1h 45m

Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-

14966

15886

4h

19h

2h 45m

Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-

14967

15885

2h 30m

1h

2h 45m

Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-

14968

15882

1h 30m

1h

QA Subtask

Planned

Actual

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15240

1h

4h

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15348

CLOSED

CLOSED

45m