Comments for 42 http://blog.hazware.com Random postings based on thoughts that I may or may not have had. Most need to be filtered through a babelfish. Thu, 9 Sep 2010 06:24:52 +0000 http://wordpress.org/?v=2.0.3 Comment on Defining Project Success by hazi http://blog.hazware.com/?p=15#comment-10 Mon, 19 Jun 2006 13:32:38 +0000 http://blog.hazware.com/?p=15#comment-10 Pier, Thank you for you comment. You are correct. I did forget the first part of you definition - concerning time, costs, & quality. Please forgive my misquote. I believe the difference stems from my view of managing software development. I believe it is important to distinguish between success and efficiency. The time, cost, quality, & happiness criteria are parts of the efficiency equation. Success is based on solely on delivering the stated goals. Maybe I am just splitting hairs. I see the ability to divide the classifications as the ability to address each independently. This is not to say they do not impact each other, they absolutely do, but in dividing them I can prioritize to a finer degree. I can also choose to sacrifice efficiency for success, if necessary. It is not my goal to do so, but it is a tool I can use to achieve the longer term goals of the governing strategy. The catch is to minimize these sacrifices so as to avoid a phyrric victory. On agile software development, I will discuss that another time. For me the jury is still out. I have seen success & failures using ASW. I do use some ASW concepts, but I am not sold on the whole model yet. Thanks again for you comment. hazi Pier,

Thank you for you comment.

You are correct. I did forget the first part of you definition - concerning time, costs, & quality. Please forgive my misquote.

I believe the difference stems from my view of managing software development. I believe it is important to distinguish between success and efficiency. The time, cost, quality, & happiness criteria are parts of the efficiency equation. Success is based on solely on delivering the stated goals. Maybe I am just splitting hairs. I see the ability to divide the classifications as the ability to address each independently. This is not to say they do not impact each other, they absolutely do, but in dividing them I can prioritize to a finer degree. I can also choose to sacrifice efficiency for success, if necessary. It is not my goal to do so, but it is a tool I can use to achieve the longer term goals of the governing strategy. The catch is to minimize these sacrifices so as to avoid a phyrric victory.

On agile software development, I will discuss that another time. For me the jury is still out. I have seen success & failures using ASW. I do use some ASW concepts, but I am not sold on the whole model yet.

Thanks again for you comment.
hazi

]]> Comment on Defining Project Success by PierG http://blog.hazware.com/?p=15#comment-9 Mon, 19 Jun 2006 13:09:06 +0000 http://blog.hazware.com/?p=15#comment-9 Hazi, first of all thankyou for quoting me. Well ... I wrote that the success is when you have time, costs and quality AND when customer and the team is happy. I do think that delivering perfect software in term of time, costs and quality AND not meeting 'changing and crazy' customer expectation is a failure. Yes it's hard AND we don't have to surrender ... there MUST be a way to cope with this (agile sw dev?)! Ciao, PierG Hazi,
first of all thankyou for quoting me.

Well … I wrote that the success is when you have time, costs and quality AND when customer and the team is happy.

I do think that delivering perfect software in term of time, costs and quality AND not meeting ‘changing and crazy’ customer expectation is a failure.

Yes it’s hard AND we don’t have to surrender … there MUST be a way to cope with this (agile sw dev?)!

Ciao,
PierG

]]>