Projects

From Organic Design wiki
Revision as of 15:49, 24 November 2006 by Bender (talk | contribs) (Caretaker: categories)


Cone.png This article or section is a stub. Stubs are articles that have not yet received substantial attention from the authors. They are short or insufficient pieces of information and require additions to further increase the article's usefulness. The project values stubs as useful first steps toward complete articles.


Projects

  • are written by supervisors
  • impacts multiple departments (support, management, payroll, accounting, etc.)
  • executed by employees.
  • starts and/or ends
  • impacts multiple departments (support, management, payroll, accounting, etc.)
  • multifacited (meaning it is “complicated�?)

An example of a Project is converting bank accounts, switching fax from phone-based to web based, installing a CRM, etc.

Projects also follow the ETVX model:

Using the ETVX Model can be extended or simplified(depending on the perspective)to include the following:

  • (WHO) - equate to Contributors to the Project
  • (WHAT) - equate to Scope of the Project Proposal
  • (WHEN) - equate to Timeline Commitments during Assessment and Delivery
  • (WHERE) - may equate to the location of the PM Toolset or Development Location
  • (WHY) - equate to Objectives and Goals
  • (HOW) - equate to either Rule of Engagement or the Method of Delivery

I don't know how we should discuss this. Mainly because I think with the visual that can be created to explain PM, most anybody should be able to grasp it with out translating to the above. Aregularjoe 06:27, 5 Oct 2006 (NZST)

im translating into a format i can grasp. --Phalseid 20:59, 22 Oct 2006 (NZDT)
See also