| Honestly I kind of rail against the suitability of traditional Project management thinking in tech. Beyond knowing: who does what, and by when, and for how much $$ the project management frameworks are largely fluff. A decent task list, with deadlines, a gantt chart if you want to be fancy, and a stakeholder RACI matrix are really all you need. Everything else is soft skills, managing stakeholders, getting alignment, getting out of the way of the individual contributors. And in the workplace any specific framework adherence is largely just a stylistic choice of documentation, if you have a handle of who does what and by when, and for how much $$ and some dependency understanding, you are >90% of the way to keeping any project under control. Also knowing what your role actually is, and not confusing project management with product management which is much different. |