Comments on: What Can We Learn about Projects from Philosophy? http://www.reformingprojectmanagement.com/2005/11/07/548/ The magazine for the project age Fri, 08 Aug 2008 21:03:49 +0000 http://wordpress.org/?v=2.0.5 by: Hal http://www.reformingprojectmanagement.com/2005/11/07/548/#comment-1865 Fri, 11 Nov 2005 19:23:26 +0000 http://www.reformingprojectmanagement.com/2005/11/07/548/#comment-1865 Bob, My comment about being led in a different direction is about giving up on trying to understand our current difficulties before producing a new perspective. Lauri suggests that our difficulty is associated with our paradigm rather than the theories that current practice is based on. I think he is onto something. Thanks for reading and commenting, Hal Bob,

My comment about being led in a different direction is about giving up on trying to understand our current difficulties before producing a new perspective. Lauri suggests that our difficulty is associated with our paradigm rather than the theories that current practice is based on. I think he is onto something.

Thanks for reading and commenting,
Hal

]]> by: Mishkin Berteig http://www.reformingprojectmanagement.com/2005/11/07/548/#comment-1864 Fri, 11 Nov 2005 15:21:59 +0000 http://www.reformingprojectmanagement.com/2005/11/07/548/#comment-1864 Hal, I've been looking into the question of the underlying philosophy that is driving Agile for a while now. When I first looked at the Agile Manifesto, I was impressed but I noticed that there were some basic unstated assumptions hidden behind it. I've taken an attempt at uncovering those basic assumptions, the Agile Work Axioms, separated from any consideration of software. They're listed at http://www.agileaxioms.com and my blog, http://www.agileadvice.com is all about their implications. Hal, I’ve been looking into the question of the underlying philosophy that is driving Agile for a while now. When I first looked at the Agile Manifesto, I was impressed but I noticed that there were some basic unstated assumptions hidden behind it. I’ve taken an attempt at uncovering those basic assumptions, the Agile Work Axioms, separated from any consideration of software. They’re listed at http://www.agileaxioms.com and my blog, http://www.agileadvice.com is all about their implications.

]]> by: Bob Wells http://www.reformingprojectmanagement.com/2005/11/07/548/#comment-1861 Fri, 11 Nov 2005 04:28:24 +0000 http://www.reformingprojectmanagement.com/2005/11/07/548/#comment-1861 Hal, I understand the need to read this three times, maybe more. There is a lot said in this paper that I do not yet understand. To provide a foundation for thought, I am using the analogy of an orchestra, and its WBS, the instruments, players and sheet music to understand the things aspect, as compared to performed orchestral music, to understand the process aspect. This is helping me see the point about metaphysics: the temporal nature of process and the nature of analysis of processes versus things. Is there something more to your comment about being lead in a different direction? The references alone are a hoot. Hal, I understand the need to read this three times, maybe more. There is a lot said in this paper that I do not yet understand. To provide a foundation for thought, I am using the analogy of an orchestra, and its WBS, the instruments, players and sheet music to understand the things aspect, as compared to performed orchestral music, to understand the process aspect. This is helping me see the point about metaphysics: the temporal nature of process and the nature of analysis of processes versus things.

Is there something more to your comment about being lead in a different direction?

The references alone are a hoot.

]]>