Archive for May, 2003
May 29, 2003
R&D vs. Project
From McGee’s Musings:
The superficial resemblance between software development and construction in the physical world obscures the fact that often what we are doing in software development is more R&D than it is general contracting. Knowing which parts of the project are routine and which might be pushing the envelope requires a more sophisticated form of estimating and budgeting than vanilla project management techniques.
That makes a lot of sense to me.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 22, 2003
After reading about LinkedIn over on rc3.org and a few other places I decided to try it out. It is basically a professional networking service that creates linkages among invitation-only networks while protecting the privacy of the participants. After making 4 invitation links I now have access to a network of over 1200 very interesting people. Pretty amazing.
I think this type of service is the kind of thing that professional associations should be focusing on: fostering quality connections among their members. That’s what they are all about and LinkedIn shows how you can facilitate that need in unique and valuable ways via the Web.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 22, 2003
IA Office Decor/Tools
Bloug Entry (May 22, 2003) has some interesting and fun ideas on how to create really large whiteboards on the cheap and other brainstorming tools.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 21, 2003
Why I Love the Web
I find random stuff like this Washington D.C. Climate Summary page that will calculate temperature and precipitation comparisons for the region over the past 40 years.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 20, 2003
Sports Virtual Communities
If you follow virtual community news, you may want to check out the May 16, 2003 issue of Sports Illustrated which has an article about the impact of sports community sites on the lives of coaches and atheletes. The article interprets that impact as largely negative. “Caught in the Net”, p46. Unfortunately SI doesn’t post their print articles online as far as I can tell.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 19, 2003
On Killing Projects
Sometimes projects cannot succeed in their current incarnation. I have been involved in a couple of projects that were initially disasters and had to be stopped, completely re-thought and then begun again. While it won’t happen often (hopefully!) being able to correctly identify a terminal project and deal with it can save time, money and finally generate a successful outcome. I’ve outlined a few factors to look for as well as some tips on how to kill a bad project.
When to Kill a Project
- Over budget.
- Over time.
- Nowhere near completion.
- Thinking about the project keeps you up at night and makes you nauseous at work.
The above are a deadly combination. Budget, time and completion milestones should all roughly keep pace with each other. Being over budget, over time and under completed is about the worst possible configuration and represents catastrophic failure for that project. Feeling sick to your stomach is your subconcious project manager telling you that you are doomed unless something is done. Listen to your body. The secret to excellent project management is recognizing tendencies toward the above early in the project rather than when you run out of money and/or time.
How to Kill a Project
- Build a case including alternate options to meet original needs.
- Gain support of stakeholders and a champion.
- Present recommendations to leadership.
- Do not play the blame game.
- Learn!
Don’t just go to your supervisor and say this project needs to be killed. You have to address how the need that generated the project in the first place will still be met or debunk the necessity of meeting it at all. You won’t get anywhere unless you can confidently answer that one. You also need to sell all the stakeholders on the idea as well. Stopping a project is incredibly hard to do once momentum is established and you will need all the help you can get. Finally, don’t get into assigning blame for who screwed up what. That will just take energy away from killing the project. Fix the problems and learn what went wrong and why and how to do it better next time.
This is not to say that all poorly run projects must be killed. Usually you can make some adjustments to an existing project that will bring it back into shape. Killing should be reserved for those few that cannot be salvaged in their current form.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 17, 2003
More on XML in the Journal Publishing Process
This article provides a good overview of the role XML can serve in the publishing process for scientific, technical and medical (STM) journals:Why STM Publishers Should Use XML.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 17, 2003
Blog Tipping Points
David Pollard has some interesting ideas about tipping points for blogs.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 13, 2003
MTWordStats Analysis of High Context
I’ve set up a basic analysis of High Context using MTWordStats.
I’ve blogged just over 22 thousand words and have been writing at the 10th grade level, which is too high for content targeted at the general public. Luckily, I’m not targeting them. :) No big surprises in the word frequencies. I do wish there were a filter to block articles and common verbs.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
May 13, 2003
Weblog Content Analysis Tools?
Anyone aware of tools or plugins that will do a rudimentary content analysis on weblog posts? A plug-in for MT that calculates simple word frequencies in posts would be very useful in identifying potential categories.
Update: Found WordStats over at MT Plugin Directory. I’ll give this a shot this evening. Note to self, google before posting.
Permanent Link | Subscribe via RSS | Subscribe via Email | Comment
+1 (410) 742-9088 | david@highcontext.com
Copyright © 2010 High Context Consulting
Privacy Policy: HCC will never share your information with anyone without your permission.