Openstuff Wiki : ProjectManagement

HomePage :: Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register

Is it a Project ?

Is It a Project?

A project has several characteristics:

Assignment to determine if it is a project:

Understanding Organizational Structures

Understanding Project Life Cycles and Project Management Processes

The Process Flow: the five process groups are iterative and should not be thought of as one time processes.

The Project Management Knowledge Areas

Initiating the Project

How to identify and document the goals of the project + project deliverables, constraints, and assumptions

Defining the Project Initiation Process

Needs and/or Demands that dictate the germination of a project:

The project Initiation process has several inputs:

Developing a Project Overview: four inputs described in the last section

Determining the Project Goals

Project Goals:
Goals should follow the SMART rule:
From a project perspective:

Project Requirements: Requirements are the specifications or necessary prerequisites that make up the product or service youíre producing

Project Deliverables: Deliverables are measurable outcomes, measurable results, or specific items that must be produced to consider the project or project phase completed

Stakeholders: Stakeholders might include the project sponsor, the customer (who might be one in the same as the project sponsor), the project manager, project team members, management personnel, contractors, suppliers, etc. Stakeholders can be internal or external to the organization.

Communicating with Stakeholders: In order to determine the specific goals of your project, youíll want to meet with each of the key stakeholders and document their ideas of the project
goals. ex: Why nedded ? Business critical ? Result ?

The Project Overview Document: The project overview document is a high-level look at the project goals and deliverables. It serves the purpose of capturing the intended outcome of the
project and its deliverables. It will provide a brief background of the project and describe the business opportunity the company is attempting to capitalize on. It will also describe the business objectives the project should meet. The overview lays the groundwork for future consensus on deliverables and project expectations.

Identifying the Project Constraints

Identifying the Project Assumptions

For planning purposes, you presume the event or thing youíve made the assumptions about is true, real, or certain. For example, you might assume that key resources will be available when needed on the project. Document that assumption.

Other assumptions could be things such as vendor delivery times, product availability, contractor availability, the accuracy of the project plan, the assumption that key project members will perform adequately, contract signing dates, project start dates, and project phase start dates...

Project Case Study Checklist

Project Goal: To open a new store in Colorado Springs six months from today.
Demand: Company data concludes that the Kitchen Heaven consumers have incomes of over $50,000 a year. The Colorado Springs area is home to a large number of people with that income. Currently, there is not a Kitchen Heaven there, but there appears to be a demand for one.
Project Sponsor: Dirk Perrier, VP of marketing.
Stakeholders: Jake Peterson, Ricardo Ramirez, and Jill Overstreet.
Organizational Structure: Functional organization with a separate projectized department.
Constraints: Time.

Creating a Project Charter

This chapter formally recognizes the launching of the project with the creation of a project charter.

Using Project Selection Methodologies

Defining Project Selection Criteria: Most organizations have a formal, or at least semiformal, process to select and prioritize projects.
=> selection criteria is concerned with the product of the project

Describing Project Selection Methods: Project selection methods are a technique used during the Initiation process to pick one project over another or to measure one particular projectís benefit to the organization.
=> selection methods measure the benefits of the project, or they compare the measurable benefits of one project against another.

Identifying the Projectís Initial Requirements

After youíve identified the project goals and the project deliverables, you should have a fairly easy time of identifying the kinds of resources youíre going to need to complete the project.

Defining Resource Requirements: human resources, equipment, materials, hardware, software, telephones, office space, travel arrangements, contractors, desks, network connections, etc.
Determining the Initial Budget: Breaking Down Project Costs

Formalizing and Publishing the Project Charter

This document is the foundation for the remaining project activity planning, execution, and control processes.
The project charter should include an:

The project charter isnít complete until youíve received sign-off from the project sponsor, senior management, and key stakeholders. Sign-off indicates that the document has been read by those signing it (letís hope so anyway) and that they agree with its contents and are on board with the project.

Creating the Scope Statement and WBS

Scoping Out the Project

Writing the Scope Statement: the purpose of the scope statement is to document the project goals, deliverables, and requirements so that they can be used as a baseline for future
project decisions. Interview your stakeholders and business experts to get at the requirements and then document them in the scope statement. The scope statement should include all of the following: (use reference, not needed te re-write all)

Publishing the Scope Management Plan

This plan is an important supplementary document to the project plan as it describes how changes to the project scope will be incorporated into the project. It also defines the process of how
to go about requesting a change.

Creating the Work Breakdown Structure (WBS)

The lowest level in a WBS is called a work package. Work packages are the tasks that can be easily assigned to one person, or team of people, with clear accountability and responsibility for completing the assignment. Assignments are easily made at the work package level. The work package level is where time estimates, cost estimates, and resource estimates are determined.

Resource Planning and Estimating

Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by WikkaWiki
Page was generated in 0.1563 seconds