Skip to content

Releases: FontysResIT/ResIT

Delivery Sprint 4

02 Jun 13:51
42a713b
Compare
Choose a tag to compare

1. Sprint goals

  • Finalize microservices
  • Connect to group 1's service bus
  • Deploy to k8s on Fontys Netlabs
  • Set-up monitoring
  • Performance and load testing

2. Sprint achievements

  • Implement restaurant configuration service
  • Connect to group 1's service bus
  • Deploy to k8s on Fontys Netlabs
  • Set-up monitoring
  • Performance and load testing
  • Finalize research

3. Project management tooling

For the management of the project, we made use of the software: "Trello".

You can find our board using the link underneath.

https://trello.com/b/Uu6rtvxL/s-rb03-resit

4. Documentation

Our documentation can be found in our GitHub repo in the folder "docs".

5. CI/CD

We have made a CI/CD pipeline with Gitflow. This pipeline will automatically perform a sum of actions: First it will check out the repository. After this the pipeline will build a Docker image with GO and Gin. Furthermore, it will check if the unit tests pass. At last, it will push the Docker image to Heroku for staging.
The pipeline can be found here.

6. Repository

Our repository can be found using the link underneath.

https://github.com/RealSnowKid/ResIT

7. Presentation

Our presentation for the sprint delivery can be found here.

8. Retrospective + planning next sprint

Both the retrospective and the planning for the next sprint can be found in canvas after the sprint review.

Delivery Sprint 3

12 May 12:09
a11f340
Compare
Choose a tag to compare

1. Sprint goals

  • Establish better communication with other groups concerning the connectivity.
  • Connect to group 1's service bus
  • Set up a gateway
  • Already prepare connecting to the other groups
  • Have a meeting with Kees, informing him of our vision for the project and appsemble

2. Sprint achievements

  • Implemented more functionality
  • Split up the project into different microservices + updated C4
  • Set up a gateway
  • Worked on the messaging bus
  • Started research towards deployment with Kubernetes
  • Have had a general meeting with Kees about Appsemble

3. Project management tooling

For the management of the project, we made use of the software: "Trello".

You can find our board using the link underneath.

https://trello.com/b/Uu6rtvxL/s-rb03-resit

4. Documentation

Our documentation can be found in our GitHub repo in the folder "docs".

5. CI/CD

We have made a CI/CD pipeline with Gitflow. This pipeline will automatically perform a sum of actions: First it will check out the repository. After this the pipeline will build a Docker image with GO and Gin. Furthermore, it will check if the unit tests pass. At last, it will push the Docker image to Heroku for staging.
The pipeline can be found here.

6. Repository

Our repository can be found using the link underneath.

https://github.com/RealSnowKid/ResIT

7. Presentation

Our presentation for the sprint delivery can be found here.

8. Retrospective + planning next sprint

Both the retrospective and the planning for the next sprint can be found in canvas after the sprint review.

Delivery Sprint 2

14 Apr 13:10
d968b0a
Compare
Choose a tag to compare

1. Sprint goals

  • Come up with an architecture and the according diagrams
  • Conduct research towards different topics
  • Build a walking skeleton
  • Have some sort of demo already in the sprint delivery

2. Sprint achievements

  • Created a C4 model and an ERD and kind of validated it already in the sprint delivery
  • Set up a CI/CD pipeline
  • Conducted research in different topics
  • Created a roadmap
  • Create a basic application with minimal features
  • Created an ethical design report
  • Created test plan and test matrix
  • Created misuse cases
  • Defined a techstack

3. Project management tooling

For the management of the project, we made use of the software: "Trello". You can find our board using the link here.

4. Documentation

Our documentation can be found in our GitHub repo in the folder “docs”.

5. CI/CD

We have made a CI/CD pipeline with Gitflow. This pipeline will automatically perform a sum of actions: First it will check out the repository. After this the pipeline will build a Docker image with GO and Gin. Furthermore, it will check if the unit tests pass. At last, it will push the Docker image to Heroku for staging.
The pipeline can be found here.

6. Repository

Our repository can be found using the link underneath.
https://github.com/RealSnowKid/ResIT

7. Presentation

Our presentation for the sprint delivery can be found here.

8. Retrospective + planning next sprint

The plans for next sprint can be found at the start of the next sprint on our Trello SCRUM board under the Sprint Backlog column.

Delivery Sprint 1

24 Mar 10:50
Compare
Choose a tag to compare

1. Sprint Goals

  • Generate both functional and non-functional requirements
  • Create use cases as well as a use case diagram
  • Conduct research to the viability of Appsemble within the context of the project
  • Make a start on the architecture

2. Sprint Achievements

  • Generated both functional and non-functional requirements
  • Created use cases from those requirements and included them in a use case diagram
  • Concluded research and gave reasons to move away from Appsemble
  • Made a start on the architecture
  • Made a start on the design of the front-end

3. Project Management Tooling

For the management of the project, we made use of the software: "Trello". You can find our board using the link here.

4. Documentation

Our documentation can be found in our GitHub repo in the folder "docs".

5. Repository

Our repository can be found using the link here.

6. Presentation

Our presentation for the sprint delivery can be found here.

7. Plans for Next Sprint

The plans for next sprint can be found at the start of the next sprint on our Trello SCRUM board under the Sprint Backlog column.

Delivery Sprint 0

24 Feb 13:37
Compare
Choose a tag to compare

1. Sprint goals

Our goals for sprint 0 were to first get a clear view of the current situation in dinner in motion, after that we planned on coming up with a solution that tackles one of the problems we addressed. Finally, we would start with the set-up of the project as well as making a start on the documentation.

2. Sprint achievements

After having analyzed the current situation and having ideated about possible solution for a certain problem, we realized that we should divide the big picture into small sufficient projects for each group. We ended up with the reservation part.
From here we started with setting up a scrum board, so that we can work in a structured manner. Now we begun expanding the project plan, which in the end has reached a decent level. Furthermore, we also already ideated about the user stories. We have thought of the existing features we think need to remain, as well as new ideas for expansion. We prioritized these user stories; however, we have not discussed them yet with the client.

3. Project management tooling

For the management of the project, we made use of the software: "Trello". You can find our board linked here.

4. Documentation

Our documentation can be found in our GitHub repo in the folder “docs”.

5. Repository

Our repository can be found using the link here.

6. Presentation

Our presentation for the sprint delivery can be found here.

7. Retrospective + planning next sprint

Both the retrospective and the planning for the next sprint can be found in canvas after the sprint review.