Posts

Showing posts from December, 2014

The Customer May Not Know Enough to Completely Define the Project

Sometimes the project manager places too high an expectation on the amount of foresight and vision that customers and sponsors have. In many cases, the project manager will go to the customer looking for answers to help define the project and the customer will not have all of the information needed. This happens all the time and it does not mean that the customer does not know what they are doing. In many cases, especially for large projects, the customer has a vision of what the end results will be, but cannot yet articulate this vision into concrete objectives, deliverables and scope.  There are three approaches for when you don't know very much information on the nature of the project. Increase Estimating Range Based on Uncertainty Based on having less than complete information, the  project manager may feel the need to guess on the details. This is not a good solution. It is better to state up-front everything that you know, as well as everything that you do not know. If you a

Four Responsibilities of Executives on Projects

A Primer on Processes and Templates Recipes for cooking are a beautiful thing. A recipe tells you the ingredients and how much of each you should include in whatever you are making. It then describes what you need to do to these ingredients in order to make a dish that is not only edible, but tasty as well. It’s great that someone else has already spent the time in putting together a recipe to follow that nearly guarantees success each time. To a certain extent we use recipes in our profession as project managers. The recipes we follow are the processes and templates that guide our projects to success each time. How can you put a process together and make the most of templates? Consider the following: A Primer on Processes and Templates Start with Phases To put a process together, a good starting place is defining the major phases in which a project must go through. Think about how a project moves through your organization, and document those major steps. For example, a simplified soft

Manage Political Problems as Issues

The larger your project gets, the more you will find that the issues you encounter are political in nature. "Politics" is all about interacting with people and influencing them to get things done. This can be a good thing, a bad thing, or a neutral thing, depending on the tactics people use. Let’s consider some examples of how utilizing political skills might be good, but can also be bad. You are able to move your ideas forward in the organization and get people to act on them (good), by currying favor, suppressing other opposing ideas and taking credit for the ideas of your staff (bad) . You have an ability to reach consensus on complex matters with a number of different stakeholders (good), by working behind the scenes with people in power, making deals and destroying people who don’t get on board (bad) . You receive funding for projects that are important to you and to your organization (good), by misrepresenting the costs and benefits, and by going around the existi