Difference between revisions of "Project management"

From Organic Design wiki
m
(what the xmlwiki is not (yet))
Line 26: Line 26:
 
This wiki syntax is anything but simple and is going to keep it from being a easy install for most customers. I will take FCK Editor anyday over this.
 
This wiki syntax is anything but simple and is going to keep it from being a easy install for most customers. I will take FCK Editor anyday over this.
  
−
the point is collaboration and content. to include an image, just put in the whole url like this (edit this page to see, or hit '''Alt-E''')
+
:the point is collaboration and content. to include an image, just put in the whole url like this (edit this page to see, or hit '''Alt-E''')
 
<br>
 
<br>
 
http://www.google.com/intl/en/images/logo.gif
 
http://www.google.com/intl/en/images/logo.gif
 
<br>
 
<br>
 +
 +
 +
we do need to meet to set expectations... :)  keep on pluggin, we need to get our content down, and our content does not belong or work in anything but a wiki.  when the content is ready, then we can presentify it and give it to the client --[[User:Phalseid|Phalseid]] 00:06, 3 Oct 2006 (NZST)
  
  

Revision as of 00:06, 3 October 2006

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 fail for two reasons.

  • Poor scope (which leads to unmet expectations)
  • Poor execution.

Projects also follow the ETVX model:

  • Initiation: gather participants and exchange viewpoints (Why)
  • Planning: agree on what to do and how to do it (How)
  • Implementation: do it (What)
  • Testing and evaluation. (When)

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


Project Management Checklist as initial designed for the Project Molecule: [[1]]
HOW DO I INCLUDE A REFERENCE TO AN IMAGE ELSEWHERE?????????????????!!!!!!! This wiki syntax is anything but simple and is going to keep it from being a easy install for most customers. I will take FCK Editor anyday over this.

the point is collaboration and content. to include an image, just put in the whole url like this (edit this page to see, or hit Alt-E)


http://www.google.com/intl/en/images/logo.gif


we do need to meet to set expectations... :) keep on pluggin, we need to get our content down, and our content does not belong or work in anything but a wiki. when the content is ready, then we can presentify it and give it to the client --Phalseid 00:06, 3 Oct 2006 (NZST)


Maybe we need to set up a W5H Project Management Philosophy since people understand the Who-How concepts.

See also
Retrieved from "https://organicdesign.nz/wiki/index.php?title=Project_management&oldid=31034"