Content Comparison

...

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

...

Dev Subtask

...

Planned

...

Actual

...

...

4h

...

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-1490915033

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

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-

...

1h

...

• 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

...

5h

...

8h 15m

• 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?

  -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

...