Three Best TLAs of all time, the hegemony of Excel, and the Intuitive Front End

Everybody jokes about TLAs and the proliferation of consultant-speak. My favorites to date include: SPOC - Single Point of Contact: During integration meetings between two merging IT organizations, SPOCs were identified as the key connection points between groups. Panders to the trekkies, but sticks in your mind. WOMP - What's On My Plate: The name of a report we developed in a PMO, listing issues assigned, projects being managed, open programming requests, etc. - one page per person. The WOMP…

Documentation Redux – a Shorthand Proposal Framework, and the PMO Surprise

McDonald sent a nice comment on my last post - he's writing a lot about project management lately, and we even chatted about some research he's doing around boomer flight. Since I don't get a ton of comments, I thought I'd respond with a post, instead. He poses the question: I am wondering if documentation of the communications associated with coding and testing (emails, archiving of successive release of code, meeting recordings, archiving of test results, etc.) can in any…

Thoughts on Why Tech Folks Hate Documentation

I've had some flashes of insight on why technical folks don't like to document stuff. Currently, I'm thrashing thru a skunkworks project that is evolving into something that will need to be reasonably available, robust, etc. I'm also trying to lead by example; I ask my teams to build for sustainability and document so they can "walk away". Of course, I'm also lazy - I really don't want to explain things over and over again. However, the time crunch I…

Guidelines for Success with your Skunk Works project

I've been hearing the term skunk works a lot lately, in reference to off-plan projects that are moving forward in all that "free time" people have in the IT department. Sometimes the term sounds slightly perjorative, but I like it when a project I am involved with is referred to in this way. The term's origin is well documented, no need to repeat it here. The Lockheed Martin folks made it famous, when referring to technology projects "on the edge"…

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…

Quality requirements for technical documentation are lower than user documentation

Ok, don't freak out now ... All I want to point out is that the apparent need for screen prints of every step in the process is a bit overdone, especially when we're talking about technical documents. Screen prints / images in the documentation typically means the electronic documents get unmanageably huge, even if you shrink the .JPGs, and few people know how to do that. Plus, you indirectly commit yourself / your organization to a huge maintenance burden. because…

Flexible intranet search does not have to mean a single search interface

Trying to provide a simple, flexible search capability for your organization's reams of historical documents? Using a project process that generates the typical stacks of documents, databases full of status reports and issues, and other "stuff"? It's important to think about the knowledge we are generating, and the best way to capture that knowledge – and not worry too much about how we’re going to search through those deliverables. There is no one way to capture / store different kinds…

Misapplying the Pareto principle

8 January, 2006
Project Management, Business Value of IT
2 Comments

Here's an interesting phenomenon I've encountered before ... When analyzing a specific section of a business, people seem to naturally focus attention and conversation on the top two or three customers/products/vendors that together represent (say) 20% of the revenues/costs/contracts. Our objective is to look at the data and identify opportunities (increase revenues, cut COGS, aggregate contracts); unfortunately, processing the data for these customers/products/vendors is currently a 100% manual task. Of course; this is why there is apparently so much "opportunity"…

The “Army Rangers” model for IT Professionals

I got a chance to read over some Gartner predictions for 2006 (available $ online). One that struck me said that the job market for IT specialists will shrink 40 percent by 2010. Hey, that's only a few years away! The article makes the point that "... IT people ... must have the capacity to move fluidly and effortlessly into multiple projects, disciplines, and processes." I like to cite, as an excellent illustration of this idea, the movie Black Hawk…

Build a Framework: Your chart junk is my roadmap / vision statement

I remember in the late 90's, seeing many examples of the little train of wedgies that folks used to characterize their business processes: I've used them myself (some of the above samples are mine, I'm comfortable in admitting it) - of course, I typically don't make this stuff up, I adapt from other examples, like everyone else. As I searched for a reasonable picture / schematic / "framework" for a "supply chain", I stumbled across what I believe to be…