PMO Nirvana is a Conversation, not a Schedule

We continue to iterate on our PMO processes - managing too few resources and too many project requests, an environment I have consistently seen in every IT group I have ever worked with. Our latest discussion concerned the concept of FIFO work on projects ... ... when presented with five things to do, I will only [emphasis added] work on them in the order received. This is an exceedingly poor assumption for your personal run-rules, and a short-sighted objective for…

Read More ...

Three Business-Case Arguments for Agile, & The Moose On The Table

Another conversation at the start of the new year - this time in our PMO, concerning project prioritization and resource assignments. Many organizations follow a "parallel" model, launching multiple projects at any one time and working concurrently to move things forward. To be fair, this often occurs because we start work on one or two things, only to have additional worthy business requirements pop-up as time goes by. Unfortunately, we don't stop the first project or delay the second; most…

Read More ...

Five Simple Rules for Project Names, plus Four Sample Lists

A recent post by Jeff Atwood about project names brought back memories of a previous employer, and the project naming convention we set up in our PMO. At this company, the IT group spawned maybe 30 to 50 chunks of work we would call "projects" - at least two calendar weeks in duration (anything smaller than that was just a programming request, and given a control number). Like any good PMO, we generated charters, mission statements, requirements, process maps, status…

Read More ...

SQL Hack for Reporting Project Phase and Status

It's been a while since I've posted some code, but I did a nice little SQL hack today that I've been puzzling over for a while. I freely admit that I may have made this more difficult with the original data model, but the die has been cast. Consider a single SQL table that captures project updates as comments note that this table also allows me to change the "phase" (ex. Design, Development, Test, Production) and/or Status (ex. Proposed, Red,…

Read More ...

How to Win at the PMO Prioritization Game

Last time I talked about "cheating" at the PMO prioritization game. Ok, it wasn't cheating, more like a trick to keep your projects small, fast - and easy to fit into a crowded schedule. Totally above board, but some might call it manipulative. Remember the old management hack ... how do eat an elephant? If that's too cliche for you, let's talk about ways to consistently win at the prioritization game. How can you make sure your projects are legitimately…

Read More ...

How to Cheat at the PMO Prioritization Game

Many will say their Project Management Office (PMO) has been established to promote "Best Practices for Project Management" - better work product, alignment with business strategic direction, etc. That may be partially true, but let's inject a little reality here ... many PMOs were created to help solve what I call the Dirt Bag problem - you can't fit 10 lbs of "dirt" in a 5 lb bag. I'm talking about the project prioritization process; I have 100 different project…

Read More ...

PMO Prioritization – Project Descriptions should be Effective, Relevant … and Short!

Next year, our PMO will be taking a run at improving "transparency" for project prioritization - a clearer process for getting projects approved and scheduled. Here's a key building block - what is the most effective way to describe a project? There is a certain amount of art and style in getting this right; most PMOs feature some sort of central database listing candidate projects; typically, the various screens, views, reports, etc. are designed for "short and sweet" descriptions. Note…

Read More ...

Subdivide a huge project list to simplify the prioritization process

A classic problem for many project-oriented organizations (IT, R&D, Engineering, Operations) ... how can resource prioritization be simplified, yet repeatable? It's a fairly involved topic, but a common approach is to group projects into a workable number of "chunks" ... we'll use the term Initiatives. How will this help? Challenge: Clarify the team's priorities, alignment, and resource levels - without going into the details The CEO asks a question – what Projects are on the to-do list for IT? [Do…

Read More ...