Retrospective and planning after iteration 2¶

Date: 26.03. 2021, 15:00 & 27.03. 2021 17:00
Present: Jan Pašek, Michal Seják, Stanislav Král, David Friesecký

Agenda¶

1. Each of the team briefly evaluates the pros and cons of the iteration based on the following points: project state, project plan, team cooperation, tools, artefacts
2. What shall be better in the next iteration?
3. How did we managed to change problematic points from the previous retrospective?
4. Other problems
5. Evaluate if we achieved the iteration targets
6. Synchronization discussion (short standup)
7. Planning of the next iteration

Conclusion¶

1. Standa - Internal communication and cooperation were OK, communication with the customer was delayed, which caused redundant work on AIA extensions.
2. Honza - Internal work of the team was OK, hopefully, the customer will cooperate better next time. Bigger decisions such as software architecture shall be discussed via a call instead of author-reader review. This cause unnecessary reworking of the architecture.
3. Michal - architecture shall be discussed together next time and such tasks shall be planned for more people than one - more people involved means more knowledge.
4. David - DB proposal said that he delivered the DB proposal later than he wanted. The team agreed that it caused no error, so no measures are necessary.
5. The project achieved LCOA milestome
6. All iteration targets were met.
7. The problem with git->issue was fixed, everyone follows the conventions.
8. Discussion about the final architecture was done in the whole team.
9. Next iteration was planned - Target is to deliver a minimal functionality enabling the user to create and download certificates using a simple web gui.