Content Comparison

...

Maintenance - Schedule Maintenance Window -

Status
colour Red title Incomplete

FRMS 3.1 - Deployment -

Status
colour Red title blocked by client

STG - Schedule Docker Engine Upgrade (Staging and Prod)

Status
colour Red title Staging complete

10KR - Hand off materials & Determine next steps -

Status
colour Green title complete

Documentation - Dev Skill Survey presented -

Status
colour Red title Incomplete

IIIF - PHP8 Upgrade -

Status
colour Green title complete

YSoA - Course Numbering Complete -

Status
colour Green title complete

YSB 4.3 - Complete Outstanding Work -

Status
colour Red title Incomplete

YSB 4.4 - Initial Research Complete (Login) -

Status
colour Red title Incomplete - Not started

Lotis FMS5 Server Update - Complete (2/26) -

Status
colour Green title complete

SDF - Code Cleanup Complete -

Status
colour Red title Incomplete

App Manager - 1.0 Release -

Status
colour Green title complete

OutSystems - Complete Platform Upgrades Across All Depts -

Status
colour Red title Incomplete

YPH-CEA - Deployment -

Status
colour Red title blocked by client

...

• jira

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

...

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

...

...

• What happened with Testing being blocked in YSB 4.3?

• Defects

  • YSB 4.3 - 25 defects

  • 21 Added throughout sprint

• What happened with OutSystems Upgrade planning - how can we plan better for future upgrades? How was work captured in Jira?

FRMS 3.1 - Deployment

...

From the beginning, this was a new feature that did not have existing OutSystems tools/components - a lot of things needed to be manually built

• Change implemented: Researching tasks

  • Lessons learned: more research will occur naturally throughout development

Ticket involves a lot of things.

• IE, “results page functionality” includes a lot of factors.

  • The table, editing, rendering, pagination

Everbridge Variables

• Example Incidents would have been helpful to have from the beginning

• Would allow for troubleshooting/debugging from the beginning for developers

• Lessons learned: developing test cases further in advance may help with debugging during initial development.

• Everbridge mapping was not available to QA was missing - that’s why testing was delayed

  • These were in confluence and in the original dev-only stories, but not in the testable stories

  • Possible documentation opportunity - Releases folder on Teams

    • This already exists on Confluence - don’t want to duplicate

    • Could we integrate into Fix Versions/Release Pages in Jira?

    • How can we make the information in confluence more accessible?

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

Like above, in 15031, there was a lot of testing different ways of implementing as the devs went.

• Changes cascade - One change to the page impacts the whole page.

Lessons learned: Drop Down Text

• In the future, we are set up for success with dropdown text - but there was a period of learning and experimenting that got us there (“Growing Pains”)

Shout Out - Advanced Search is a great example for future projects (and could be an awesome example for the CoP)

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

There were a lot of elements to modify.

CSS fixing and testing involves a lot of trial and error.

Lessons Learned: CSS as a language, especially within OutSystems, requires additional time to test and complete.

• How can we remember this during estimation?

  • Estimation Cheat Sheet with Lessons Learned- Created by Becki

Lessons Learned: AI Mentor Fixes may generate new, additional work that was not present during the initial estimation.

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

This was an issue where there was a mistype within the text of the ticket that caused multiple implementations.

Takeaway: Don’t be afraid to hop on a call

This is a lesson we are actually learning People have really improved on this

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

• Pair programming can be crucial but does take additional time.

  • It also acts as cross training and can eliminate code review.

• What happened with Testing being blocked in YSB 4.3?

• What happened with OutSystems Upgrade planning - how can we plan better for future upgrades? How was work captured in Jira?

Pride and Prejudice Sprint SHOUT OUTS!!!

• QA has been awesome at communication!

  • Checking in before making defects

  • Communicating when Defects are ready for estimation

• Ed has been handling fires and done a great job!

• Chris has done a great job on pair programming and training in the moment/cross training on maintenance tasks

• Kristian and Jesus for slaying defects for 4.3

• Responsiveness has been super quick and everyone has been very available for calls

  • #LetsAvoidDefects

• Nestor for cleaning up OLD Haunting tickets

• Nico for being back - we missed him

• Mauricio for being a proactive communicator and stepping up into a leadership role

FRMS 3.1 - Deployment

2h

Expand

FRMS - Enhancement - Detail by Department Report - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16077 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16102 3h 2h 45m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16103 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16104 15m 15m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16105 2h 2h Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16307 1h 30m By Agency Name report - Update Excel format - Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS- 16077 16449 Dev Subtask Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS- 16102 16482 3h 2h 30m 2h 45m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS- 16103 16483 30m 30m Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS- 16104 16484 15m 30m 15m 30m QA Subtasks Planned Actual Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS -16105

2h

-16457	30m
Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-16458	15m
Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-

16307

16456

1h 30m