/
2018-05-31 Sprint 220 Retrospective
2018-05-31 Sprint 220 Retrospective
Date | May 31, 2018 |
---|---|
Participants | @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) @Former user (Deleted) |
Retrospective
What did we do well?
All the issues were worked on the sprint plus a few extra
Worked after hours on FB issue
Caught up on code reviews
Good response time on FB issues
Did all our standup meetings this week
What should we have done better?
Direct deposit bug for batch count
Try to reduce technical debt
Bad unit tests (allowed bad results to get through)
Actions
@Former user (Deleted) @Former user (Deleted) Document the payment process
@Former user (Deleted) How can we reduce technical debt? One sprint or two during 3 month period, one person a sprint or whenever. Entire team to create Jira task issues when coming across technical debt code.
, multiple selections available,