This repository has been archived by the owner on Jan 30, 2023. It is now read-only.
Sprint 5 Retrospective #303
jeremystocking
started this conversation in
General
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Things that went well:
As far as things that went well, sprint 0-4 went well. Hardly any hang-ups, a lot of good collaboration, good communication, and barely any excuses with this group. In sprint 0 we made some solid strides out of pure excitement for the project. By the end of Sprint 4 we had a product that our sponsor was quite impressed with. With such a strong start, our team felt very comfortable going into sprint 5. We decided it was not the best idea to start any new goals that would be left unfinished or could break our great functioning product. This sprint we primarily focused on deliverables, hand-off, code cleanup and presentation preparation.
Things to do better:
Having group members move from the database to the back-end to the front-end to testing comes with a learning curve. Ultimately, we could have best utilized our resources by having each developer assigned to one area and focused more on collaborating.
Carryover:
We don’t have to touch the project board from this point but we have until the deliverable deadlines to finish our pitch video, project hand-off and presentation. Project handoff, pitch video, and presentation are still on the table but we have no worries about those being ready.
Beta Was this translation helpful? Give feedback.
All reactions