RE: [agilefinland] On Agile and Risk, Agile does not increase risks in software development.
Hiya,
Though I agree, of course.
Wasn't the risk in this context meaning "the risk of doing something
different".
So, it would be the same if the team would move to TSP.
Bas
>-----Original Message-----
>From:
agilefinland@yahoogroups.com
>[mailto:
agilefinland@yahoogroups.com] On Behalf Of ext duarte_vasco
>Sent: 16 December, 2006 19:44
>To:
agilefinland@yahoogroups.com
>Subject: [agilefinland] On Agile and Risk, Agile does not
>increase risks in software development.
>
>--- In
agilefinland@yahoogroups.com, "Lasse Koskela"
><lasse.koskela@...> wrote:
>>
>> On 6/15/06, Mikko Kurki-Suonio <maxxon@...> wrote:
>> > When you really think about it, everyone wants the
>agility of agile
>> > development but nobody wants the risk that goes with it.
>
>I'm sorry to disagree here. Agile methods (not talking of
>Agile as in "Agile Values") do not increase any risk inherent
>to any software development project.
>
>A "Risk" (let's talk about the abstract concept of Risk here)
>exists independently of the development mehotodology that you take.
>
>Agile does not increase the Risk in a project.
>
>Furthermore, according to Agile (the values now) you sould
>value "people and interactions"
>over "processes and tools" (the people value). That in effect
>is a recipe for reducing risk. In software projects risks
>don't get handled by processes, processes can at best help
>handle risks, but ultimately people handle risks. If you
>follow the people value you will more likely solve the risks
>that will (inevitably) realise in any software project.
>
>> >
>> > Businesses pay others to take the risks for them. If they want to
>> > take the risk, it's their core business and they want to
>do it themselves.
>
>Let me see if I understand. Are you suggesting that by
>following a waterfall, spiral or iterative (but not agile)
>methodology you are "eliminating" the risk for the customer?
>
>I'm sorry, but if that's what you are suggestion I could not
>disagree more. Just look at the Chaos report and the huge
>percentage of failed projects that _used_ other than agile
>methodologies.
>
>> >
>> > IMHO, the key to selling agile is finding a way to carry the risk
>> > for the customer while still keeping the agile methodology.
>
>What do you mean by "carry the risk for the customer"?
>
>
>
>
>Yahoo! Groups Links
>
>
>
>