Sprint Goals

FRMS 3.1 - Close remaining feature stories - Allocated Complete New work added
Yale Directory - Deploy to all environments and get ISO to re-scan - Complete
TAR - Deploy TAR Changes - Complete
YSB - Complete advanced search functionality - incomplete
YSB - Add Advanced Search to Hamburger Menu - DEV CompleteNot QA Complete
YPH-CEA - Identify solution for PDF Report issue - Complete
FMP - FMS1 Update 2/6 - Complete
YIM - Faculty Web Interface Complete - Complete
SoA - Planning Complete - Complete
App Manager - Deploy to Production - Completeissues identified
SDF - Complete Architecture Documentation - incomplete
SDF - AI Mentor Studio Testing complete - incomplete
IIIF - Goal TBD - incomplete
FAS - 2.5.4 Feature Complete - Complete
UI/UX - Review Figma updates - incomplete
UI/UX - Review Poster Board - incomplete
All planned work will be completed by 2/12, including development and testing - incomplete

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

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

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

YSB: Close all 4.2 tasks -

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

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 -

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

YIM - Faculty Web Interface Complete

YSoA - Planning Complete

SDF: Close all Maintenance Tasks-