Comments on: Mission, Vision, and Strategy in Project Management

By: Travis Anderson

Travis Anderson — Fri, 22 May 2009 19:35:43 +0000

Jerry,
This is a great topic and a favorite for me.

Up front communications is the most important in my view. Often is the case that a lead or PM hits the ground running and does not spend enough time on the primary focus. That is why a strategy is so important. Formulating a strategy involves a common sense iterative approach by 1) gather information; 2) develop processes and procedures to analyze information; 3) determine decision points or phase gates; 4) implement the decision. Communicating the strategy early and often is very important. People or more commonly decision makers often shoot from the hips and do not spend an appropriate amount of time on the first step. Also, it is common for some individuals to make a decision and not keep an open mind. Flexibility is important in an ever changing environment. That being stated, it is also important to stand ground on some issues. Issues related to the primary decision points must be monitored and regulated using procedures and practices to make sure performance expectations are being met.

Travis

By: pradeepbhanot (Pradeep Bhanot)

pradeepbhanot (Pradeep Bhanot) — Thu, 21 May 2009 09:38:02 +0000

Twitter Comment

Just commented on a blogpost the role of an MRD in a project at [link to post]

- Posted using Chat Catcher

By: Pradeep Bhanot

Pradeep Bhanot — Thu, 21 May 2009 09:09:14 +0000

In my experience Jerry, once the project is underway, it is too late to be asking those ‘why’ questions.
What the project team needs to have communicated to it is the business plan. The formal document that usually contains this information is the Market Requirements document (MRD). The MRD makes the case for the company to invest in the project or program and connects the project to the companies MVS. The MRD is not widely shared as it often contains company financial performance, market share and competitive threats that only product managers, marketing leadership and investment board need to know.

The Product Requirements Document (PRD) defines the requirements. PMBOK begins the journey at the PRD stage.

Pradeep Bhanot, Product Marketing Director, CA Clarity, CA

By: Ferne Arfin

Ferne Arfin — Thu, 21 May 2009 08:53:53 +0000

Interesting ideas. And I would agree that communicating the purpose of a project – not only to all team members, but ultimately to the beneficiaries of the activity – is important.
But, in my more than 20 years in corporate communication, I’ve tended to shy away from the formal MVS process because, it usually becomes an exercise in spinning wheels.
Because an MVS is a committment and a promise, managers and executives tend to over manage them to stay safe and within the minimum that is doable. So over and over again, I witnessed a great deal of management and communications time being spent on creating long winded, clause packed statements that everyone could agree with but no one could really understand.
To my mind, no one has ever topped the old Avis slogan – “We Try Harder” as a clear statement of where a company wanted to go and how it was going to get there. It worked on many internal and external levels. I doubt very much that it was the product of a committee charged with coming up with a Mission and Vision Statement.

By: commsabilities (Jo Ann Sweeney)

commsabilities (Jo Ann Sweeney) — Thu, 21 May 2009 08:05:02 +0000

Twitter Comment

Can project communications be systematised or is it about relationships [link to post]

- Posted using Chat Catcher