The Unchangeable Rules of Software Change

BradAppleton  posta questa idea sul gruppo di yahoo AgileProjectManagement

My own "anecdotal and case-study evidence" has led me to a set of
"unchangeable rules of software change" that I often convey to new
developers and teams. I blogged about them at
and they are:

==> Rule #0: The Requirements/Plans ARE going to change! (Change is Inevitable)

==> Rule #1: There isn't a darn thing you can do to prevent Rule #0.
(Resistance is Futile)

==> Rule #2: The more you try to deny and defy rule #1 by attempting
to prevent rule #0, the worse things will get. (Change is like
quicksand - Fighting only makes it worse)

==> Rule #3: The more flexible and adaptive you are at accommodating
change, the more control you will have over it. (Embrace change to
control change)

La riporto qui perche' mi sembra veramente interessante e perche' forse non tutti sanno dell'esistenza di questo interessantissimo gruppo.

Print | posted on giovedì 19 gennaio 2006 20:08


# original yahoo discussion

left by Pingback/TrackBack at 02/02/2006 14:58 Gravatar
original yahoo discussion

# Meridia.

left by Meridia. at 29/03/2009 20:00 Gravatar
C health meridia. Meridia clinic toronto. Meridia meridia. Meridia. Meridia reviews.
Comments have been closed on this topic.