Comments on: Training Precedes Project Integrity http://www.reformingprojectmanagement.com/2003/01/14/93/ The magazine for the project age Fri, 04 Jul 2008 13:35:36 +0000 http://wordpress.org/?v=2.0.5 by: Hal http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-437 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-437 Thanks Joe. :+: Thanks Joe. :+:

]]> by: Mary Poppendieck http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-438 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-438 I have a fundamental difference with Hank Winters on project management training for IT, and what is important for achieving project success. Virtually all the training he points to advocates scope definition, front end specifications, and specification tracking. This approach does not recognize, let alone address, the basic problem with software projects – that is, early, detailed specification is the wrong approach for any but the most routine development. Premature specification in software development leads to excess features, customer dissatisfaction and brittle systems that resist future change. In my opinion, the standard mantra about how to train project managers is precisely what leads to a large number of software project failures. Mary Poppendieck I have a fundamental difference with Hank Winters on project management training for IT, and what is important for achieving project success. Virtually all the training he points to advocates scope definition, front end specifications, and specification tracking. This approach does not recognize, let alone address, the basic problem with software projects – that is, early, detailed specification is the wrong approach for any but the most routine development. Premature specification in software development leads to excess features, customer dissatisfaction and brittle systems that resist future change.

In my opinion, the standard mantra about how to train project managers is precisely what leads to a large number of software project failures.

Mary Poppendieck

]]> by: Hal http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-439 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-439 Mary, I couldn't have said it better. :+: However we both agree with his conclusion on poorly trained project managers. We'd just teach a different approach. ;) Mary, I couldn’t have said it better. :+: However we both agree with his conclusion on poorly trained project managers. We’d just teach a different approach. ;)

]]> by: Hal http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-440 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2003/01/14/93/#comment-440 Buck, Please send me an email. I'd like to discuss this further with you. Thanks Buck,

Please send me an email. I’d like to discuss this further with you.

Thanks

]]>