Sprint #: 38/39
Date:
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 |
|---|---|---|
Good relationship building for the client | feedback from Farhan that progress is slow, GTP UI is slow, Recording is slow, and it is NOT related to the computer. | issues aren't being resolved. we have partial successes and then issue re-appears. |
Farhan is very patient and spending lots of time with us(+1) (+2) | don't have visibility on status of issues | build doesn't have version number, having OnPremise<5>.rar looks unprofessional, looks like we don't have build process. |
team is working very hard (+2) | 2x daily scrums stopped being effective. | takes a long time to do manual operations on the machine -> need scripts or automation |
Team work on STC is great (+1) | don't have a build creation process automated, can’t tell build version | |
Start on Playwright (+2} | ahmer can't pull code and create build on his local, means he is always stuck on dependency | |
Glad that our team has been handling STC-related implementations and testing exceptionally well. | It's unfortunate that we can't test getting OTP via the database since we don't have valid credentials. | |
UI/UX Progress is good (+2) | ||
Team is being patient enough to explain the QA ecosystem on the certain flow which i was sceptical about. | My hope was to have larger participants of our team to have more interaction so that the outcome would be better compared to what we have now, sharing the thought process would help us more to leverage the experience. | |
Team is allocating time to get on call and brainstorm on the ux designs. | STC | STC(+1) |
Talks about PlayWright and enhancing locators (+2) | ||
Implemented JWT | ||
Fruitful Discussion on Playwright | ||
Team is back (+2) | ||
Added ODBC for STC | ||
S.No | Action Items |
|---|---|
1. | |