Difference between revisions of "Project management"

From Organic Design wiki
m
(Project'Or RIA)
 
(33 intermediate revisions by 6 users not shown)
Line 1: Line 1:
−
{{stub}}
+
{{glossary}}{{stub}}
−
[[Category:Best_practice]][[category:glossary]][[category:ETVX]]
 
−
Projects fail for two reasons.
 
−
*Poor scope (which leads to unmet expectations)
 
−
*Poor execution.
 
  
−
Projects also follow the [[ETVX]] model:
+
== Agile ==
  
−
*Initiation: gather participants and exchange viewpoints ([[Why]])
+
=== Scrum Principles ===
−
*Planning: agree on what to do and how to do it ([[How]])
+
The framework and terminology are simple in concept yet difficult to implement. Successful Scrum teams embrace the values upon which Scrum is based (paraphrased from the Agile Manifesto):
−
*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:
+
;We value
−
*([[Who|WHO]]) - equate to Contributors to the Project
 
−
*([[What|WHAT]]) - equate to Scope of the Project Proposal
 
−
*([[When|WHEN]]) - equate to Timeline Commitments during Assessment and Delivery
 
−
*([[Where|WHERE]]) - may equate to the location of the PM Toolset or Development Location
 
−
*([[Why|WHY]]) - equate to Objectives and Goals
 
−
*([[How|HOW]]) - equate to either Rule of Engagement or the Method of Delivery
 
  
 +
*Individuals and interactions over processes and tools
 +
*Completed functionality over comprehensive documentation
 +
*Customer collaboration over contract negotiation
 +
*Responding to change over following a plan
  
−
'''Project Management Checklist''' as initially designed for the Project Molecule:<br>
+
That is, while there is value in the items on the right, the items on the left matter more.
−
http://www.sequoiais.com/pm/pm.gif<br>
 
−
<br>
 
  
−
'''Project Stages Checklist''' as initially designed for the Project Molecule:<br>
+
True success with the Scrum framework comes from teams and organizations who understand these values and the principles that form the foundation of all agile processes.
−
http://www.sequoiais.com/pm/project.gif<br>
 
−
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.
 
  
−
:i would also say that we are at the metatextual ''initiation'' stage of you and me working together....so lets just enjoy the process! --[[User:Phalseid|Phalseid]] 00:24, 3 Oct 2006 (NZST)
+
=== Agile Scrum links ===
 +
*http://www.youtube.com/watch?v=_BWbaZs1M_8
 +
*http://www.coachingagileteams.com/what-is-agile/
 +
*http://www.youtube.com/watch?feature=player_embedded&v=OuhZAVJO3xw
  
−
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)
+
== Open source software ==
 +
*[http://projectorria.toolware.fr/ Project'Or RIA]
  
−
 
+
== See also ==
−
Maybe we need to set up a W5H Project Management Philosophy since people understand the Who-How concepts.
+
*[[Organisation]]
−
 
+
*[http://appfrica.net/blog/2009/02/08/the-best-and-worst-project-management-apps/ The Best and Worst Project Management Apps] ''- good comparison of some web-based project management options''
−
;See also
+
*[[MW:Extension:Semantic Project Management]]
−
*[[Wikipedia:Project management]]
+
*[http://www.readwriteweb.com/archives/project_management_mechanical_turk_smartsheet_looks_awesome.php Project Management + Mechanical Turk? Smartsheet Looks Awesome]
−
*[[Wikipedia:List of project management topics]]
+
*[http://www.readwriteweb.com/archives/wedoist_introduces_real-time_contemporary_project.php Wedoist Introduces Real-Time Contemporary Project Management]
 +
*[http://workflowy.com/ Workflowy.com]

Latest revision as of 23:09, 11 August 2012

Glossary.svg This page describes a concept which is part of our glossary
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.


Agile

Scrum Principles

The framework and terminology are simple in concept yet difficult to implement. Successful Scrum teams embrace the values upon which Scrum is based (paraphrased from the Agile Manifesto):

We value
  • Individuals and interactions over processes and tools
  • Completed functionality over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

That is, while there is value in the items on the right, the items on the left matter more.

True success with the Scrum framework comes from teams and organizations who understand these values and the principles that form the foundation of all agile processes.

Agile Scrum links

Open source software

See also

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