Chapter 3. Starting a New Project

BECAUSE the heart of project management is planning, it’s no wonder that the planning processes for a new project require you to do a significant amount of work just to set the stage. You define the big picture and obtain stakeholder approval for the specifications of the product or service you’re creating and for the boundaries defining the overall scope of the project itself.

After this vision is in place, you’re ready to create your project blueprint—the project plan—using Microsoft Project 2010. You create a new project file and enter foundation information.

Then you break down your project goals and objectives into the actual phases, milestones, and tasks that form the backbone of your project information system. You sequence the phases and tasks and organize them into a hierarchy that maps to your project.

If your project or organization has more specialized or advanced requirements, you can use work breakdown structure codes that organize your task list by each deliverable.

You can add your supporting documentation, such as the vision or strategy document, to the project plan. Likewise, you can add supplementary information such as notes or hyperlinks to individual tasks, milestones, and phases. All this information makes your project plan the central repository of project information.

Getting from Idea to Proposal to Project

Many projects begin life as a bright idea. Maybe it’s a new product idea, a new service, or a new community fundraising event. The new project can be the solution to a specific problem that has arisen—for example, a factory retooling, a marketing initiative, or a training program. The new project might be generated from a client company that puts out a request for proposal.

Often the normal cycle of business dictates the creation of a new project. If you’re in the software development business, for example, you live with a product cycle that begins with a project plan and ends with the software launch. If you’re in the construction business, you work within a building process that starts with a project plan and ends with the ribbon-cutting ceremony. Whatever the project—another office move, another trade show, or another system deployment—you know you need to start with the project plan.

Before you get to the project plan, however, the idea needs to be given the green light by the powers that be, especially if it’s an entirely new idea. This is true whether a new project idea is conceived from the normal course of business, is the solution to a problem, or is a brilliant flash of inspiration. The skeleton of the idea is fleshed out in the form of a project proposal or business case. In the proposal or business case, the project is described along with the rationale for carrying out the project.

The largest part of this rationale is often the cost-benefit analysis. The proposal outlines the expected cost of implementing the project, the resources and time needed, the risks involved, and any assumptions and limitations. The proposal then explains the resulting benefits of the project, such as increased customer satisfaction, more efficient processing, or increased profitability.

The proposal is assessed by upper management. This group examines whether the proposal is compelling and workable, whether the organization has the necessary capacity, and most importantly, whether the expected benefits are greater than the expected costs. If these conditions are met, upper management gives the project the go-ahead, and the project can be implemented.

With all the preliminary thinking that goes into the proposal, you’re likely to be well aware of everything from scope to risks for the new project.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.223.206.225