For years, many project and functional managers have believed they need the “exact right person” in each role on a project. Those exact right people are specialists, and some of them have quite narrow specialties. Here’s the story of one specialist and her impact on several projects. Two project managers needed the same person, a […]
I’ve been sick for weeks, and am finally coming out of it to be close to healthy. (I was still coughing in the 8-degree Fahrenheit cold leaving the gym. Oh well.) One of the problems is that my work doesn’t stop if I’m sick. I bet yours doesn’t either. Daughter #2 asked last night if
After I returned home from the Sweden PSL, I had a cold, and then have been redesigning simulations for my upcoming (tomorrow!) customized project management workshop. At PSL, we invoked one idea repeatedly: the zeroth solution. The zeroth solution is the simplest thing that could work. So, if you need a simulation for a workshop,
I gave a talk last night at the Software Quality Group of New England about schedule games. During the talk, I explained how serial lifecycles don’t manage technical, schedule, or cost risk. Serial lifecycles actually increase the duration of the project. And, serial lifecycles don’t offer feedback early enough for the project team. (They only
Esther has insights, Specialists AND Generalists, on Why Projects Don’t Need Specialists. Her point, that people tend to coalesce around their interests, and that as specialists, they may not share interests, is something I have also seen on projects. As Esther says, Reducing categories (having “developers” rather than many named specialists) reduces differences and helps
I taught several PM workshops last week in Israel. The Israeli project managers have the same concerns that my US students do–it’s difficult to imagine moving to Agile or even just integrating agile methods into your project if you have specialists. Specialists increase project delays in these ways: They aren’t available when you need them.
I spoke with a program manager who’d been displaced from his program because he doesn’t scream or yell at people. (No, I’m not making this up. This is true.) He’s an effective program manager, because he doesn’t tell people to do this or that task. Instead, he tells them the goal and the results he’s
Chris asked in his comment, how about using the word ‘abandoned’ for projects that are “finished”? I just don’t think of completed projects as abandoned. Let’s separate the product from the project. Projects complete. Products may never be done, but projects do finish, sometimes whether we want them to or not. I was working as
John Cook, wrote a lovely post, Peter Drucker and abandoning projects, explaining how Drucker talks about abandoning projects. (John, thanks, I will definitely be referencing Drucker in the PPM book.) I haven’t been using the word “abandon” when I describe stopping projects. I’ve been using the word “Kill” and the concepts of permanently stopping projects
In July, I sent out the Pragmatic Manager email newsletter: 90% Done is Not Almost Done. I have finally posted it. Enjoy!