Close tickets in Planner (in addition to Assyst)



Close tickets

Lets check on the priority of the Bookmark incident

Bookmark incident ticket - when do i work on this ticket - BP

project contributors seamlessly moved in and out of sprints as needed

Pushing for Purkinje support for go-live day and $ecuring it

Great communication on implementation day

could possibly review the process or prerequisites for installing software in various non-prod environments i.e.
- downtime notice
- email comm before installing in VAL
- etc :)

We didn't dry run implementation plan

Pro active recommendations to the client: i.e. updating IUS and providing notes and screenshots for changes

Collaboration with the Health Services and DEIMS

Impact analysis should also include the CFHIS customs reports.

NO TICKETS ON CORE

Thorough testing, found a bug in production: Bookmarks column
Thanks to Arshia and HIAs for documentation and analysis

Team collaboration and folks stepping up to take on tasks and helping colleagues with testing, documentation etc

Team meetup / celebration
night

Installation procedures need to be updated to be less confusing between Server and client installs.
True for the KB Procedures as well.

Network connection worked well and no need to be on-site Carling.

Maybe we need a checklist for things to watch out for all releases i.e. DB changes and their impact

Server & Client Installations from previous v5.17 to v5.18 - Identifying the changes related to v5.18 is time consuming

No food takeout sent to homes of resources. ;P

Planning and getting all stakeholders grouped to work together.

Technical implementation went well

What went Well?

Plan for the holidays and check for teams availability

Collaboration.
Issues Identity and trouble-shooting.

Parking Lot Things

What can we improve on?

What did not go Well?