Retrospectives - Ga-3tan/AMT_Project GitHub Wiki

Restrospective 28.01.2022 - Final Report

To Keep

The team works well together, there have been many discussions regarding development choices, techniques and best practices. There were no major delays or major failures in the system developed.

Communication tools :

  • Discord

Scrum tools :

  • IceScrum

Dev frameworks and implementation of them :

  • Spring Boot
  • Spring Security
  • Thymeleaf
  • LoomBook
  • JUnit
  • Tomcat
  • Github actions CI

Environment Docker Docker helped us a lot in the deployment phase of the microservice, the aws machine we were working on had a lot of constrains with denied permissions and required authorizations. Docker allowed us to avoid all these problems and save a lot of time. In a second project we will start directly with this tool.

Reworks

Couchbase is deployed on the server but is not working properly :

  • Technical limitation (can't access to different collections, no clear resources/documentation to help with that)
  • Complicated/incomplete documentation
  • Time consuming

Workaround : switch to mongoDB or alternative

The current Continuous Deployment is not working and needs more time to troubleshoot :

  • Waiting for the help of the scrum master
  • Complicated infrastructure and low experience with CD

Workaround : has been judged non-essential for the moment, deployment is done manually

Lack of documentation and diagrams:

  • Technology choice in the wiki
  • Readme partially incomplete
  • Any diagram

Workaround : All these elements were carefully revisited and completed.

Lack of stand-up meeting :

  • We need to know more about who did what at the beginning of each working session
  • Write a log

Workaround : Try to be present and do a stand-up meeting at the beginning of the working session

Git old convention :

  • Slow and cumbersome methodology
  • Branches have to be named using a convention, which is often impractical for the programmer.

Workaround: We switched to using GitFlow to automate this process

Project security with Spring Security

  • Complex and difficult to implement

  • You can easily get lost in it

Workaround: Starting from a simple but functional base security, add more functionality slowly to this base.