Repository navigation
Weekly Meetings
unbot2313 edited this page Oct 15, 2026
·
7 revisions
Record of the team's weekly meetings. Each member answers the same three questions. Newest meeting first.
Date: 2026-10-15 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Updated the data model diagram and documented the table relationships in Deliverable 3 |
| What are you going to do this week? | Start FR31, the integration of different AI providers into the analysis, and help record the video |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Updated the component diagram with the new reports and notifications applications |
| What are you going to do this week? | Review the architecture section of Deliverable 3 and prepare the architecture part of the video |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Finished FR29, sending the analysis report by email through n8n, and wrote most of Deliverable 3 |
| What are you going to do this week? | Work on FR32, the not found page, and update the README and the usability principles page |
| Are there any obstacles? | None |
- Close the documentation of Deliverable 3 before the Sprint Review.
- Record the video with the pitch, the requirements of this sprint and the demo of the new features.
- Add FR31 (integration of different AIs) and FR32 (not found page) to the backlog for the next sprint.
Date: 2026-10-08 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
Progress review and planning session. The team went over the state of Sprint 3 — what was already merged and what was still pending — and agreed on how to continue with the remaining requirements and Deliverable 3.
| Question | Answer |
|---|---|
| What did you do last week? | Tested the visual identity and the loading states in the application after they were merged |
| What are you going to do this week? | Update the data model section of Deliverable 3 |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Checked that every view uses the shared design tokens after the switch to the dark theme |
| What are you going to do this week? | Update the component diagram for Deliverable 3 |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Reviewed the n8n integration used for the password recovery emails |
| What are you going to do this week? | Finish FR29, the analysis notification email, and continue the Deliverable 3 page |
| Are there any obstacles? | None |
- Summary of the sprint so far: FR28, FR30 and UR08 are done and merged; FR29 and UR07 are still pending.
- Split the sections of Deliverable 3: architecture and data between Tomas and Miguel, corporate image, repository and project management with Alessandro.
- Finish the pending requirements before starting new features.
Date: 2026-10-01 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Designed the GeoRank logo, applied the dark theme and redesigned the topbar and footer |
| What are you going to do this week? | Add a loading state while a website is being analyzed (UR08) |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Defined the shared design tokens so that all the views use the same colors and spacing |
| What are you going to do this week? | Review the views after the visual identity changes |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Moved the report creation into the reports application (FR30) and sent the password recovery email through n8n (FR28) |
| What are you going to do this week? | Work on FR29 and start the Deliverable 3 page in the wiki |
| Are there any obstacles? | None |
- Apply the visual identity — logo, color palette and dark theme — to all the views.
- Register UR08 in the backlog: show the user that the analysis is running.
- Start the Deliverable 3 page in the wiki.
- Completed the pending requirements carried over from Sprint 1
- Split functionality across separate applications/modules
- Proposed several ideas for future app updates
- All planned updates were implemented successfully with no major issues
- All pending issues for the sprint were closed
- Feature split across applications improved modularity
- No backlog items were created for features planned for upcoming sprints
- Security considerations were not defined with enough specificity
- Commit conventions were not consistent across the team
- Log all discussed feature ideas and new requirements into the backlog as they come up, not after the fact
- Define specific security requirements/factors for upcoming sprints (auth, data validation, access control, etc.)
- Agree on and document a unified commit message convention (e.g., Conventional Commits) for the team to follow
Date: 2026-09-24 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Went over the ideas left from the Sprint 2 retrospective and turned them into candidate requirements for Sprint 3 |
| What are you going to do this week? | Review the pull requests of the new requirements and support the definition of the visual identity |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Reviewed the templates and styles of the application to find inconsistencies between the views |
| What are you going to do this week? | Define shared design tokens so that all the views use the same colors and spacing |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Wrote the new requirements for Sprint 3 and registered them as issues in the backlog |
| What are you going to do this week? | Work on FR28, FR29 and FR30, and start the usability principles page |
| Are there any obstacles? | None |
- Add FR28, FR29, FR30 and UR07 to the backlog as the scope of Sprint 3.
- Move the report creation out of
analysisinto its own application (FR30). - Define the visual identity of GeoRank — logo, slogan and color palette — and apply it through shared styles.
Date: 2026-09-17 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Went over the Sprint 2 retrospective with the team and reviewed the state of the code after the delivery |
| What are you going to do this week? | List improvement ideas and candidate requirements for the next sprint |
| Are there any obstacles? | Less time available because of other courses |
| Question | Answer |
|---|---|
| What did you do last week? | Went over the email and PDF features delivered in Sprint 2 to look for possible improvements |
| What are you going to do this week? | Review how consistent the styles are across the views |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Wrote the Sprint 2 retrospective on the wiki |
| What are you going to do this week? | Draft the new requirements for the next sprint |
| Are there any obstacles? | None |
- No new development this week; the time is used to plan Sprint 3.
- Each member brings proposals for new requirements to the next meeting.
- Keep following Conventional Commits, as agreed in the retrospective.
Date: 2026-09-10 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Moved the settings to environment variables, generated requirements.txt from the lockfile and completed the Deliverable 2 page |
| What are you going to do this week? | Go over the retrospective action items with the team |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Finished and merged the PDF export, the analysis email notification, the password recovery and the company-level access to reports |
| What are you going to do this week? | Go over the delivered features to look for possible improvements |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Worked on the Deliverable 2 page and added requirements.txt
|
| What are you going to do this week? | Write the Sprint 2 retrospective on the wiki |
| Are there any obstacles? | None |
- Close Sprint 2 with all 39 requirements Done.
- Hold the Sprint 2 retrospective and record it on this page.
- Log new feature ideas in the backlog as they come up, and agree on a single commit message convention for the team.
Date: 2026-09-01 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
Session held with the project monitors. The team discussed the limitations of the project, the definition of the target users, and a configuration issue found in the code.
| Question | Answer |
|---|---|
| What did you do last week? | Developed the competitor registration and comparison |
| What are you going to do this week? | Apply the points raised by the monitors |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Reviewed the requirements assigned for this sprint |
| What are you going to do this week? | Continue with the assigned requirements |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Reorganised the applications and worked on the sector recommendations |
| What are you going to do this week? | Continue with the assigned requirements |
| Are there any obstacles? | None |
- Discuss with the monitors what the team considers to be the limitations of the project.
- Define who the target users of GeoRank are, and who they are not.
- Fix a configuration value that was exposed in the code instead of being read from the environment.
Date: 2026-08-24 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Propose and independently develop new features for the application |
| What are you going to do this week? | Continue testing and developing the features |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Apply the requirements suggested by the monitors |
| What are you going to do this week? | Finish developing the remaining requirements in the backlog |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Perform the separation of the project into different applications |
| What are you going to do this week? | Working on the wiki and conducting driving tests |
| Are there any obstacles? | None |
- Present the project and its current progress to the mentors in the next meeting.
- Complete the outstanding requirements.
Date: 2026-08-17 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
Session held with the project mentors. The team presented GeoRank and explained the scope of the product and the current state of the development.
| Question | Answer |
|---|---|
| What did you do last week? | Continued the development of the application |
| What are you going to do this week? | Apply the feedback received from the mentors |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Worked on the assigned requirements |
| What are you going to do this week? | Apply the feedback received from the mentors |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Reviewed and tested the application |
| What are you going to do this week? | Apply the feedback received from the mentors |
| Are there any obstacles? | None |
- Present the project and its current progress to the mentors.
- Apply the clarifications and recommendations given by the mentors.
Date: 2026-08-13 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Continued the development of the application |
| What are you going to do this week? | Review the prioritisation of the requirements |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Updated the project documentation |
| What are you going to do this week? | Continue with the assigned requirements |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Reviewed the deliverable and tested the application |
| What are you going to do this week? | Continue testing the application |
| Are there any obstacles? | None |
- Review the MoSCoW prioritisation of the requirements.
- Define the development order of the remaining requirements.
- Distribute the remaining requirements among the team members.
Date: 2026-08-06 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Worked on the main functionality of the application |
| What are you going to do this week? | Continue with the development of the application |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Worked on the deliverable |
| What are you going to do this week? | Work on the presentation slides |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Worked on the deliverable |
| What are you going to do this week? | Work on the presentation slides |
| Are there any obstacles? | None |
- Define the elevator pitch of the project.
- Distribute the presentation slides among the team members.
- Review the progress of each member's development work.
Date: 2026-07-30 Attendees: Tomas Ramirez Galeano, Miguel Angel Alzate Osorno, Alessandro Soccol Mejia Absent: —
| Question | Answer |
|---|---|
| What did you do last week? | Update the project wiki and develop deliverable 1 |
| What are you going to do this week? | Begin with the development of the basic functionalities of the project |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Update the project wiki and develop deliverable 1 |
| What are you going to do this week? | Establish the specific requirements that Georank will have |
| Are there any obstacles? | None |
| Question | Answer |
|---|---|
| What did you do last week? | Update the project wiki and develop deliverable 1 |
| What are you going to do this week? | Establish the specific requirements that Georank will have |
| Are there any obstacles? | None |
- Distribute the sections of the deliverable among the team members
- Begin the project development work
- Establish the specific requirements of the project
- Divide the GeoRank explanatory video into sections.
| # | Task | Owner | Due date |
|---|---|---|---|
| 1 | Begin the development of the project's code. | Tomas | 2026-08-06 |
| 2 | Complete the section 2 of the deliverable | Miguel and Alessandro | 2026-08-06 |
| 3 | Create an explanatory video for the project | All team members | 2026-08-06 |
Next meeting: 2026-08-06