Please enable JavaScript.
Coggle requires JavaScript to display documents.
Retrospective Bug Hunters Jul 24 - Aug 04 (Sprint 149) - Coggle Diagram
Retrospective
Bug Hunters
Jul 24 - Aug 04
(Sprint 149)
What actions are needed?
Anthony: Will confirm status on daily stand-up meeting
Tai: Take mongoDB related task, collaborate with Dat to learn more
Tai: Take notes of the mistakes so it will not happen again
Dat: Investigate card by myself. Follow the steps same with Anthony's discussion. Get review.
When testing, pair with Anthony
Dat: Be more careful in testing postman
Dat: When reporting bugs to DEV Team, ask when will it be fixed.
What needs improvement?
Tai: knowledge about mongoDB is still on basic level
Tai: minor mistake on input values in postman
Dat: get confused when creating test cases that involves AWS and Jenkins, don't know which test to cover
Dat: Bug fix is taking too much time
Anthony: Status of the google sheet was not updated everyday (first week)
Dat: created bug card but root cause was wrong parameter name during testing
What went well?
Tai: Me and Dat did staging test on time, we don't spend too much time on a card
Tai: Good communication with DEV Team
Dat: Sharing from Anthony about how to test including UI/AWS/mongoDB/Jenkins
Dat: Me and Tai can handle some test cases from postman, able to check if data is stored in mongoDB
Anthony: Members are proactive to ask questions about card's AC