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 ...

Wading into a Project In Progress

This week I had to wade into the depths of a Large Project; well, actually a component of a Large Project, that was struggling a bit to find a path through the forest. Not my first time, certainly not my last, and (believe it or not) usually a pretty good time! <aside> Ok, by "large" I mean "amazingly high profile, visible to Upper Management, involving Lots of Talented, Busy People" </aside> <aside> Ok, by "Talented" I mean "terrific at their…

Read More ...