 |
Page History
| Page properties | ||||
|---|---|---|---|---|
|
Retrospective
| Panel | ||||
|---|---|---|---|---|
| ||||
Liked |
- List anything that went well in this sprint including shout out to others that went out of their way to help (add your name after your comment)
| Panel | ||||
|---|---|---|---|---|
| ||||
Disliked |
- List anything that we could have done better in this sprint (add your name after your comment)
- The release was a "risky release " : QA when signed off to prod , we did not have high confidence on the quality of the product , as we were scrambling till the last minute to finish the testing in stage .
- The Build was incorrect on stage which we were testing for all the DME changes and FS version was not matching that of QA .
- The DME was pointing to the dev Schema and we found out on the day of stage release this triggered a manual regression to be finished in 4 hours for a go no . We were lucky that nothing broke in production.
- After the "code freeze" we get "hot fixes" , if we are gettign daily one sometimes two build as " hot fixes " this defeats the purpose of code freeze. QA needs a stable build without any changes at least 3 days to have this confidence that everything is tested and no bugs will creep to production . Can we limit "hot-fix Builds to a maximum of two after code freeze?
| Panel | ||
|---|---|---|
| ||
Learned |
- List anything you learned about in this sprint (add your name after your comment)
Actions
