Dear Bob ...
My question pertains to prioritizing projects: I'm a supervisor in the IT shop that supports a fairly large city department (~1500 personnel). We have 27 IT folks dedicated to supporting the department. (I say "dedicated" because we do get some additional support from the city IT staff too, but only limited support, since they're not cleared.) There are 3 of us working supervisors, plus the IT Manager.
For some time now, I have been fighting with our upper management to better address how projects are being doled out to us. I've stressed how we (the IT shop) have got to get a handle on this process because our folks are feeling overwhelmed and getting burnt out. I've had more than one person tell me "I don’t care what projects you want me to work on, just tell me which ones those are, and stop changing the list every week!"
So my senior management devised a plan to help us out by implementing a formal project request process (which we've done), and then they will prioritize the projects for us. Right now there are 55 approved projects on this list! And, of course, they're listed in 1,2,3… priority order. Which goes completely against your recommendations as stated in your book [the writer is referring to Chapter 10 of Keep the Joint Running: A Manifesto for 21st Century Information Technology - Bob].
At first, when this process was implemented, I thought it was a good idea, since it really didn't matter to me how many projects were on the list, since our folks could only work on the top 6 or 8 at any one time. But what's been happening is that as a new "hot" project comes up, they'll send me a new project list with this project listed as #7. So whatever we've done for projects 7, 8 & 9 have to stop, or be readjusted, to accommodate this new project schedule. Overall, projects are getting done, but the administrative overhead we expend to "manage" this process is killing us and our staff.
So according to your book, I need to convince my senior management to go with a single master project plan where all the approved projects are listed. And the response that someone who submits a project, should be either "No" or "When." I've read, and re-read this section several times, and I think I understand this, in principle. But how can I assure my management that the projects will be worked in the order they wish, if we do implement your approach?
- Governanced to death
Dear Governanced ...
Here's how I think you need to modify the process to make it work, and it isn't a very complicated change.