/
2019-01-31 Sprint 252 Retrospective
2019-01-31 Sprint 252 Retrospective
Date | Jan 31, 2019 |
---|---|
Participants | @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) |
Retrospective
What did we do well?
Improved report performance by 3x on average
Directing priorities based on end user feedback
Turned around two critical hotfixes within hours
What should we have done better?
Ensure that we are fully testing all aspects of patches to make sure they cannot have negative impact and potentially prevent application startup
The fact that Kim is testing default for Q/A and not the actual release branch can cause issues when problems that are on default, but not the release branch are detected in testing.
Actions
, multiple selections available,
Related content
2019-05-23 Sprint 268 Retrospective
2019-05-23 Sprint 268 Retrospective
More like this
2019-01-10 Sprint 249 Retrospective
2019-01-10 Sprint 249 Retrospective
More like this
2019-05-16 Sprint 267 Retrospective
2019-05-16 Sprint 267 Retrospective
More like this
2019-01-03 Sprint 248 Retrospective
2019-01-03 Sprint 248 Retrospective
More like this
2019-05-02 Sprint 265 Retrospective
2019-05-02 Sprint 265 Retrospective
More like this
2018-11-15 Sprint 243 Retrospective
2018-11-15 Sprint 243 Retrospective
More like this