Comments on: 12 Principles of Risk Management (PMBOK – with an Agile slant) http://agile101.net/2009/07/28/12-principles-of-risk-management-pmbok-with-an-agile-slant/ Agile Project Management, Programme Management and Digital Publishing Sat, 17 Sep 2011 20:53:37 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Bill Haseltine http://agile101.net/2009/07/28/12-principles-of-risk-management-pmbok-with-an-agile-slant/comment-page-1/#comment-11346 Bill Haseltine Wed, 06 Jul 2011 10:37:32 +0000 http://agile101.net/?p=436#comment-11346 Good article, and I STRONGLY ENCOURAGE everyone to read Andy Bruce's earlier response. Andy has nailed the often missed point - the PMBOK approach is based on the Waterfall Method; and to me, as important, the Agile Method is best used in Gov't work where the PMO is "hands off" (that takes a lot of trust in the Development Team) and doesn't need documentation for long-term support of the software (maintenance, compatibility, training, etc). IMHO, this article is a good "first step" at trying to "bridge the gap" between the Waterfall and Agile methods within the PMBOK Risk Management construct. Good article, and I STRONGLY ENCOURAGE everyone to read Andy Bruce’s earlier response. Andy has nailed the often missed point – the PMBOK approach is based on the Waterfall Method; and to me, as important, the Agile Method is best used in Gov’t work where the PMO is “hands off” (that takes a lot of trust in the Development Team) and doesn’t need documentation for long-term support of the software (maintenance, compatibility, training, etc). IMHO, this article is a good “first step” at trying to “bridge the gap” between the Waterfall and Agile methods within the PMBOK Risk Management construct.

]]> By: sahib josh http://agile101.net/2009/07/28/12-principles-of-risk-management-pmbok-with-an-agile-slant/comment-page-1/#comment-10787 sahib josh Mon, 07 Feb 2011 17:10:11 +0000 http://agile101.net/?p=436#comment-10787 good article, articulate and precise enough for starters. good article, articulate and precise enough for starters.

]]> By: Andy Bruce http://agile101.net/2009/07/28/12-principles-of-risk-management-pmbok-with-an-agile-slant/comment-page-1/#comment-1997 Andy Bruce Sat, 18 Dec 2010 03:58:43 +0000 http://agile101.net/?p=436#comment-1997 What an interesting idea! I'm learning all about PMBOK and I have to say that, IMHO, Risk Mgmt with PM (with all that implies) really doesn't fit the PMBOK model. Not that I'm dissing Agile (I work in a true PMO environment and the amount of time spent on artifact management is staggering). Both Waterfall (and, let me just say it, PMBOK is Waterfall as a deluge) and Agile want to do the right things: deliver a quality product. Risk management is key to both: Waterfall by careful planning and eliminating surprise, Agile by realizing that for SW dev in particular you really "don't know what you don't know" so you have *trust* and work *closely* with your sponsor. It's just that PMBOK and Agile define "Quality" fundamentally differently: PMBOK says "conformance to requirements" and Agile says "meets users real needs" (especially where those needs aren't known, hence "we welcome change" in Agile which is *absolutely not* the approach and methodology under PMBOK). Waterfall is great for building roads, not so good for building software. Agile doesn't work well in firm-fixed price (read: all Gov't work) except where you have a lot of trust and little need for auditable documentation artifacts. What an interesting idea! I’m learning all about PMBOK and I have to say that, IMHO, Risk Mgmt with PM (with all that implies) really doesn’t fit the PMBOK model.

Not that I’m dissing Agile (I work in a true PMO environment and the amount of time spent on artifact management is staggering). Both Waterfall (and, let me just say it, PMBOK is Waterfall as a deluge) and Agile want to do the right things: deliver a quality product. Risk management is key to both: Waterfall by careful planning and eliminating surprise, Agile by realizing that for SW dev in particular you really “don’t know what you don’t know” so you have *trust* and work *closely* with your sponsor.

It’s just that PMBOK and Agile define “Quality” fundamentally differently: PMBOK says “conformance to requirements” and Agile says “meets users real needs” (especially where those needs aren’t known, hence “we welcome change” in Agile which is *absolutely not* the approach and methodology under PMBOK).

Waterfall is great for building roads, not so good for building software.

Agile doesn’t work well in firm-fixed price (read: all Gov’t work) except where you have a lot of trust and little need for auditable documentation artifacts.

]]>