Don't Be a Process Zealot
Every piece of software ever shipped involved some form of project management — even if it was just one person keeping a mental list of what to do next. Project management, at its core, is the practice of deciding what to work on, in what order, and making sure it actually gets done. It is not about meetings, status reports, or color-coded Gantt charts. Those are tools, and tools can be used well or badly.
Engineers often develop an allergy to "Project Management" because they've experienced the bad version: status meetings where nothing is decided, tickets created for the sake of tracking rather than clarity, and processes that exist to comfort managers rather than help builders. This is a real problem. But rejecting all structure because you've seen bad structure is like refusing to use version control because someone once force-pushed to main.
Valid project management is fundamentally risk management for time. You have a finite number of hours, a team with limited capacity, and a set of things that need to happen. The question is not whether you manage the project — it's whether you do it deliberately or let chaos manage it for you. The three questions every project management approach tries to answer are:
- How do we visualize work? — Can everyone see what's in progress, what's blocked, and what's next?
- How do we limit chaos? — How do we prevent the team from being pulled in 15 directions simultaneously?
- How do we predict when we'll be done? — Can we give stakeholders a credible estimate, and can we detect early when we're falling behind?
There are endless wars about methodologies (Agile vs. Waterfall, Scrum vs. Kanban, SAFe vs. anything). As a senior engineer, you should ignore the dogma and focus on the physics: what actually reduces uncertainty and increases throughput for your team in your context. The three dominant dialects you must be fluent in are Agile (the philosophy), Scrum (the structured implementation), and Kanban (the flow-based implementation). We'll cover each in depth.
Key Point: The best project management is invisible. When it's working, engineers feel like they have clarity and focus. When it's failing, they feel like they're drowning in process. If your process doesn't directly reduce confusion or increase delivery speed, it's waste — cut it.