/
2018-01-25 Sprint 202 Retrospective

2018-01-25 Sprint 202 Retrospective

Owned by Former user (Deleted)
Last updated: Feb 01, 2018
1 min read





Date

Jan 25, 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?

  • Made progress on focusing on QA and testing issues as they are completed

  • Were much better on staying caught up on code reviews

  • Daily standups helped communication between offices and amoungst the team in general

  • Stayed fairly on top of ssdt-feedback with quick responses



What should we have done better?

  • Estimate issues more accurately to prevent issues spanning multiple sprints

  • Over committed to issues slightly for Sprint 202 (velocity was off)

  • Functional tests proved fragile and resulted in a long stretch of failed builds



Actions

Attempt to be more realistic in our estimates and throw values over 2 story points where applicable (make .5 mean extremely simple)
@Former user (Deleted) Possibly reduce velocity (first we will try to