Just slept on this article and realized something.
There are two wildly popular management methodologies in IT (and probably other places), which can be grouped into constraint-based like agile, scrum, where the focus is not on individual deadlines, but getting a consistent performance out of employees, and goal-based, with project managers and deadlines.
I wouldn't exactly say either style is uncontroversially popular, and depends on the needs of the project, with greenfield projects requiring a goal-based approach, and maintenance/feature dev of existing ones leaning more towards agile (there's a lot more of the latter, that's why agile's popular).
For what works for you, well that's up to you. I'm a wildly inconsistent person by nature, whether playing to my strengths or covering my weaknesses is a better approach, that's once again not an easy question to answer.
There are two wildly popular management methodologies in IT (and probably other places), which can be grouped into constraint-based like agile, scrum, where the focus is not on individual deadlines, but getting a consistent performance out of employees, and goal-based, with project managers and deadlines.
I wouldn't exactly say either style is uncontroversially popular, and depends on the needs of the project, with greenfield projects requiring a goal-based approach, and maintenance/feature dev of existing ones leaning more towards agile (there's a lot more of the latter, that's why agile's popular).
For what works for you, well that's up to you. I'm a wildly inconsistent person by nature, whether playing to my strengths or covering my weaknesses is a better approach, that's once again not an easy question to answer.