On October 17, 2026, I reached another meaningful milestone in my Master of Science in Information Technology (MSIT) journey at Bulacan State University as I delivered my first graduate school presentation. Through a 43-slide discussion on Project Time Management, I explored how understanding activities, dependencies, networks, and durations can transform the way we plan, coordinate, and successfully deliver Information Technology projects.
My First Presentation, Another Step in My Graduate School Journey
“A deadline is not a plan, and a busy team is not always a productive team.”
This was one of the most important lessons I wanted to share during my first graduate school presentation on October 17, 2026, as a Master of Science in Information Technology (MSIT) student at Bulacan State University (BulSU).
For our IT Project Management subject, I was assigned to discuss a portion of Chapter 6 of Kathy Schwalbe’s Information Technology Project Management, focusing on the fundamental concepts of Project Time Management.
Through a 43-slide presentation, I explored four essential components of effective project scheduling: defining activities, identifying dependencies, understanding project schedule networks, and determining activity durations.
Rather than presenting these concepts as isolated definitions, I wanted to create a discussion that would help my fellow graduate students understand their significance in actual IT projects.
Using storytelling, practical examples, diagrams, and reflective questions, I connected the principles of project scheduling to situations commonly encountered in software development and Information Systems implementation.
As someone who is now balancing the responsibilities of being a college instructor and a graduate student, this presentation became more than another academic requirement.
It was an opportunity to challenge myself, strengthen my understanding of project management, and continue developing my ability to communicate technical concepts with clarity and purpose.
Time Is Limited, but Effective Planning Makes It Meaningful
I began my discussion with a thought-provoking statement attributed to renowned management thinker Peter Drucker:
“Time is the scarcest resource and unless it is managed nothing else can be managed.”
This quotation provided an important foundation for the entire presentation.
In almost every IT project, time is one of the most critical resources. Organizations may acquire additional funding, hire more personnel, or invest in better technologies, but they cannot recover the time that has already passed.
Yet, even with sophisticated project management tools and experienced teams, many projects still struggle to meet their deadlines.
This raises an important question: Are projects delayed simply because teams do not have enough time, or because the work itself has not been properly understood, organized, and coordinated?
I wanted my classmates to recognize that project time management is not merely about creating schedules, assigning deadlines, or encouraging team members to work faster.
It begins with understanding the activities required to complete a project, recognizing how those activities depend on one another, and determining how available resources and constraints affect their completion.
Having a deadline does not necessarily mean having a plan.
A project team may know when a system must be delivered, but without a clear understanding of the work required to reach that deadline, the schedule becomes little more than an expectation.
Bringing Project Management Concepts to Life
To make the discussion more practical, I introduced a case involving Sue Johnson, a project manager featured in Schwalbe’s textbook, and the challenges associated with developing an online student registration system for a university.
The project involved creating a system capable of supporting student enrollment, subject selection, class schedules, and online registration.
However, the project faced a critical deadline of May 1, along with several challenges that threatened its timely completion.
University representatives were not always available for consultations, important approvals were delayed, and the unexpected resignation of a senior programmer created additional staffing difficulties.
As development activities began falling behind schedule, delays in one area threatened to affect other tasks that depended on their completion.
I encouraged my classmates to imagine themselves as members of the project management team responsible for addressing these challenges.
What would happen if the database design were delayed? Could the development team proceed without approved requirements? Would assigning more programmers necessarily solve the problem? How could one delayed activity affect the entire project?
These questions helped establish the connection between theoretical project management principles and the realities of managing complex IT initiatives.
Throughout the presentation, I revisited this scenario to explain how activities, dependencies, network diagrams, and durations influence project performance.
One lesson became increasingly clear:
Project delays do not always mean that people are not working hard enough. Sometimes, the real problem is that the work has not been properly planned, sequenced, or coordinated.
Understanding the Work Before Managing the Time
The first major part of my discussion focused on defining project activities.
I explained that a broad instruction such as “Develop the Student Registration System” is insufficient for creating a realistic project schedule.
Although it describes an expected outcome, it does not identify the specific tasks required to produce that outcome.
For example, developing a student registration module may involve gathering requirements, designing the database, developing the user interface, integrating components, and conducting system testing.
Each activity requires different resources, technical competencies, and amounts of time.
I also discussed the relationship between the Work Breakdown Structure (WBS) and activity definition, emphasizing that the WBS organizes the project’s deliverables and work packages, while activity definition identifies the specific actions needed to complete the work.
To provide a clearer understanding, I introduced the importance of activity lists, activity attributes, and milestone lists in organizing project responsibilities and tracking important accomplishments.
I also explained progressive elaboration and rolling wave planning as approaches that allow project teams to refine their plans as additional information becomes available.
The central message was straightforward:
Before we can estimate how long a project will take, we must first understand what needs to be accomplished.
Recognizing How One Delay Can Affect Everything
The next part of my presentation focused on activity dependencies, or the logical relationships that determine how project activities should be sequenced.
I explained that not every task can be performed independently or simultaneously.
Some activities must be completed before others can begin, while certain tasks may proceed in parallel depending on technical requirements and project constraints.
Our discussion explored mandatory, discretionary, and external dependencies, as well as four common activity relationships: Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish.
Using examples from software development, system testing, deployment, and IT operations, I illustrated how these relationships affect project schedules.
For instance, certain system integration activities cannot proceed until the necessary components have been developed. Similarly, deployment may depend on successful testing, required approvals, and the readiness of the organization’s infrastructure.
I connected these concepts to Sue Johnson’s project, where delayed stakeholder approvals and the loss of an experienced programmer created consequences beyond the activities directly affected.
This reinforced an important lesson about coordination:
A delay rarely exists in isolation. When activities are interconnected, one problem can influence the progress of an entire project.
Understanding these relationships helps project managers anticipate risks, recognize scheduling conflicts, and make better decisions before minor delays become significant project setbacks.
Seeing the Bigger Picture Through Project Networks
One of the more technical portions of my presentation involved Project Schedule Network Diagrams, which visually represent the relationships and sequences among project activities.
I introduced two approaches: Activity-on-Arrow (AOA) and the Precedence Diagramming Method (PDM), also known as Activity-on-Node (AON).
Through textbook figures and simplified illustrations, I explained how activities and their relationships can be represented using arrows, nodes, and boxes.
I also discussed the concepts of bursts and merges, which help describe how project activities branch into parallel work and later converge.
To make the discussion easier to visualize, I developed a simplified example involving six activities required to implement a student registration system.
The activities began with requirements gathering, followed by database and user interface design, system development and integration, testing, and deployment.
I demonstrated how some design activities could proceed simultaneously, while integration would depend on the completion of the required components.
This example helped illustrate why network diagrams are more than visual representations of tasks.
They allow project managers to understand the relationships among activities, identify potential scheduling challenges, and evaluate how delays may affect the project’s overall progress.
A project schedule network helps us see not only what each team member is doing, but also how individual efforts contribute to the completion of the entire project.
Understanding That Effort and Duration Are Not the Same
The final technical concept I introduced was activity duration, particularly its distinction from effort.
Although these terms are sometimes used interchangeably, they represent different aspects of project work.
Effort refers to the amount of work required to complete an activity, while duration refers to the time period over which that activity is completed.
For instance, a programming task may require a certain number of work hours, but its actual duration can depend on the developer’s availability, competing responsibilities, and other project constraints.
I also emphasized that adding more people to a task does not always reduce its completion time proportionally.
Technical complexity, coordination requirements, waiting periods, external approvals, and resource limitations can all influence the duration of an activity.
This discussion established the foundation for my presentation partner’s succeeding discussion on duration estimation and other project scheduling techniques.
More importantly, it completed the connection among the four concepts I had explored.
Activities tell us what work must be done. Dependencies explain the required sequence. Network diagrams help us visualize the relationships. Durations allow us to understand the time needed to complete the work.
Together, these concepts provide a stronger foundation for developing realistic and effective project schedules.
Making Technical Discussions More Meaningful
Beyond the project management concepts themselves, another important part of this experience was reflecting on how I wanted to deliver my presentation.
As a college instructor, I am accustomed to preparing learning materials and explaining technical concepts to students. However, presenting to fellow graduate students provided a different opportunity to develop these skills.
I wanted the discussion to be informative without becoming unnecessarily complicated.
Rather than relying entirely on textbook definitions, I organized the presentation around a realistic project scenario and gradually introduced each concept as part of a connected discussion.
I used storytelling, case-based examples, reflective questions, visual diagrams, and practical IT applications to make the lessons more relatable.
I also incorporated both English and Filipino in my explanations, particularly when clarifying technical relationships and emphasizing practical interpretations.
For me, effective communication is not simply about presenting accurate information. It is also about helping the audience understand why that information matters.
A presentation becomes more meaningful when listeners can connect what they are learning to situations they may encounter in their academic, personal, or professional lives.
This experience reminded me that knowing a concept and communicating it effectively are two different competencies, both of which require continuous practice and improvement.
When the Teacher Becomes the Student Again
One of the most meaningful aspects of this milestone is the perspective it brings to my continuing journey as an educator and graduate student.
In my regular teaching responsibilities, I stand before students to facilitate discussions, explain concepts, and guide their learning.
But in graduate school, I also find myself on the other side of the classroom—listening to professors, learning from classmates, preparing academic requirements, and challenging my understanding of concepts I have yet to fully master.
Experiences like this remind me that teaching and learning are not separate journeys.
They continuously influence and strengthen one another.
Preparing for my first graduate school presentation required me to revisit technical concepts, examine their practical implications, and think carefully about how they could be communicated to others.
In doing so, I was not only preparing to share information. I was also strengthening my own understanding of the subject.
Sometimes, one of the most effective ways to discover how much we have learned is to challenge ourselves to explain that knowledge to someone else.
As I continue pursuing my Master of Science in Information Technology, I hope to embrace more opportunities that challenge both my technical knowledge and my communication skills.
I recognize that becoming a better educator requires me to remain a committed learner, just as becoming a better graduate student requires discipline, curiosity, and the willingness to accept constructive feedback.
There is still much for me to discover and improve, but milestones like this remind me that growth does not always have to come from extraordinary accomplishments.
Sometimes, it comes from preparing one presentation, explaining one unfamiliar concept, or becoming a little more confident in sharing what we know.
Gratitude for the Opportunity to Learn and Share
I would like to express my sincere appreciation to our IT Project Management professor for providing us with the opportunity to explore important project management concepts and develop our understanding through academic presentations and discussions.
To my presentation partner, thank you for the collaboration and for contributing to our shared discussion.
I am equally grateful to my fellow MSIT graduate students at Bulacan State University for being part of this learning experience.
Having the opportunity to exchange perspectives, explore technical concepts, and learn alongside individuals with different professional experiences makes graduate education especially meaningful.
I also remain thankful for the people who continue to support and encourage me as I balance my responsibilities in teaching and postgraduate studies.
This first presentation may represent only a small step in my MSIT journey, but it is a milestone I appreciate because of the effort, preparation, and lessons that accompanied it.
Lessons That Extend Beyond IT Project Management
As I reflected on my discussion, I realized that the principles of project time management are relevant not only to IT projects but also to how we approach many of our responsibilities in life.
We often set deadlines for ourselves, whether for academic requirements, professional goals, personal plans, or long-term aspirations.
But establishing a deadline is only the beginning.
Without identifying the steps we need to take, understanding the resources available to us, and recognizing the challenges that may affect our progress, our goals can remain difficult to achieve.
Likewise, being constantly busy does not necessarily mean we are moving in the right direction.
We can spend considerable time and energy completing tasks while overlooking whether those efforts contribute meaningfully to our objectives.
This is why thoughtful planning, prioritization, communication, and coordination remain essential.
Effective progress requires us to understand not only what we want to accomplish, but also how we intend to accomplish it.
As future IT leaders and professionals, we must learn to recognize that project success depends not simply on how quickly individuals complete their assigned work, but on how effectively their efforts are organized toward a common goal.
Good project management is not about asking people to work endlessly or move faster. It is about creating the conditions that allow people to work effectively, collaboratively, and with a clear sense of purpose.
A First Presentation, A Lasting Reminder
I concluded my presentation by returning to the central message introduced at the beginning of our discussion:
“Before we can effectively manage time, we must first understand the work that fills it.”
Looking back on this experience, I recognize that my first graduate school presentation taught me lessons that extend beyond the technical principles of project scheduling.
It reinforced the importance of preparation, the value of clear communication, and the responsibility of translating complex ideas into understandable and practical knowledge.
It also reminded me that every academic opportunity is a chance to improve—not only in terms of professional competencies, but also in confidence, discipline, and the ability to contribute to the learning of others.
As I continue navigating my journey as both an instructor and an MSIT student, I hope to carry these lessons into my classroom, future academic engagements, and professional responsibilities.
There will certainly be more presentations to prepare, concepts to understand, and challenges to overcome.
But for now, I am grateful for this first milestone and the opportunity it gave me to grow.
Success is not simply about meeting deadlines, completing tasks, or staying busy. It is about understanding our objectives, organizing our efforts, working meaningfully with others, and making decisions that move us closer to the outcomes we hope to achieve. Time may be limited, but thoughtful planning gives direction to how we use it. Whether we are managing a project, pursuing an academic degree, building a career, or working toward our personal aspirations, progress becomes more meaningful when every action serves a clear purpose. May we learn to value not only how much we accomplish, but also how wisely we plan, how responsibly we lead, and how effectively we turn our efforts into results that matter.
Here’s to the lessons that challenge our thinking, the experiences that strengthen our confidence, and the opportunities that remind us that becoming better professionals begins with remaining committed learners.
Because in project management, as in life, the goal is not merely to finish on time—it is to move forward with purpose, direction, and a clear understanding of what truly matters. ⏳🎓💙