Team Reflection - CampusEats

PLANNING

▶

Reflected by Imran Najwan for Requirement, Project Charter, Gantt Chart and CPM

This project was a steep learning curve in professional project management. Combining Requirement gathering with structured planning tools gave me a complete picture of the development lifecycle. The Requirement stage taught me how to filter and prioritize user needs, ensuring we were building the right product.

Taking those requirements and structuring them into a Project Charter gave the team a unified direction. But the most practical growth came from using the Gantt Chart and CPM. These tools transformed our timeline from a simple deadline into a dynamic strategy, helping us coordinate resources and prioritize critical tasks with zero slack. I am grateful for this holistic experience, as it equipped me with the confidence to not just build software, but to manage the complex ecosystem that surrounds it.

ANALYSIS REQUIREMENT

▶

Reflected by Ahmad Luqman about Feasibility Study and abstract from Project Charter

Developing the Feasibility Study for CampusEats was an insightful experience that bridged the gap between concept and reality. Initially, assessing the viability of a student led delivery workforce and real time mapping seemed complex, but the analysis allowed me to objectively evaluate the technical and operational requirements. It was rewarding to confirm that utilizing students as riders was not just a cost effective solution for the platform, but also a sustainable income model for our peers.

Simultaneously, drafting the Project Charter helped clarify the system's core direction and scope. Defining the features, such as the pre-order mechanism and vendor directory, required precise attention to ensure we addressed actual pain points like long queues. This process taught me the value of foresight in anticipating risks, such as order surges during peak hours and seeing the project transform into a structured, viable plan gave me a strong sense of accomplishment in our team's vision.

DESIGN

▶

Reflected by Suhayl Izzat about Conceptual and Physical for design

Reflecting on this project, my journey as the Website Designer was defined by the complex transition from Conceptual vision to Physical reality. In the beginning, the conceptual phase was limitless, filled with abstract ideas, sketches and a vision of how we wanted the user to feel. However, moving into the physical design phase required discipline. I had to translate those loose ideas into concrete, functional elements that users could actually interact with.

This process wasn't just about aesthetics, it was about problem solving. I am deeply grateful for the challenge of bridging this gap. It taught me that a great design isn't just about a beautiful concept, it is about the rigorous physical execution that ensures the interface is intuitive, responsive and true to our original goals.

IMPLEMENTATION & CONVERSION

▶

Reflected by Amir Nordin about Implementation Step and Parallel Conversion

Reflecting on the Implementation & Conversion phase, I gained a profound appreciation for the power of structured planning. Initially, the idea of migrating to a new system felt daunting, but breaking it down into distinct phases such as pre-implementation, parallel operation and full transition brought a sense of clarity and control.

I am particularly grateful for the parallel conversion strategy. Operating both systems simultaneously allowed us to identify discrepancies and gather real time feedback without the high risks of a sudden switch. It turned potential anxiety into a constructive process of refinement. This journey taught me that true system reliability isn't just about code, it's about the patience to synchronize data, the discipline to run parallel tests and the attention to detail required to ensure a seamless experience for the end user.

OPERATION & MAINTENANCE

▶

Reflected by Fadhil Haekal about Post Implementation Review & System Operation and Maintenance

For me, the Post-Implementation Review highlighted how effectively CampusEats simplifies the dining experience for the university community. Feedback from students and vendors was predominantly positive, particularly regarding the ease of skipping queues and the convenience of the delivery service, though it also identified areas where we could refine the user interface. While managing the project resources and staying within budget was a challenge, the system's eventual reliability and data security proved to be our strongest assets during the launch.

The maintenance phase further taught me the value of having a structured process specifically the importance of rigorous testing, analyzing user feedback, and prioritizing updates based on real needs. I realized that ensuring the security of payment data and maintaining a smooth user experience for both vendors and riders requires constant vigilance. Overall, this experience demonstrated that maintaining CampusEats is a continuous effort to ensure the platform remains effective and aligned with our mission to support campus life.

OVERALL REFLECTION

▶

Reflected by Affiq Fauzi about the Overall Project Journey

Building CampusEats was a defining experience that allowed us to bridge classroom theory with real world campus logistics. Developing a platform for students, vendors and riders pushed us to look beyond code and focus on the entire user ecosystem. We gained hands on experience in system design, learning exactly what is required to modernize dining processes and eliminate long queues.

Collaboration was the backbone of this project. Facing challenges like refining map integration and rider assignment logic strengthened our problem solving skills, while strict deadlines taught us the value of adaptability and clear communication. Relying on each other's strengths was essential to keeping such an interconnected system moving forward.

Ultimately, we are proud that CampusEats not only delivers food but also creates economic opportunities for student riders and helps vendors reach a wider audience. This journey has sharpened our technical abilities and inspired us to continue building solutions that make a meaningful difference in our community.

Thank you for taking the time to read through our reflections. We hope this provides insight into our development journey and growth throughout the CampusEats project. For further questions or collaboration opportunities, feel free to reach out through our university channels.

— The CampusEats Team

Imran Najwan, Ahmad Luqman, Suhayl Izzat, Muhammad Amir, Muhammad Affiq Hazriq, and Ahmad Fadhil Haeikal

Reflection of Our Team Members