/
Sprint 1 Retrospective
Sprint 1 Retrospective
Retrospective
What did we do well?
- @Griff - We ran into unanticipated difficulties, but this felt like any programming project. Expect the unexpected.
- Chris Kirkwood-Watts - When we have very specific implementation tasks, we understand how to get that done, how long it will take, etc.
- Medha Parlikar (Unlicensed): Several team members met their sprint committment!
- Former user (Deleted): Story points seems to be working fine for him.
- Michael Stay (Unlicensed) -I feel that things went very well. Let's do it again.
What should we have done better?
- Chris Kirkwood-Watts -
- Weeks are not nearly as long as if we had explicit requirements. We are spending a lot of time talking about what we are going to do.
- Former user (Deleted) - In future, I should break out the research from the drawing up the documentation. I need to have compiled all the research before I execute on the documentation.
- Michael Stay (Unlicensed) - Allocate time at the end of the sprint to report on what happened, but reporting is part of the research task.
Actions
Related content
Sprint 4 Retrospective
Sprint 4 Retrospective
More like this
Sprint 3 Retrospective
Sprint 3 Retrospective
More like this
2018-03-26 Core sprint 5 retrospective
2018-03-26 Core sprint 5 retrospective
More like this
Sprint 5 Retrospective
Sprint 5 Retrospective
More like this
Core sprint 3 Retrospective
Core sprint 3 Retrospective
More like this
Core Sprint 11 Retrospective
Core Sprint 11 Retrospective
More like this