Content Comparison

...

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

...

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

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-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 3.5h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16121 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16122 15m 0m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16067 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16068 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16069 20m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16070 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16230 1h 0m 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. Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16123 3h 5h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16124 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16125 15m 15m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16065 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16066 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16063 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16064 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16220 1h 0m 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 Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16126 3h 4h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16127 30m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16128 15m 15m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16059 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16060 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16061 20m 20m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16062 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16218 xx 0m 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 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15598 1d 1d Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15599 30m 45m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15600 30m 30m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15601 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15602 3h 3h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15603 25m 25m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15604 3h 3h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16228 1h 0m 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 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15590 8h 7h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15591 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15592 30m 30m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15594 3h 3h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15595 15m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15596 3h 2h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15956 1h 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15593 30m 30m 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 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15582 8h 2.5h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15583 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15584 30m 0m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15585 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15586 3h 3h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15587 15m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15588 3h 3h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15729 30m 30m Proposal by Preparer Report - Drop-down/multi-select - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15559 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15560 8h 6h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15561 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15562 30m 30m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15575 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15576 2h 2h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15577 15m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15578 3h 3h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15669 1h 1h

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

...

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

Dev: Yale Directory SPA -

...

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 Defects and Bugs - 5 Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15918 8h 10m 7h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15887 1h 30m 1h 45m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15886 4h 2h 45m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15885 2h 30m 2h 45m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15882 1h 30m 1h 45m

YSB: Advanced Search Hamburger Menu

...

Add the "Advanced Search" button to the "Hamburger" navigation button for mobile devices. -

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

-

Status
colour Green title Complete

Status
colour Yellow title Not on schedule

...

Dev Subtask

...

Planned

...

Actual

Lessons Learned 4.2:

• Development Team - Removed Button Functionality

  • Challenge Assumptions and smoke test functionality (Edit and Add button)

• Development and QA Team - Pre-deployment validation and smoke testing

  • Dedicated pre-launch smoke testing of environment to be deployed (load test)

Lessons Learned 4.3:

• Development Team - New functionality built for the first time - very difficult to estimate and plan for

  • How can we “revisit” things - getting things working != the best, most maintainable version

Wins 4.3:

• Development Team - Additional research tasks are being identified during refinement to help normalize

• Communication around issues has improved

YSB: Advanced Search Hamburger Menu

Expand

Add the "Advanced Search" button to the "Hamburger" navigation button for mobile devices. - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15780 - Status colour Green title Complete Status colour Yellow title Not on schedule Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15781 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15829 15m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15782 15m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15783 30m 30m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15824 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15825 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15826 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15827 45m

Tip-o-the-hat: Kristian Rivera-Santiago for identifying and proactively working on issues that he discovered during development and testing

CEA: Finish Print View -

Expand

CUS-14899 - PDF Export Truncating data - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14899 Closed, work continued on other tasks. Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14965 4h 6h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14966 4h 19h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14967 30m 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14968 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 Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14900 20m 1h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14901 30m 0m CUS-15400 - CEA - Create Printer friendly view - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15400 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15401 2h 3h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15402 4h 8h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15403 30m 0m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15404 30m 30m QA Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15414 30m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15415 2h 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15680 2h TO DO Defects - 3 Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15675 5h 20m 7h 20m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15676 3h 2h 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15677 4h 45m 9h 30m QA A11y Defect - CEA - CO2 Emissions Analysis - Action on buttons does not change the focus - WCAG 2.0 - OPERABLE - 2.4.3 Focus Order - Level A Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-13302 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15064 0m 6h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-13317 16h 39h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-13315 15m 15m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15239 45m 45m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-13316 15m 15m QA Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14097 30m xx Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-13303 45m 30m

Lessons Learned:

• Team Thoughts: Perfection is not always an attainable or the best outcome

  • Our team was trying to fix issues that were present in the charting library

• Dev and QA team - Opportunities to test lost throughout feature development

  • As charts were developed, report was not tested

  • By the time we reached the end, there were significant changes implemented

• Dev Team - Planning for Research and creating research subtasks is very important.

• Dev Team - Let’s develop best practices around PDF reports and accessibility and implement them during the initial design process

  • IE, we don’t need to print buttons, drop downs, etc

• Dev Team and QA - for highly complex or have gone back and forth to testing many times, 1:1 meetings between testers and devs can be very helpful

• Team Thoughts:

  • Can we get UI/UX feedback on features that have given us trouble?

    • PDFs, Excel Exports, Charts

FMP - FMS1 Update 2/6

Expand

FMP fms1 Server pre-upgrade support - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15746 - Status colour Green title Complete Status colour Yellow title Not on schedule Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15791 6h 6h 16m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15792 6h 5h 20m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12416 16h 7h 35m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12417 3h 20m FMP fms1 server upgrade - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15747 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12053 4h 2h 46m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15749 4h 1h 20m FMP fms1 server post-upgrade support - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-15748 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12054 4h 2h 35m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12209 8h 2h 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-12047 8h 15m

...