Activities Don't Count…So Don't Count Them
- Topics:
- Project Management
- Tags:
- 4PM.Com,
- Strategy,
- Software,
- Project Management,
- Product Marketing,
- Marketing,
- Management,
- It service Management,
- It Operations,
- Enterprise Software,
- ...
- Source:
- 4PM.Com
FREE Registration is required
Overview: The article starts with a story and the morals of the story that the activity of writing code, while certainly necessary, does not really count. What counts is improving customer service. The PM should count and reward the programmer’s measured contribution to the larger customer service achievement rather than the activity of coding. This is achievement-driven project management. Another moral in this story concerns the amount of reward "horsepower" to put behind whatever performance metric we use. Readers familiar with the ahievement-driven Project Management understand the difference between activities and achievements. The second decision a PM must make concerns the magnitude of the consequences we associate with the measured achievements.
(Is this item miscategorized? Does it need more tags? Let us know.)
Format: PDF | Size: 155KB | Date: Jan 2003 | Pages: 2




