They told me I was hired for a new project. Q2. Marifa Tech, with offices across Africa. My FullStack developer background, cloud certs, and that database migration I mentioned in the interview—they were the ticket. I thought I was coming in as a Cloud Developer. Then the offer letter changed. IT Project Manager. Just like that, the keyboard was replaced by a whiteboard, and the code editor by a project brief.
Project Atlas. Ten million customer records. A legacy SQL database, heavy with years, destined for a cloud-native CDP. Nine months. No margin for error. My first day, and I was neck-deep in the woods. The question burned: What does an IT PM do, really?
As a developer, I built. I knew the elegance of a clean architecture, the satisfaction of a deployed feature. Now, I was informed that my task was all about a concept referred to as the Project Management Iron Triangle – Scope, Cost, and Time, whose core was Quality. And the harsh reality: almost every third IT project fails miserably without an IT Project Manager. This wasn't about writing the code anymore; it was about making sure the code had a chance to live, to thrive, to deliver.
The Iron Triangle: My New Reality
It’s not abstract. It’s the air we breathe on Project Atlas.
1. Scope: Drawing the Line in the Sand
As a developer, I chased features. As an IT PM, I define the battlefield. For Atlas, the scope is clear: migrate 10 million records on a cloud-native CDP to real-time marketing. The devil, however, is always in the details. What is actually mission critical? Which integrations are required; not desired? My job is to carve out the achievable, to say "no" to the unnecessary, to protect the core mission from the endless expansion of wants. Devoid of a set limit, Atlas would turn into an expansive, endless project, a drain of resources and spirit. It is all about making sure that we build the right thing.2. Time: The Relentless Clock
Nine months. That is the hard deadline for Atlas. As a developer, I dealt with my sprint activities. As an IT PM, I am in charge of the whole project. This implies subdivision of the Atlas project into manageable stages: Initiation, Planning, Execution, Monitoring and Controlling and Closure. Every stage has milestones, its dependencies. To observe the entire clock, to predict the delays, to maintain the rhythm of the project is my business. It is about making sure that we get it done on schedule.3. Cost: The Fuel for the Journey
This isn't just about money. It is time, time of the developers, cost of the cloud resources, the opportunity cost of all delays. In the case of Atlas, each decision, each unexpected technical challenge, each misunderstanding, eats away at this price. I am supposed to watch this fuel, to have efficient utilization of this fuel, to have enough of this fuel to make it to the destination without causing bankruptcy or killing the team. It is the cold mathematics of resource distribution, the tough decisions that keep the project going.4. Quality: The Promise Delivered
Finally, it is about production of a product that works. A CDP that allows marketing in real-time, personalized, improves the customer experience, and allows better data-driven decision-making. It is the quality we assured. As a developer, and I was concerned with the beauty of the solution. As an IT PM, I would guarantee that the solution fulfills the business requirement, it functions as required, and it delivers a tangible value. It is the ultimate test of success the evidence that the trip was not in vain.
Project Lifecycle
This isn't just about the triangle; it's about the different phases of Project Management.
- Initiation: That first brief to Atlas. Providing an explanation of the purpose of doing so, a problem it resolves among the clients of Marifa Tech in Africa.
- Planning: Splitting Atlas project into sprints, visualizing the data migration, configuring the cloud environment. This is where I as the developer come in to realize the technical complexities but the PM in me makes everything meet the business goal.
- Implementation: The real structure. The pipelines of data, the CDP setup, the integrations. Here my business is to pave the way to the engineers, to clear away obstructions, to see that the engineers have whatever they require to create.
- Monitoring & Controlling: This operates with execution. It has to do with keeping Atlas on course. When an API changes, when a security patch poses a threat to launch, I am the person who notices, evaluates how the triangle will be affected and issue the call to change. It is constant vigilance.
- Closure: Handing over a fully functional CDP, capturing the lessons learned, and ensuring Marifa Tech's clients get the value they signed up for.
I came to Marifa Tech to build. However, now, I am constructing something new. My new code is the Project Atlas brief. My new compiler is the Iron Triangle. My experience as a developer, a team leader, and perhaps that one conversation about database migration brought me here. It provides me with the engineering sympathy to relate to the engineers, the technical understanding to follow the engineering, and the product intuition to keep the business objective in focus.
The reason behind the failure of projects is not that people are not talented enough, but rather that they are not guided, they have no steady hand to hold the code and the chaos in the same breath. That is what an IT PM does. They are the creator of the voyage, the protector of the destination. They guarantee the commencement of a project such as Atlas of 10 million records and a 9-month deadline not only starts but completes. Successfully. The only story that counts in the end is the one that is successful.
Here I am thrust into the world of IT Project Management, working on a life project with a deadline; This is Week 0 and this is my story.
Top comments (0)