/
2019-02-28 Sprint 256 Retrospective
2019-02-28 Sprint 256 Retrospective
Date | Feb 28, 2019 |
---|---|
Participants | @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) |
Retrospective
What did we do well?
Try to stay focused on a single task (i.e. programming)
What should we have done better?
Missed our velocity quite a bit and added several issues mid-stream on the sprint
Found a bug that suggests the sers new hire report may have never worked
Need to make sure these sorts of reports have been adequately tested including test submissions to the reporting entities if applicable
we should also have file comparison tests in place where possible to prevent regressions
Actions
, multiple selections available,
Related content
2019-01-31 Sprint 252 Retrospective
2019-01-31 Sprint 252 Retrospective
More like this
2019-01-03 Sprint 248 Retrospective
2019-01-03 Sprint 248 Retrospective
More like this
2019-05-16 Sprint 267 Retrospective
2019-05-16 Sprint 267 Retrospective
More like this
2019-05-02 Sprint 265 Retrospective
2019-05-02 Sprint 265 Retrospective
More like this
2018-11-29 Sprint 244 Retrospective
2018-11-29 Sprint 244 Retrospective
More like this
2019-01-10 Sprint 249 Retrospective
2019-01-10 Sprint 249 Retrospective
More like this