Skip to end of metadata
Go to start of metadata
You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
Version 1
Next »
- 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