Please enable JavaScript.
Coggle requires JavaScript to display documents.
Mobility2 Retrospective Sprint 21.2-1 - Coggle Diagram
Mobility2 Retrospective Sprint 21.2-1
What needs to improve?
Handling of mobile OS compatibility issues
Deployment/porting of completed item for specific environment (Dev/IE and Android/iOS)
Unclear process on the porting process
Devs doesn't have actual device to test their code
Additional QA for the team
Handling/scheduling of priority items
What went well?
Devs were able to help in testing items.
for the QA estimate of the item,
Dev will populate
QA will improve on his response to provide QA
WFH
better for OT(y) (weekend..holiday)
JAL AWR Backporting and support
JAL AWR porting done by 1 Dev, no dependency and naiiwasan ang conflict
Good dev support on BA parallel testing
JAL AWR User stories
Process for most workflows (porting, testing, etc) were better and clearer.
Team is open for change and able to help each other
What went wrong?
Clash of priorities
JAL and BAU priorities
Release notes for NFR configurations
Outdated OS of mobile phones for testing
Wiki of OS version for each client - will get this from BAs
DEV does not have an IOS device for JAL AWR
UI Porting issues.
During IE release, cause some defects/issues
Should somehow lessen this issue with new workflow - dev porting to IEs
E?S?V?P?
S
S
S
S
S