The Regenerate Web
facilitating the regeneration of software teamsNavigation
User login
Syndicate
Services
Project
- delivery (3)
- duration (1)
- effort (3)
- estimation (4)
- Iterative (1)
- measurement (1)
- metrics (1)
- Planning (2)
- PMI (1)
- PMBOK
- Progressive Elaboration (1)
- risk (1)
- Rolling Wave (1)
- schedule (1)
- task (2)
- velocity (6)
- duration (1)
- effort (3)
- estimation (4)
- Iterative (1)
- measurement (1)
- metrics (1)
- Planning (2)
- PMI (1)
- PMBOK
- Progressive Elaboration (1)
- risk (1)
- Rolling Wave (1)
- schedule (1)
- task (2)
- velocity (6)
Management
Browse archives
| Su | Mo | Tu | We | Th | Fr | Sa |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |
Analysis
- abstraction (1)
- metaphors (1)
- modeling (3)
- requirements (5)
- research
- semantics (1)
- Analysis (1)
- metaphors (1)
- modeling (3)
- requirements (5)
- research
- semantics (1)
- Analysis (1)
Staff
Who's online
There are currently 0 users and 1 guest online.
PMI
Project Management as a Discipline
Submitted by regen_r8 on Sat, 2006-08-05 13:29.
PMI
I was reading on Random Thoughts of a CTO this post "Are you focused on what's really important on a project?". I really liked where he was going with this. I wholeheartedly agree with Skip's statements about projects and outcomes. In this post, I am exploring what I see as some of the contributing factors to this phenomenon.
The problem with project management as a discipline of practice (profession?) is that it tends to be more focused on the mechanics of the project process, than on the usage of that process as a means to an end.