Sprint goals | Deliveries | Burndown | Backlogs
We have a challenge to automate the journey of files stored in cloud "A", performing a transfer to cloud "B".
The requirements (both customer and educational institution) covered for the first sprint are:
- RF 01: Construction of the API that will fetch the files that must be sent to the Cloud.
- RF 02: File API connection (Google Drive and AWS S3)
- RF 03: Download files and transfer from Cloud to Cloud.
- RF 04: Create downloaded file history screen
- RNF 11: Tests (Fatec Requirement)
- RNF 12: Implement CI/CD (Fatec Requirement)
- RNF 13: Documentation (Fatec Requirement)
🔗 Click the link below to view the Kanban of team activities:
We created the API that transfers files from Google Drive to AWS S3 automatically, the application queries new files every 1 minute.
Upon entering, the user is directed to the home screen, with buttons that will forward to other functions of the system.
On this screen, the user will be able to access the list of files through the button, in the future the dashboard for data analysis will be implemented.
We made a history of the files transferred to AWS S3, through the listing, the user will be able to view the metadata of the files that were transferred in real time.
To extract and understand the customer's wishes, an initial prototype was built in Figma, creating the visual identity and design of the system, the layout was validated by the customer.
🥷 Click here to view the project wireframe.
We modeled the database to relate the tables, as shown below.
🔗 Click here to view the model documentation logical.
In order to make better use of each member's skills, the team was separated into two fronts: frontend and backend, where, in the first sprint, the frontend team was responsible for making the prototype, frontend design and integration of features while the team the backend was responsible for creating the necessary services and identifying the metadata that will be stored in the dashboard in the future.
- The monitoring of activities, the responsibility of the Scrum Master, is shown in the image below, which contains the Burndown chart generated by the team (where the X axis is the days worked in the sprint and the Y axis values represent the deliveries and efforts made with the passage of time), including the activities carried out and those responsible for them.
- Graph updated on 04/02/2023
