Sprints 0 1 Retrospective
Due to the fact that Sprint 0 was, mostly, documentaring and of short duration, it will be, therefore, documented with Sprint 1. Futhermore, the pairings were maintained in order to promote the knowledge rotation, since only in Sprint 1 there were any coding.
- Planned activities were completed.¹
- Easily and quickly structured working environment.
- Chosen tools are efficient (PEP 8, IDE, Travis).
¹ Tests were not done, because we're still learning the technologies
- Two members left.
- Focus lack.
- Comunication failure.
- No tests.
- Activities Efficient Planning: The Scrum Master must be more active to compensate for the absence of the members.
-
Improve communication:
- Better use of communication tools.
- More frequent meetings.
- Google Drive Folder.
- Sprints as Milestones on Board.
- To study Pytest
