CEREMONIES - JeanCarloLondo/SpectRA GitHub Wiki
Week 2: Contact with the Challenge Supervisor via Microsoft Teams
During this week, our team had the first formal contact with the professor in charge of the challenge through a Microsoft Teams. At this early stage, we still had limited knowledge about the full scope of the project, so we focused on clarifying expectations and understanding the general context of the challenge.
As part of our initial alignment, we brainstormed possible names for the project. After evaluating several ideas, we unanimously decided on SpectRA, a name that reflects both the augmented reality nature of the solution and the vision of offering a wide “spectrum” of information about the university campus.
In addition, we defined team roles according to skills and responsibilities, ensuring that each member had a clear function within the Agile Scrum framework. We also began our initial research on the problem, exploring potential technologies, reviewing existing AR solutions, and identifying possible user needs.
Week 3: Virtual Meeting with the Challenge Supervisor
This week was a turning point for the development of the project. During class, Professor Liliana shared with us her incredible idea: bringing augmented reality to the university campus. From the very first moment, we were excited about the concept and decided to base our project around it.
Previously, we had arranged a virtual meeting with the professor in charge of the challenge, and this week it finally took place. During the session, we introduced ourselves, the professor presented his vision, and he was open to hearing our proposal. By the end of the meeting, he agreed to our approach, giving us the green light to proceed.
With a clear understanding of the objectives, we began dividing tasks among team members through our WhatsApp group and virtual calls, ensuring that everyone had a defined responsibility moving forward.
Week 4: Reflection after the Presentation
During this week, our team continued with the normal rhythm of classes, but we also had an important milestone: our first presentation to the client and professors. Although we had worked hard and ensured that everything was technically correct, we realized that when it came to presenting, we got confused. This lack of coordination caused our presentation to look disorganized, with no clear order between team members.
We honestly felt embarrassed because we know we could have done better. However, this experience gave us an important lesson: it is not enough to have the work done, we also need to show it with confidence and structure. Despite these difficulties, we believe the client was quite satisfied with the results, as the core idea and effort behind the project were evident.
As a team, we are committed to improving our organization and communication for Sprint 1. We are motivated to learn from our mistakes and continue building something meaningful. At the end of the day, we recognize that we gave our best, and that is something we value deeply as a group.
Week 5: A Short Weekly due to Exams
This week was marked by midterm exams, so our team did not have as much time to meet or advance collectively. To adapt to the situation, we opted for a short weekly session where we mainly focused on distributing the pending work for Sprint 1.
The programmers began to explore and learn their respective technical tools to be ready for implementation. Meanwhile, the rest of the team, including roles such as design, documentation, and coordination, took the time to decide how to approach their pending tasks in a more effective way.
Even though the workload of exams reduced our availability, we remain confident that we are on the right track. These small steps, even during a busy week, help us stay aligned and ensure that everyone knows their responsibilities moving forward.
Week 6: Priorities from Other Courses
This week our team faced a common challenge for university students: balancing multiple academic responsibilities. Due to deadlines in other subjects, we had to temporarily shift our focus to preparing projects and assignments that required immediate attention.
As a result, we were unable to start the development phase as planned. However, we maintained communication through WhatsApp and ensured that each member was aware of their responsibilities for the upcoming sprint. Even if we did not make technical progress, this week allowed us to recharge and reorganize our agenda for what was coming next.
Week 7: Beginning the Development Phase
After the break from the previous week, this one marked the official start of development. The developers began coding the first functional components of SpectRA, exploring the use of AR frameworks and integrating them with our planned features.
Meanwhile, the rest of the team concentrated on improving documentation, refining diagrams, and ensuring that our vision was clearly aligned with the client’s expectations. We also held several virtual meetings to set concrete deadlines, redistribute tasks, and keep everyone on track.
Although progress was gradual, this week represented the turning point where ideas started to become a tangible product.
Week 8: Sprint Delivery Delayed
This week was originally designated for the delivery of Sprint 1. However, the reality of development presented several obstacles: unexpected bugs, a learning curve with the AR tools, and the pressure of other university projects and midterm exams.
Fortunately, the professors granted us an additional week to polish our work. This extra time gave us breathing room to stabilize the code and resolve critical errors. Despite the delays, we kept our motivation high and saw this situation as an opportunity to deliver a more complete and functional version of our MVP.
Week 9: Preparing the MVP Presentation
This was the most crucial week so far: the moment to present a Minimum Viable Product (MVP) of SpectRA. Our MVP focused on recognizing Building 19, one of the most iconic spots on the campus. Through our trained machine learning model, we were able to correctly identify the building and link it to the AR experience.
The team worked intensively on both the technical demo and the presentation narrative, ensuring we could showcase not only the functionality but also the vision of SpectRA as a scalable solution for the university.
We rehearsed several times to avoid repeating the mistakes of previous presentations, assigning clear speaking roles and preparing visual aids. The final result was a viable MVP that reflected the effort, collaboration, and resilience of the whole team.
Week 10: Reflecting on Sprint 1 Feedback
After presenting our first sprint, we took this week to carefully reflect on the feedback received from both the professors and the client. Their comments were incredibly valuable in helping us identify what worked well and what still needed improvement.
We were pleased to hear that our presentation had shown significant progress compared to Sprint 0 — especially in terms of structure, confidence, and visual clarity. The positive remarks motivated us deeply, as they confirmed that our efforts to improve communication and teamwork were paying off.
As a team, we took the time to analyze every piece of feedback, from technical suggestions to design and usability notes. This process allowed us to redefine priorities for the next development cycle. More importantly, it strengthened our sense of unity — we genuinely felt that SpectRA was no longer just an academic challenge, but a shared vision we were building together.
Week 11: Sprint 2 Planning and Task Assignment
This week marked the beginning of Sprint 2 planning. We gathered as a team to discuss new objectives, review the backlog, and clearly assign responsibilities based on each member’s strengths. The atmosphere during our meetings was collaborative and focused, as everyone was eager to contribute to the project’s next phase.
We organized development tasks around both new features and improvements suggested after Sprint 1. The developers aligned their goals for implementing the next AR functionalities, while the design and documentation teams prepared updated diagrams, user flows, and testing plans.
A highlight of this week was Daniel — our UX specialist — taking the initiative to start learning Unity. His enthusiasm to support the development team by bridging the gap between design and technical implementation truly exemplified our team’s growing synergy. By the end of the week, we had a clear roadmap and renewed motivation to bring SpectRA closer to its full potential.
Week 12: A Quiet Week with Academic Priorities
This week was relatively calm in terms of SpectRA’s progress, as most of us were occupied with demanding academic projects from other courses, particularly in telematics and systems engineering. Balancing multiple deadlines proved challenging, but we managed to maintain communication and ensure that everyone remained informed about upcoming sprint objectives.
Although technical development slowed down, we focused on finalizing pending documentation and refining our testing strategies. We also revisited the user stories to ensure consistency between the project vision and the practical implementation planned for the next sessions.
Even in a week with limited progress, our commitment remained firm. We saw this short pause as a necessary breather before diving into a more intense development phase in the following week.
Week 13: Final Preparations and Demo Readiness
This week represented the culmination of our efforts for Sprint 2. After weeks of planning, research, and coding, we finally reached a stage where SpectRA was ready for demonstration. The team conducted internal tests to verify that the main features — including building recognition, AR overlays, and interactive information panels — worked seamlessly and met performance expectations.
We also began preparing the pitch presentation, aiming to make it not only technically solid but also engaging and inspiring. Having learned from our earlier experiences, we prioritized clarity, storytelling, and visual coherence. Each team member took ownership of their segment, ensuring that our delivery would feel unified and confident.
There was a sense of excitement in the air — a mix of nerves and pride. Seeing SpectRA come to life through functional demos reminded us of how far we had come since those early brainstorming sessions. We closed the week with optimism and anticipation, ready to showcase the evolution of our project and the teamwork that made it possible.