Difference between revisions of "Project management"

From Organic Design wiki
m
(Project'Or RIA)
 
(30 intermediate revisions by 5 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.
 
−
Let us figure out how we are going to avoid them.
 
  
−
== Objectives and Goals - Don't Start Without Them==
+
== Agile ==
  
−
Before you start, have a purpose. Before a bid is created for project, you need to be absolute regarding Goals and Objectives of the project. The Goals are the mission statement for the project and indicate the general business purpose for the project.
+
=== 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):
  
−
'''Sample Goal''' -  Here at Widgets-R-Us we would like to improve our customer service by better addressingg the complaints of customers.<br><br>
+
;We value
−
The objectives are more tangible directives for the project that corellate directly to the specifications for the design and development cycles. There should always be a meet-exceed metric for these objectives.
 
  
−
'''Sample Objective''' - We need to develop a tool for service reps to log Customer name and address information and the nature of the complaint.
+
*Individuals and interactions over processes and tools
−
'''Another Sample Objective''' - We want to require classification of the complaint so the complaint can be routed properly.
+
*Completed functionality over comprehensive documentation
 +
*Customer collaboration over contract negotiation
 +
*Responding to change over following a plan
  
−
== Specifications - Defining Done ==
+
That is, while there is value in the items on the right, the items on the left matter more.
−
I know I have had too much experience in projects from hell that for some reason don't appear to have an end. This is almost always due to poor scope or scope creep. The statement of objectives and sign off on specification define the endpoint and thus no scope creep. need to explain a good spec here.
 
  
−
== Tasks ==
+
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.
−
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<br>
 
−
'''Diagram 1 - The Decomp of Objectives to Task'''
 
−
<br>
 
−
http://www.sequoiais.com/pm/pm_molecule_execution.gif<br>
 
  
−
== Contributors - Who Gets to Play ==
+
=== Agile Scrum links ===
−
<br>
+
*http://www.youtube.com/watch?v=_BWbaZs1M_8
−
Explaing the staffing model of project. Determining who is going to assume what role. Distributed players<br>
+
*http://www.coachingagileteams.com/what-is-agile/
−
http://www.sequoiais.com/pm/pm_molecule_participants.gif<br>
+
*http://www.youtube.com/watch?feature=player_embedded&v=OuhZAVJO3xw
  
−
'''Project Management Tools'''<br>
+
== Open source software ==
−
There are ample tools out there for a project manager to chose from. The major problem have seen with all the tools I have used or reviewed is that they are generally geared towards micromanagement and they don't scale well for smaller projects.
+
*[http://projectorria.toolware.fr/ Project'Or RIA]
  
−
A good project management tool should be the product of a sucessful Functional Decomposition where the independant functions can scale dependending upon the complexity of each PM component. explain that a project may be heavy on goals and objective definition(thus much consulting) and easy on execution. other project easy on scope and spec but difficult on task execution.
+
== See also ==
−
 
+
*[[Organisation]]
−
For instance, If you are planing on going to lunch with a freind to talk about PM, the PM tool should allow you to simply schedule the time and person(s) participating. If that lunch date grows into a working meeting, you may need to record materials you need to bring to the table. If that lunch meeting grows into a departmental presentation, you may need to chose and select a caterer, reserve a room, rent a projector, log expenses and send out invitations. And now that you are a 'Relative Expert' on PM your lunch meetings have become full blown seminars, you need a means to log the contact info of the members or your road show, create a task list, asssign reponsibilities, establish a budget, collect quotes, track various statuses..etc.
+
*[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''
−
 
+
*[[MW:Extension:Semantic Project Management]]
−
'''Project Management Checklist''' as initially designed for the Project Molecule:<br>
+
*[http://www.readwriteweb.com/archives/project_management_mechanical_turk_smartsheet_looks_awesome.php Project Management + Mechanical Turk? Smartsheet Looks Awesome]
−
http://www.sequoiais.com/pm/pm.gif<br>
+
*[http://www.readwriteweb.com/archives/wedoist_introduces_real-time_contemporary_project.php Wedoist Introduces Real-Time Contemporary Project Management]
−
<br>
+
*[http://workflowy.com/ Workflowy.com]
−
 
 
−
'''Project Stages Checklist''' as initially designed for the Project Molecule:<br>
 
−
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.
 
−
 
 
−
 
 
−
 
 
−
Projects also follow the [[ETVX]] model:
 
−
 
 
−
Using the [[ETVX]] Model can be extended or simplified(depending on the perspective)to include the following:
 
−
*([[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
 
−
 
 
−
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.
 
−
[[User:Aregularjoe|Aregularjoe]] 06:27, 5 Oct 2006 (NZST)
 
−
 
 
−
;See also
 
−
*[[Wikipedia:Project management]]
 
−
*[[Wikipedia:List of project management topics]]
 

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"