Comments on: More on PM Methodologies: Be Selective! http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html Dealing with software projects in real life Fri, 10 Feb 2012 19:07:34 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Pawel Brodzinski http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2181 Pawel Brodzinski Mon, 02 Mar 2009 07:00:00 +0000 http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2181 I know your background so I have no other choice but to agree. Personally I haven't worked in environment where such alignment was required although I can think of a few examples. Anyway I think that vast majority of projects which are done don't fall into "follow the manual" approach in any place. I know your background so I have no other choice but to agree. Personally I haven’t worked in environment where such alignment was required although I can think of a few examples. Anyway I think that vast majority of projects which are done don’t fall into “follow the manual” approach in any place.

]]> By: Glen B. Alleman http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2180 Glen B. Alleman Mon, 02 Mar 2009 02:38:00 +0000 http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2180 Pawel,<br/>I'd say that the difference between a toolbox item and manual to follow are domain dependent.<br/>The monthly statusing of Control Accounts on a NASA program are "step-by-step" processes performed exaclty the same way every month.<br/>The creation of the baseline for the next rolling wave on the same program is "step-by-step" for the framework, but the content is highly situationally dependent on the engieering processes.<br/>With those step-by-step processes the ad hoc processes have no framework in which to be developed.<br/>This is the core difference and princple and practice. Pawel,
I’d say that the difference between a toolbox item and manual to follow are domain dependent.
The monthly statusing of Control Accounts on a NASA program are “step-by-step” processes performed exaclty the same way every month.
The creation of the baseline for the next rolling wave on the same program is “step-by-step” for the framework, but the content is highly situationally dependent on the engieering processes.
With those step-by-step processes the ad hoc processes have no framework in which to be developed.
This is the core difference and princple and practice.

]]> By: Pawel Brodzinski http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2179 Pawel Brodzinski Sat, 28 Feb 2009 16:27:00 +0000 http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2179 Raven,<br/><br/>For me methodologies used in project management or software development were always more like a toolbox rather than a manual to follow up. When you have a toolbox you use tools which suit you fine in a specific situation. There's no need to use a hammer every single time.<br/><br/>What more you can achieve the same results different ways - sometimes it takes more effort sometimes less. Sometimes you have other tools that these from your toolbox which helps you to do the job. I see no point in throwing them away only because it wasn't a part of a brand new toolbox you bought the other day. Raven,

For me methodologies used in project management or software development were always more like a toolbox rather than a manual to follow up. When you have a toolbox you use tools which suit you fine in a specific situation. There’s no need to use a hammer every single time.

What more you can achieve the same results different ways – sometimes it takes more effort sometimes less. Sometimes you have other tools that these from your toolbox which helps you to do the job. I see no point in throwing them away only because it wasn’t a part of a brand new toolbox you bought the other day.

]]> By: Raven Young http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2178 Raven Young Sat, 28 Feb 2009 16:09:00 +0000 http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2178 Pawel - Thanks for sharing my post and I totally agree this is the best tip in the bunch! <i>Being selective</i> with what (or how) to implement from a given process, standard or methodology is key to making it work in your specific org, group and team. Pawel – Thanks for sharing my post and I totally agree this is the best tip in the bunch! Being selective with what (or how) to implement from a given process, standard or methodology is key to making it work in your specific org, group and team.

]]> By: Pawel Brodzinski http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2177 Pawel Brodzinski Sat, 28 Feb 2009 09:04:00 +0000 http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2177 Glen, you're right. We so often hear to follow this method or another but we seldom think why a specific technique should be used. Which principle is covered and if that's the best way to do the job.<br/><br/>That's what I have on my mind every time when I'm talking about choosing wisely which techniques you should use when implementing new methodology. I've seen a couple of times situation when practices doing good job with covering key principles of project management were thrown away just because they didn't align with new cool methodology. No one thought why they have been in the place, which principle stands behind them and whether new methods will do the same or better job. Glen, you’re right. We so often hear to follow this method or another but we seldom think why a specific technique should be used. Which principle is covered and if that’s the best way to do the job.

That’s what I have on my mind every time when I’m talking about choosing wisely which techniques you should use when implementing new methodology. I’ve seen a couple of times situation when practices doing good job with covering key principles of project management were thrown away just because they didn’t align with new cool methodology. No one thought why they have been in the place, which principle stands behind them and whether new methods will do the same or better job.

]]> By: Glen B. Alleman http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2176 Glen B. Alleman Sat, 28 Feb 2009 04:03:00 +0000 http://blog.brodzinski.com/2009/02/more-on-pm-methodologies-be-selective.html#comment-2176 Pawel,<br/>What we've started doing is to focus on the "principles" of managing projects before moving the the "practices."<br/>This provides an anchor for assessing the approporiateness of the practice. <br/>A problem is there are only a few descriptions of the principles and many - possibly too many - practices. Pawel,
What we’ve started doing is to focus on the “principles” of managing projects before moving the the “practices.”
This provides an anchor for assessing the approporiateness of the practice.
A problem is there are only a few descriptions of the principles and many – possibly too many – practices.

]]>