Sprint 52/53 GTP Retrospective Analysis

Date: Jan 29, 2025

GLAD Things that have worked very well and made team very happy	SAD Disappointments, things that has not worked as well as hoped	MAD Things that didn't work well wasted a lot of time

GLAD Things that have worked very well and made team very happy	SAD Disappointments, things that has not worked as well as hoped	MAD Things that didn't work well wasted a lot of time
Migration scripts prepared
Great to see the GTP Azure environments set up with nearly all functionalities and Playwright integration
First Production released with new infra
	Team downsizing may over burdened +1
Glad that demo went well with mass.
Glad that we have completed the Switch tab and windows and if/else feature.
Glad we are at completion of feature’s needed for swbc	Worried that team's also being engaged with other tasks , due to which its becoming tuff to prioritise feature’s needed for now.
		Getting hit from everywhere




if/else and switch windows are in the dev most of the major stuff for migration is done new dev and prod are up and stable	if/else and switch windows are not in the prod

S.No	Action Items

S.No	Action Items
1.	We need to conduct testing on Azure and the GTP Application with approximately 10 concurrent users to ensure system stability and performance. Additionally, there are speed issues related to Lazy Loading of locators, which need to be identified and resolved to improve efficiency.
	It is also important to review the team's workload and align priorities for ongoing tasks. The discussion should focus on product development, SWBC, ServiceNow, and Classbuddy interactions to ensure that all activities are properly managed and completed on time.