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…
They always say data conversions are a labor of love - you pour your heart and soul into the program, to get the most data converted as possible, and then, when you actually do run the code in production - it's a one time event; toss the source files in the bit bucket. Well, that's what it was [almost] like in my first job - we sold Property Management systems along with implementation services, and those services invariably included a…
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…
Last in a series on some practical legal mumbo jumbo (disclaimer: IANAL) for your Master Consulting Agreements (MCA). This one was particularly interesting to put in; it's really interesting to see who catches it, but it was an amazing (in retrospect) observation that led us to include the language. The Trigger Event: A virus outbreak. We had been hit before, and the executive group was not fond of losing their email for a day or two, so we implemented fairly…
I am late is responding to a comment on this post, first in a series about Consulting Engagements. Earlier this week it was Intellectual Property, with another good comment ... so, why all the harsh language about protecting IP that I probably can't commercialize? Ah - welcome to the world of Risk Sharing. The issue is that most businesses, especially SMBs that are simply not used to paying $200 an hour for labor, typically have a tough time wrapping their…
Previously, I wrote about Fee Structures in Consulting Engagements, which is the stuff that the consultants are primarily interested in. If the consultant / firm has any strategic skills, their next concerns will be about Intellectual Property (IP) rights. <aside> Not that IP, this IP </aside> Do you really think that they make it all up from scratch for each new customer? Of course not - like any other developer, they have a body of code (and/or project/process methodology) that…
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…
Yet another vendor seminar last month, and the idiosyncrasy of the day was an abnormal amount of focus on the fee structure (they were presenting their expertise on a certain platform, and talk of fees was a tad disconcerting). The vendor is, of course, railing against the fixed fee - puts all the risk on them, artificially constrains the project, etc. They didn't mention how the fixed fee enables an upside on their part - if the Vendor (contractor/consultant/them) pads…