 |
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)
- The team came together and we worked towards a workflow to deploy microservices that works for all projects based on the experience we had (Amit Mukherjee).
- Although, there is room for improvement the team worked hard to get the release out the door and I'm very proud of the work that was accomplished (Kuffel, Gina (NIH/NCI) [C] )
- Shout out to Fleming, Michael (NIH/NCI) [C] for helping the ICDC team navigate the ICDC Release process. Mike did a great job coordinating with the CloudOne team and keeping the Release Dashboard updated (Kuffel, Gina (NIH/NCI) [C] ).
| 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 on stage .(Laxmi Lolla)
- The Build was incorrect on stage which we were testing for all the DME changes and FS version was not matching that of QA .( Laxmi Lolla)
- 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.( Laxmi Lolla)
- After the "code freeze" we get "hot fixes" , if we are getting daily one sometimes two builds 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?( Laxmi Lolla ) .
- Under Estimation of the code Complexity to implement Facet Value ui Display "label". Number of Search Faceted Sections and Facets item of Data Explorer Navigator should be capped. (Rana, Ambar (NIH/NCI) [C] )
| Panel | ||
|---|---|---|
| ||
Learned |
- List anything you learned about in this sprint (add your name after your comment)
- We needed an elegant way of microservice version management and hand-off across different tiers.(Amit Mukherjee)
Actions
- Revisit the timeframes of code freeze and testing timeframes
- Investigate the idea of a "Code Slush" prior to the actual "Code Freeze"
