Project management
|
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 initially designed for the Project Molecule:
http://www.sequoiais.com/pm/pm.gif
Project Stages Checklist as initially designed for the Project Molecule:
http://www.sequoiais.com/pm/project.gif
This diagram is obviously geared towards the development of software/websites. We should consider creating one that is more focused on delivering a combo of Business Process and Software.
Project Molecule - Execution
Every task that is performed during the design and development stages of a project should directly correlate back to one of the original objective set forth during the Specification stage of a project
http://www.sequoiais.com/pm/pm_molecule_execution.gif
Project Molecule - Participants
Explaing the staffing model of project
http://www.sequoiais.com/pm/pm_molecule_participants.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
