Timeline for Does PMBoK say that a project manager should resist any change to the approved plans?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2020 at 17:27 | vote | accept | Daniel | ||
| Nov 29, 2020 at 15:39 | comment | added | David Espina | Throw away that book. There is a lot of junk out there. Think about it from the customer's perspective. If you hired painters to paint your wall an off white color but your partner wants pale blue, and your painter PM inhibits your change, how much will you like the off white painted wall when it's finished? | |
| Nov 29, 2020 at 15:36 | comment | added | Daniel | In one book, explaining the PMBoK processes, I've read that a project manager should minimize changes to the project. One of the reasons is that changes can demotivate the project team. | |
| Nov 29, 2020 at 15:27 | history | edited | David Espina | CC BY-SA 4.0 |
edited body
|
| Nov 29, 2020 at 15:26 | comment | added | David Espina | @Daniel, the PMBoK is not a method. Nor is it prescriptive. The implication is that the processes as described in it would require the PM to encourage its use, not just the change process but all of them as needed. Regarding change itself, why would PM not encourage change? An approved change implies a necessary change. That has to mean that, as a PM, you would encourage change requests so you can tease out necessary changes. Else, you continue with a project that is inherently less valuable or even wrong. | |
| Nov 29, 2020 at 14:51 | comment | added | Daniel | Are you sure that such a heavy project management method as described in PMBoK encourages changes? Can you provide any excerpts? | |
| Nov 29, 2020 at 12:00 | history | answered | David Espina | CC BY-SA 4.0 |