From Preparation to Participation: Our Experience Leading a Project Management Seminar
From Preparation to Participation: Our Experience Leading a Project Management Seminar
As a graduating Computer Science student, I have learned that building a system is not just about writing code. There are deadlines to meet, teammates to coordinate with, tasks to divide, problems to solve, and decisions to make along the way. Sometimes, the technical part is difficult, but managing the whole process can be just as challenging.
That is why conducting our seminar titled “Intro to Project Management” felt meaningful to me. It was not just another seminar requirement. It was a chance for us, as GC BitBarkada, to share something useful with younger Computer Science students and help them understand a skill that they will definitely need as they move forward in the program.
The seminar was held on May 13, 2026, at Gordon College, Room 508, with BSCS 1C as our audience. The main talk was titled “Architecting Success: A Student’s Guide to the IT Project Management Lifecycle.”
At first, I honestly felt unsure about how the seminar would go. The room was quiet, and fewer than fifty students were present when we started. As someone helping conduct the event, that kind of beginning can make you nervous. You start thinking whether the students will participate, whether the discussion will feel alive, or whether the seminar will go the way we planned.
But as the program continued, more students came in. Slowly, the atmosphere changed. Students began listening, responding, and joining the activities. What started as a quiet room eventually became a more active and engaging seminar.
That moment reminded me that not every event starts perfectly, but it can still end meaningfully.
Why Project Management Matters
The seminar focused on the importance of project management in IT. One of the biggest points discussed was that a project does not succeed just because the code works. A good IT project needs planning, organization, communication, teamwork, and proper execution.
As students, we often focus on the output. We want the system to run, the design to look good, and the features to work. But behind every successful project is a process that keeps everything organized.
Without project management, even a good idea can become confusing. Tasks may overlap, deadlines may be missed, and team members may misunderstand their responsibilities.
That is why the topic was very useful for BSCS 1C students. They are still early in their Computer Science journey, so learning about project management gives them a better foundation before they face bigger projects in the future.
The Project Management Lifecycle
One of the most important parts of the seminar was the discussion about the five stages of the project management lifecycle.
The first stage is Initiation, where the team defines the project and identifies the problem it wants to solve. This stage is important because it answers the question: Is this project worth doing?
The second stage is Planning, where the team creates a clear roadmap. This includes the project scope, task breakdown, schedule, and possible risks. Personally, I think this is one of the most important stages because poor planning usually leads to stress later.
The third stage is Execution, where the actual work begins. This is where coding, designing, testing, and building happen. But even during execution, communication is still important because everyone needs to stay aligned.
The fourth stage is Monitoring and Control, where the team checks progress and makes sure the project stays on track. This includes tracking deadlines, managing changes, and checking the quality of the output.
The final stage is Closure, where the project is completed, documented, and handed over. This stage also includes reflecting on what went well and what can be improved.
Listening to the discussion made me realize that these stages are not only for professional projects. Even students can use them for capstone, group activities, research, and system development tasks.
Conducting the Seminar as a Graduating Student
Since I am already in my fourth year, conducting this seminar felt different. It made me think about how much I have learned throughout college and how useful it is to share those lessons with students who are just starting.
When you are close to graduating, you begin to see things differently. You realize that the skills you need after college are not only technical. Yes, programming is important. But communication, time management, leadership, adaptability, and teamwork are just as important.
That is what made this seminar valuable. It reminded the students that being in IT is not only about building systems. It is also about delivering solutions properly.
As one of the organizers, I also saw how important preparation is. Conducting a seminar requires coordination, planning, program flow, materials, speaker preparation, audience engagement, and backup plans. In a way, organizing the seminar itself was also an example of project management.
We had to plan, execute, monitor, and close the event properly.
Student Participation and Seminar Flow
One thing I appreciated during the seminar was how the students became more involved as the session went on. At first, the atmosphere was quiet, but the icebreaker helped loosen the mood.
The icebreaker questions were simple and relatable, such as asking what app they would use for the rest of their life or how much of a digital citizen they think they are. These kinds of questions helped make the students more comfortable and prepared them for the discussion.
The Q&A portion also gave students a chance to ask about project management, ICT in education and careers, responsible technology use, and tips for BSCS students.
Another fun part was the cash giveaway game. It added excitement to the seminar and encouraged the students to listen carefully. Activities like that may seem simple, but they help keep the audience engaged, especially in a classroom setting.
Even though some students had to leave halfway because of classes or other important commitments, the seminar still continued smoothly. The remaining students participated, listened, and made the session worthwhile.
What I Realized from the Experience
This seminar reminded me that conducting an event is not always easy. There are moments when things do not go exactly as expected. The audience may be smaller at first, some participants may leave early, and the energy in the room may take time to build.
But what matters is how you handle the situation.
As an organizer, you still have to continue, adjust, and make the most out of the event. That is something I learned from this experience.
I also realized that project management is something we do more often than we think. We use it when we organize seminars, create systems, prepare reports, manage deadlines, and work with other people.
For me, this seminar was not only about teaching students what project management is. It was also a reminder that we are already practicing it in real life.
A Few Things We Can Improve
Although the seminar went well, there are still things that can be improved next time.
First, it would be better to coordinate the schedule more carefully so that more students can attend and stay until the end. Some students had valid reasons for leaving, but better timing could help improve full participation.
Second, we can make the beginning of the seminar more energetic. Since the room started quietly, a stronger opening activity could help students engage right away.
Third, adding a short hands-on activity would make the topic more memorable. For example, students could create a mini project plan or identify risks in a sample IT project. This would help them apply the lesson instead of only listening.
Still, even with these small challenges, the seminar achieved its purpose.
Final Reflections
Overall, conducting the Intro to Project Management seminar was a meaningful experience for me as a graduating student.
It reminded me that IT projects require more than technical knowledge. They require planning, teamwork, communication, patience, and discipline. It also showed me that organizing a seminar is already a form of project management because it involves preparation, execution, and adjustment.
I am glad that we were able to conduct this seminar for BSCS 1C students. Even if the session started quietly, it eventually became engaging and productive.
If there is one lesson I will take from this experience, it is this:
A successful project does not happen by accident. It happens when people plan properly, work together, and stay committed until the end.
And as a graduating Computer Science student, that lesson feels very real—because whether in school, work, or life, success always needs both skill and direction.
Comments
Post a Comment