From: 2025-01-03

To: 2025-01-09

Scrum Master: Miguel Belchior

Product Owner: Alexandre Cotorobai

Developers: Joaquim Rosa, Hugo Correia, André Oliveira

Sprint Goal​

In order to complete this milestone of our project, it is expectable to conclude the following sprints goals:

• Buy Ticket - Persist in Ticket Service
• Access Ticket Information - User
• Create Tickets - Admin
• Edit Ticket - Admin
• List Purchased Tickets - Admin
• Validate Ticket
• List Created Tickets - Admin

Sprint Backlog​

Task Status (Completed/Not Completed)​

• SCRUM-24: Access Ticket Information - User
• SCRUM-46: Create Tickets - Admin
• SCRUM-21: Buy Ticket - Persist in Ticket Service
• SCRUM-47: Edit Ticket - Admin
• SCRUM-48: List Purchased Tickets - Admin
• SCRUM-50: Validate Ticket
• SCRUM-55: List Created Tickets - Admin

User Stories​

Team Velocity: 17

Sprint Review​

Sprint Retrospective​

What we did well​

In this sprint, we managed to complete all the logic related to the ticket service, that was the main goal of this sprint. With this, we concluded the goals for our project after the redeffinition of the project scope.

Sprint Burndown Chart​

From: 2024-12-20

To: 2025-01-03

Scrum Master: Hugo Correia

Product Owner: André Oliveira

Developers: Joaquim Rosa, Miguel Belchior, Alexandre Cotorobai

Sprint Goal​

In order to complete this sprint, we need to implement the following tasks:

• Access Ticket Information - User
• Create Tickets - Admin
• Admin Login and Registration
• Terraform
• List Created Tickets - Admin
• CI/CD Pipelines
• End-to-End Containerization

Sprint Backlog​

Task Status (Completed/Not Completed)​

• SCRUM-65: CI/CD Pipelines
• SCRUM-66: End-to-End Containerization
• SCRUM-53: Terraform
• SCRUM-49: Admin Login and Registration
• SCRUM-46: Create Tickets - Admin
• SCRUM-55: List Created Tickets - Admin
• SCRUM-24: Access Ticket Information - User

User Stories​

Team Velocity: 3

Sprint Review​

Sprint Retrospective​

Although we are behind schedule, we implemented the terraform, which was one of the main objectives of this sprint. We also implemented the user story for admin login and registration, CI/CD pipelines, and end-to-end containerization. The user story for listing created tickets - admin is in progress, and the user story for creating tickets - admin is in progress.

Sprint Burndown Chart​

From: 2024-10-28

To: 2024-11-11

Scrum Master: Joaquim Rosa

Product Owner: Alexandre Cotorobai

Developers: Miguel Belchior, André Oliveira, Hugo Correia

Sprint Goal​

In order to complete the second milestone of our project, it is expectable to conclude the following sprints goals:

• Access Ticket Information
• Admin Login and Registration
• List Purchased Tickets - Admin
• Create Tickets - Admin
• Deploy the project using Terraform

Sprint Backlog​

Task Status (Completed/Not Completed)​

• [] SCRUM-24: Access Ticket Information
• [] SCRUM-49: Admin Login and Registration
• [] SCRUM-48: List Purchased Tickets - Admin
• [] SCRUM-46: Create Tickets - Admin

User Stories​

Team Velocity: 0

Sprint Review​

Sprint Retrospective​

In this sprint, we were unable to complete any of the tasks due to a lack of time to invest in the project. We were working on other projects, and none of the team members could dedicate much time to this project. We tried to do the terraform for deploying the project, but we were unable to complete it. We were also unable to do the daily stand-ups; instead, we organized two short weekly meetings to discuss each team member's progress.

Sprint Burndown Chart​

From: 2024-10-14

To: 2024-10-28

Scrum Master: Hugo Correia

Product Owner: André Oliveira

Developers: Joaquim Rosa, Miguel Belchior, André Oliveira

Sprint Goal​

In order to complete the second milestone of our project, it is expectable to conclude the following sprints goals:

• Implement the first version of the Matches Page
• Update the Landing Page with the next match
• Implement the Games API
• Populate the Games DB
• Link the Backend with the Frontend
• Implement the Games API - Testing
• Implement the Frontend Tests
• Implement the Ticket microservice API
• Implement the Purchase ticket Page v1
• Implement the Backend Testing
• Implement the User logout implementation
• Implement the User logout testing - Backend
• Implement the Integration with Frontend
• Implement the User logout testing - Frontend
• Implement the Frontend Checkout
• Implement the Backend Checkout
• Implement the Checkout success and cancelled pages
• Implement the Payment Checkout

Sprint Backlog​

Task Status (Completed/Not Completed)​

• SCRUM-27: First Version of Matches Page
• SCRUM-28: Update Landing Page With the Next Match
• SCRUM-31: Games API
• SCRUM-37: Populate Games DB
• SCRUM-38: Link Backend with Frontend
• SCRUM-40: Games API - Testing
• SCRUM-43: Frontend Tests
• SCRUM-29: Ticket microservice API
• SCRUM-36: Purchase ticket Page v1
• SCRUM-39: Backend Testing
• SCRUM-32: User logout implementation
• SCRUM-33: User logout testing - Backend
• SCRUM-35: User logout testing - Frontend
• SCRUM-41: Frontend Checkout
• SCRUM-42: Backend Checkout
• SCRUM-44: Checkout success and cancelled pages

User Stories​

Team Velocity: 15

Sprint Review​

Sprint Retrospective​

What we did well​

We managed to complete all the tasks we had planned for this sprint. We were able to work together and help each other when needed. We also managed to have a good communication between the team members. We were able to have a good understanding of the tasks and the work that needed to be done. Understanding Stripe API and implementing the payment checkout was a big achievement for the team.

Sprint Burndown Chart​

From: 2024-10-10

To: 2024-10-13

Scrum Master: Alexandre Cotorobai

Product Owner: Miguel Belchior

Developers: Hugo Correia, Joaquim Rosa, André Oliveira

Sprint Goal​

In order to complete the second milestone of our project, it is expectable to conclude the following sprints goals:

• Prepare First Presentation
• Prepare the Initial Presentation Website
• Setup Backlog
• Set the "Definition of Ready"
• Set the "Definition of Done"
• Architecture

Sprint Backlog​

Task Status (Completed/Not Completed)​

• SCRUM-8: Landing Page - Frontend
• SCRUM-9: Landing Page - Testing
• SCRUM-10: AWS Cognito Setup
• SCRUM-11: AWS Cognito Setup
• SCRUM-12: API Authentication and Authorization
• SCRUM-13: Landing Page - PWA Support
• SCRUM-14: API Authentication and Authorization
• SCRUM-15: Landing Page - Little Refacture
• SCRUM-16: Backend Testing
• SCRUM-17: Link Back-end with Front-end
• SCRUM-18: User Login - Testing
• SCRUM-19: User Registration - Testing

User Stories​

Team Velocity: 7

Sprint Review​

Sprint Retrospective​

Despite the short length of this first sprint, we didn’t expect to deliver a large number of features. However, we were able to complete all the tasks we had planned. These include three user stories related to the user authentication epic: user registration, login, and the landing page.

Sprint Burndown Chart​

During the development of our application we spread the work to be done by sprints. Each sprint had a duration of 2 weeks (except the first one) and at the end of each sprint we had a meeting to discuss the work done and the work to be done in the next sprint.