Finishing projects on time is very important; but holding yourself accountable to a baseline is only as valid as the change management process you have in place. The definition of “on time” changes based on context and how expectations are managed. Change happens on projects, and in my experience most of that change is not […]
So I’m doing some PMP sample test questions today and ran into one where at the end, additional things were added and the customer is very happy. According to the answer, this project was unsuccessful because the additional features were “gold plating” which wastes time and probably cost. I got this wrong because I read “the project has added [this and that]” as the [this and that] = intended product of the project.
But there’s a deeper insight here.
There is often a misconception that managing an IT project is difficult. Avoiding the common pitfalls of IT project management is not rocket science, it is simply a case of taking some sensible measures. This article identifies 5 killer mistakes of project management and their solutions.
“My boss read in a magazine that developers using ‘___’ programming language are twice as productive, so he bought us a copy and cut our schedule in half.”
Project Change Management: Why developers need a project manager who can also manage change well, and get buy-in from the team before forcing a change on them.