Butting In to the Conversation: PM Communication Tools

Dennis McDonald and Lee White are conducting an interesting experiment on their blogs, crossposting a conversation about project management and social media. I'll add my voice, with both input on the topic and observations on the method. (Topic) The Right Tool for The Job - depends on the Job The first part of the conversation talks about whether social media could replace classic project management tools, in terms of communicating project status. I agree with Dennis - you can never…

Update on Blogs as PM Tools – Tales from the Front Lines

We seem to be going through a second wave of focus (hype?) in the popular technology press, on the idea of using blogs as an important project management tool. The topic made the cover of CIO Magazine this week - Lynch made a number of interesting observations - interesting because I don't necessarily see the same things in practice: The Reputation Hurdle: While I agree that blogs aren't fully understood by everyone, the folks that need to use them pick…

Innovation That Matters – Substance Over Style

When talking about "innovation" in a non-digital firm, don't force-fit the trendy stuff - focus on the innovative stuff you've done with your traditional environment, like ERP and Data Analytics. Tie this to what creates value for the enterprise, and you have something meaningful.

Five Simple Rules for Project Names, plus Four Sample Lists

8 January, 2008
Project Management, PMO
0 Comments

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…

Tactics for Controlling Project Scope

5 January, 2008
Project Management
0 Comments

I wrote about ways to "cheat" at project prioritization [aka trying to figure out what to work on next, when there is more demand (projects) than supply (people to work on them)]. One significant tool you have at your disposal is controlling scope - can you do 20% of the work to get 80% of the benefits? Easier said than done, sometimes you need tactics, that help identify an opportune place to stop, a run-on project, or a design that…

How to Win at the PMO Prioritization Game

19 December, 2007
PMO, Communication
0 Comments

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…

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

9 December, 2007
Project Management, PMO
0 Comments

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…

PM Anti-Patterns That Increase IT Project Cycle Time

Lots of conversation at work these days about PMO, resource prioritization, and reducing cycle time for IT projects. I feel a series of posts coming on ... IAPL, we launched a project to bring test discipline to our technology efforts. The team was writing standards and guidelines for test scripts, implementing integrated testing tools supplied by the ERP vendor, and adding steps to our project methodology requiring test scripts for all system changes. As the project dragged into a fourth…

College Professor uses Tried-and-True method for Encouraging Knowledge Sharing

via Slashdot a few weeks ago, and Ars Technica; at the University of Washington-Bothell, Martha Groom recently assigned her students to work on Wikipedia entries, and add to the knowledge base. An interesting approach; I found the reaction of the Wikipedia community most interesting, in that the entries were aggressively edited and commented upon - sometimes "rudely". It's a common theme in many KM discussions, as early adopters enter their first Trough of Disillusionment, and see these wonderful tools languish…

Defining the Business Value of a Project

25 October, 2007
Project Management, Business Value of IT
0 Comments

I'm following a project management meme lately; while freely admitting that I'm oversimplifying some complex topics, I will forge ahead with ... project "value". At work, we've been talking about the classic challenge of putting a business value on a project. I call it a "classic" challenge because it's a basic requirement for every prioritization exercise that I've been exposed to. You know the drill - we have 10 projects, but only time and resources to do 5. How does…