The lament echoes time and again, "The CIO should have a seat at the table." The claim continues that business cannot survive without the simplest of technologies. Then they provide evidence as if it would be the final nail in the coffin, "Just the other day, when email was down..." Raising my eyebrows in question, I ask, "So your email was down? For how long?" The question is like a scene from a horror film where the sudden realization is that the casket being completed is... your own. Gaining strategic respect is a long way away for those having trouble maintaining their tactical obligations. If your organization is having difficulty providing basic services, you will never have the privilege of being a partner with the business.
- How do you know when your project is in trouble? What have been you’re a-ha moments?
- Having managed many PMOs, what mechanisms have you used to avoid failure?
- What is your approach in bringing projects back from red?
(Obviously, I need more light in my office for these 4:00AM Google+ Hangouts.)
Have you ever had a boss that simply wants to stand in your way? They avoid making even the smallest decision, never providing enough information to understand their objections. It is more common than most of us would imagine. In fact, this behavior is the central to every sales interaction. Even though you may be repulsed at thinking of yourself as "selling" to your boss, that is exactly what is required with any idea you are pushing. Therefore, it makes perfect sense to employ the same techniques used to sell large systems. If you think this is rubbish, as one of my esteemed readers once eloquently said, I will posit that you are already using sales techniques, just the wrong ones—the ones car dealers use. Changing this approach will subdue your unruly boss
eCameron, Inc. and Formos, LLC are very pleased to officially announce significant contracts bringing millions of dollars over 2012 and 2013 to Clark County Washington businesses. These contracts directly address the #1 goal in the CREDC's strategic plan--growth and innovation in the Information Technology sector. Please, read the entire press release here.
Are you an event planner looking for more information about our keynotes, presentations, webinars. workshops, and classes? Most of our keynotes, track sessions, classes, and workshops are posted on this website. There are many that are not since we don't numerous custom education sessions for clients. If you feel that something posted on the site is close to what you want, please contact us and we can see if ti logically fits with what we offer.
We also have a complete page of references. You can contact us and we will give you the names and contact details for event-planner references doing events like yours.
You can reach us at +1 360-521-9051. As for Todd Williams.
The steps I think would be best are:
- Apply to PMI and start the application process. This provides you with a tool to track your hours, much like the spreadsheet I have, which should be considered a good starting point. I mailed this to each person that might end up being questioned on it so that it would minimize the chance of problems.
- When you think you have your hours, take a class. PSU has great PMP prep classes. I took a set of online courses from a reseller. The big thing to look for is the sample tests. I think they are critical and the I bought had two sets of test. They other offerings too.
- From the PMBOK and the classes I made flash cards to help me memorize certain material. I did them by hand, since I learn better that way, but you can probably find them for sale somewhere.
- After you get your 35 contact hours, then determine how long it will take you to nail the tests and apply for a test with enough time to study the sample tests. I would lot a few weeks for that.
- Watch the timing. The PMBOK's Fifth Edition in in progress and I am not sure when it will kick in. Do not study the fourth edition and find out you need the fifth. It is best to check with PMI on the timing.
I, also, borrowed the textbook Project Management: A system approach to planning, scheduling and controlling, by Harold Kerzner, and found it very good. I am thinking about getting it for my library. It is not something you need for the PMP, it is a good PM reference textbook.
The total cost for the PMP in 2009 was $997.00. Now it is about $50 more.
Let me be perfectly clear, I hate PMOs. It matters not if you call them project management offices, program management offices, or portfolio management offices, they only spell one thing—poor leadership. Now those of you that know me, have heard this enough times that your eyes are rolling back as you mumble, "Here he goes again. Who set the bait in front of him this time?" However, I have confused people with a couple of PMO articles that might seem contrary.
From her corner office, the new executive decried, "Decentralize the PMO. Let each department be responsible for their own projects." Maybe she had made a pact with another executive for some other bit of power, or it could be she lost a power struggle and the PMO had to go, or possibly she has little regards for project management thinking it is a mechanical, blue collar discipline that methodically follows a recipe to execute each project. Bottom line, she is missing the point of the Project Management Office (PMO)—it is all about business goals. Unfortunately, for the company, decentralized PMOs provide little if any value. They are similar to distributed teamwork—an oxymoron. The concept is illogical.
Again, I was chided for saying there are no Information Technology projects. This time, the excuse was that the company built software. I countered my antagonist by asking if the same group that built their software also maintained the account system, workstations, email, and network. "No, that is a separate group." He was missing that his company's production group was not IT. Information Technology is the support group... and yes, they should not be doing anything that fails to directly affect getting product out the door or reducing costs. Every project's goal must be to deliver to the operational needs of the company—selling product—not to the whims and desires of the IT group. If a project fails to address the needs of the customer (directly or indirectly), then it should never see a penny of funding. This seems such an elementary concept, but it is routinely violated by techno-bigots trying to implement the latest toy or tool.
Yesterday, I received an email from a Dad promoting a fundraiser his adult son is conducting—a Wounded Warrior Project. His Marine son escaped being on the receiving end of the project, but he is surely haunted by memories and guilt. I do not know this young man; I can only imagine his pain. Any of us trying to live through the loss of a son, daughter, or buddy who is only starting their life intimately knows this expansive, indescribable void. This young man is trying to bring good from the nonsensical events around him—he is growing into a leader.