From Wikibooks, open books for an open world
< Project+
Jump to navigation Jump to search

IDENTIFY PROJECT PURPOSE[edit | edit source]

Key Points[edit | edit source]

  • identify business objective i.e. stated goal of the project
  • define the opportunity/problem

Goal[edit | edit source]

  • desired end result
  • often synonymous with objective
  • may be a high-level objective that has less-than-complete definition

Objective[edit | edit source]

  • something to be achieved
  • desired outcomes of the project or any part of the project
  • measued in in terms of concrete deliverables and behavioral outcomes
  • it has to be visualisez before


Key Points[edit | edit source]

  • Identify high-level business-related requirements, outcomes, and criteria for success
  • identify low-level needs and expectations
  • establish boundaries for project budget, duration, and risk

Triple Constraints[edit | edit source]

  • scope
  • schedule
  • budget

Business Case[edit | edit source]

  • the information that describes the justification for the project
  • project is justified if expected benefits outweigh estimated costs and risks
  • often complex
  • may require
    • Financial Analysis
    • technical analysis
    • organization impact analysis
    • feasibility study

Request for Proposal (RFP) AKA Request for Quote (RFQ).[edit | edit source]

  • describes
    • need for products and/or services
    • conditions under which product/services are to be provided
  • purpose
    • solicit bids or proposals from prospective suppliers


Project Manager[edit | edit source]

  • key stakeholder
  • responsible and accountable for managing a project's planning and performance
  • single point of accountability for a project

Customer or Client[edit | edit source]

  • key stakeholder
  • person or organization that is the principle beneficiary of the project
  • Generally has a significant authority regarding
    • scope definition
    • whether the project should be initiated and/or continued.

Performing Organization[edit | edit source]

  • key stakeholder
  • company or group doing the work

[edit | edit source]

  • key stakeholder
  • builds and maintains executive commitment
  • allocates organization resources (capital, human, etc.)
  • provides direction
  • has authority to settle disputes between project staff & functional staff

Champion[edit | edit source]

  • senior exec who promotes and defends the project

Project Steering Committee[edit | edit source]

  • execs from functional areas that provide
    • guidance
    • strategic input and direction
    • enlist cooperation from their functional group
    • high level project approval

Project Team (decide later? In planning phase?)[edit | edit source]

  • anybody who is doing work on the project
  • includes contractors and consultants

Authority[edit | edit source]

  • ability to get other people to act based on your decisions
  • based on perception that a person has been officially empowered to issue binding orders

Power[edit | edit source]

  • ability to influence the actions of others
  • may come from
    • formal delegation of authority
      • charter gives PM this
    • reference power
      • personality
    • subject matter expertise
      • respect earned from skills
    • ability to influence rewards and penalties
      • rewarded or coercive authority
    • other sources.

Stakeholder[edit | edit source]

  • anybody and everybody with a stake in the project
    • clients
    • sponsors
    • performers
    • general public
    • family and friends of direct participants
    • others?

Managerial Structures[edit | edit source]

  • functional
  • project
  • matrix

Matrix Organization[edit | edit source]

  • business structure in which people are assigned to
    • functional group
      • departments, disciplines, etc
    • projects or processes
      • cut across the organization
      • require resources from multiple functional groups.


Scope Components[edit | edit source]

  • function
  • performance

Five (scope?) Constants[edit | edit source]

  • project end date
  • project ownership
  • completion criteria
  • rigorous change control procedure
  • "best practices" life cycle for this type of project

Statement of Scope AKA Statement of Work (SOW)[edit | edit source]

  • description of the scope of a project
  • centered on the major deliverables and constraints
  • develops and confirms an understanding of project scope
  • typically requires more time to create than WBS or charter
  • review of the scope documents held before proceeding to project planning phase
  • complete after the PM and the sponsor agree that objectives will be met
  • establishes procedure to request changes to a project scope
  • end-users representative approves technical changes

SOW-PROCS (mnemonic)[edit | edit source]

  • (P) - Policies and Procedures
  • (R) - Requirements
  • (O) - Overview
  • (C) - Criteria for Vendor Purchase
  • (S) - Specifications

Scope: three dimensions[edit | edit source]

  • product
    • full set of features and functions
  • project
    • work that has to be done to deliver the product
  • impact
    • involvement by performing and client organizations.
    • effect on performing and client organizations.

Scope Change[edit | edit source]

  • any change in the definition of the project scope
  • can result from:
    • changes in client needs
    • discovery of defects or omissions
    • regulatory changes
    • other

Scope Change Control AKA Scope Change Management[edit | edit source]

  • process of making sure that changes to the scope are consciously evaluated
  • making sure that implications are considered in making a decision to
    • make the change
    • postpone it
    • reject it

Scope Creep[edit | edit source]

  • changes in scope over the life of a project
  • unconscious growth of the project scope
  • results from uncontrolled changes to requirements
  • managed by implementing a rigid change control process

Scope Definition[edit | edit source]

  • breaks down major deliverables into more manageable components
  • makes verification, development, and project control, easier
  • may be part of requirements definition and/or design

Scope Planning[edit | edit source]

  • development of a statement of project's
    • principle deliverables
    • justification (business case)
    • objectives
  • part of requirements definition

Scope Verification[edit | edit source]

  • process to ensure that all project deliverables have been completed satisfactorily
  • associated with acceptance of the product by clients and sponsors.

BUILD CONSENSUS AND OBTAIN WRITTEN APPROVAL (objectives)[edit | edit source]

Secure Written Confirmation Of[edit | edit source]

  • customer expectations
  • problem/opportunity
  • deliverables
  • strategy
  • completion date
  • Budget
  • risks
  • priority
  • sponsor
  • resources
  • resources availability

- all the above documented in the charter?

Methods to build consensus[edit | edit source]

  • negotiating
  • interviewing
  • meetings
  • memos

Strategies To build And Maintain Senior Management Support[edit | edit source]

  • involve mgmt in defining project concept
  • involve mgmt in defining scope
  • involve mgmt in reviewing and approving deliverables
  • provide role for mgmt as spokesperson/advocate

Consensus[edit | edit source]

  • unanimous agreement among the decision-makers
  • requires conviction that the decision will adequately achieve objectives
  • if one person is not in agreement then there is no consensus