Tactics

Do you want it good or fast? Prioritizing Time-to-Value over Requirements

I have a background in software product development, iterative "methodologies", and the sort of fast-twitch life cycle that characterizes entrepreneurial startups, high-growing businesses, and "lean" process improvement projects. Unfortunately, this style is also favored by departmental developer wannabes, sloppy coders, and impatient Gen-Y newbies that want to apply a consumer products mentality to corporate IT. <aside>Yes, I'm throwing a bit of a challenge out with that last statement. I understand that as the demographics of my IT team changes, management…

Read More ...

Five More Realities for Driving Business Value from Technology

Dennis McDonald's recent post listed Ten Realities of Managing and Using Technology to Generate Business Value. I think a few of these items need some elaboration ... Implementing a technology based solution without understanding the costs is a big mistake ... and most projects only consider TCI - Total Cost of Implementation. This typically includes acquisition, first-year maintenance, and professional services (or internal IT time) to integrate with existing systems. Smart managers will add in Recurring Costs, such as annual…

Read More ...

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…

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

Measuring and Reporting IT Value (2 of 2)

My last post generated some interest, so here's the rest of the examples. Last time, I wrote about the simplistic approach to measure and report on IT value: Is your IT group working on the right things? Are they working on the right things well? Is your IT spend comparable to industry norms? Is your IT spend comparable to other measures of company performance? A bit more detail ... balancing quantitative and qualitative ... (Quantitative) To make sure you have…

Read More ...