Another caveat for the erstwhile agile developer

15 January, 2007
Change Management, Application Development
0 Comments

If your objective is a "sense of urgency", or maybe "time to value", please don't think this gives you carte blanche to push patchy, chewing-gum-and-bailing-wire solutions out into production. Expect the expectation that the production systems' availability level must be maintained. Confused? It sounds like I'm taking two opposing sides ... I want speed and quality, and doesn't the Iron Triangle force you to pick between the two? It's possible, of course, you just need to practice a little discipline…

A stunningly direct list, suitable for self-evaluations at year end

via Rothmann (who got it from Lester) - MacLeod's list (from the prolific Wade) ... The Career Manifesto (original here) Unless you’re working in a coal mine, an emergency ward, or their equivalent, spare us the sad stories about your tough job. The biggest risk most of us face in the course of a day is a paper cut. Yes, your boss is an idiot at times. So what? (Do you think your associates sit around and marvel at your…

The Iron Triangle – Quality is a Feature that We Choose to Omit from Projects

Project managers must communicate the trade-off between additional functionality and the time required to fully test the work. Don't assume testing will be completed - it's something that takes time!

A great mission statement for Corporate IT

This is actually an old story, from a previous life, but I need to get back on the posting bandwagon. Way back in the day... ... there was a site on the public Internet with Company Confidential Information out there. The site was put together by an ambitious sales rep with some time on his hands, a few technical books, and a yen for something interesting to do. It was a nice little site, too - even had user ID…

The Law of Large Numbers – or, why Enterprise Wikis are Fundamentally Challenged

26 September, 2006
Web 2.0
1 Comment

Some will be taken a bit by surprise to read the title of this post; we have implemented a wiki in our group at work, and I have the evangelist role in promoting the tool. Still, a recent "event" brought home the fact that wikis are not the silver bullets that some breathless articles may make them out to be. To be fair, Hickins' article does call out the "law of large numbers", although the idea is buried in the…

Funny, how techies talk to each other

I'm writing an email to my favorite SQL guru, about a pretty sticky little problem I'm working on, and I found myself making up words ... In the LotesDB, comments / notes are kept in a single field. Each comment is time and date stamped, with a uname, so that's pretty predictable. The data in the field looks like this: 02/15/2002 03:46 PM (Steve Manager): Capital was approved on 2/11. Project Number has been assigned in SAP and server hardware…

War Stories from the Change Management front

Stories make our ideas real and relevant, and are helpful tools when introducing change. This article has a few examples of stories - all around the topic of introducing change.

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…