My personal experience working on this case study helped me better understand how complex managing technology systems can be in a large organization like a university. Before this project, I didn’t really think about how many different software applications are used across departments or how difficult it is to keep track of things like licenses, versions, and security. Breaking the project down into the six stages of project management made it easier to see how something this big can actually be planned and completed step by step.

One challenge I personally faced during this project was organizing all the information in a clear and structured way. At first, it felt overwhelming trying to connect everything—from stakeholders and security requirements to database design and risk management—without missing anything important. I had to go back and reorganize my work a few times before it started to make sense. That process was frustrating, but it helped me improve how I approach complex problems by breaking them down into smaller, manageable parts.

I also learned how important communication and planning are when working on IT systems. There are many different stakeholders involved, like IT staff, department heads, and compliance officers, and each group has different priorities. This showed me that technical knowledge alone isn’t enough—you also need to be able to explain ideas clearly and make sure everyone is aligned.