[AM] Need opinions from All Experts here!

M***@Graybill.com

2004-02-25 16:48:00 UTC

A revolutionary publication is about to become
available that is being written by a local university
professor (interdisciplinary) on a topic that hasn't
been tackled in full scope - ever. The concepts within
has direct correlation with software development
methodologies. The topic is the principles of
prediction and timing.

I'll give you an example: Right now, close your eyes
and visualize yourself unlocking the front door to your
home and walking in. Most people can do that very
well. However, most people also failed to picture all
the events and tasks leading up to opening their front
door.

If they are coming home from work, the preface scene to
opening their front door would look different than say
coming home from shopping or church or another activity
- all activities different enough to alter the scope of
the total scene ending with walking in the front door.

Developing software has the same problem, only the
variables are far greater in number, more detailed and
intangible and obscure (because they rely too much on
factors related to fallibilities in human nature.)

When we think about the main problems in software
(soliciting feedback here), such as predicting events
or conditions that alter the scope, required resources
or time frame (at alia), or due to boundaries of such
things, the software is "stuck" to the concepts and
designs imposed on it at the onset of the project, and
it does not have the freedom to evolve; thus, the
customer does not get the value and function they
expected.

If we could take a project, allow it to evolve by
taking as much time, expending as much resources, and
giving time for re-engineering and refactory, while
documenting every unexpected turn, every detail of
re-engineering or refactoring -- where in the end it
not only delivers all the value the customer expected
but more and with the highest software quality. Then
if we accomplish a complete analysis of that software,
developing detailed requirements and a full project
audit, we could use that information and do it all over
again and be precise at our predictions, and we could
use whatever methodology fits the best - it simply
wouldn't matter, IMHO.

But unfortunately, this is fantasy - people are not
crystal balls - they err constantly. Real situations
call for pragmatic and sometimes drastic measures to
maximize the delivery of value as early as possible,
and be most amenable to change. This is what I see as
"Agile."

Alistair called software development a "cooperative
game of communications and invention." (If my memory
serves correctly.)

So the total problem can be stated as follows
(abstracted into two main categories, IMHO).

1. Failure at adequately predicting the future.
- fail to foresee latency
- fail to foresee embedded details
- etc.
2. Conceptual entropy.
- transfering domain & system concepts is lossy
- premature conceptual elaboration (requires
evolution)
- etc.

Just my thoughts.

Mark

Post by SChing Chan
Hi All,
Im a new member here. Recently, Im doing a report on
the traditional
methodologies, such as waterfall, spiral and
prototyping models to the
modern Agile methodologies. I came to read about
Agile from one of
the books Agile Modelling by Scotts Ambler, Agile
Software
Development Ecosystem by Jim HighSmith and know some
of the issues,
pros and cons.
And I got to know this discussion web site from a
friend. So hopefully
to hear from the experts gathering here in this web
site your point of
views about what you all think about the differences
between traditional
and the nowadays modern Agile methodologies. Hope to
hear from you all
about the methods; pros and cons, and many points,
which we all miss out
or heard before. And hope to let you all know that

Ill

Post by SChing Chan
be using some of
your useful points as part of my analysis in my

report.

Post by SChing Chan
If possible, I hope you can send your individual email
to
comments better.
Thank you for anyone who will provide me with his or
her point of views.
Your great help is appreciated. :)
Regards,
SChing
For more information about AM, visit the Agile

Modeling

Post by SChing Chan
Home Page at www.agilemodeling.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"The significant problems we face cannot be solved at
the same level of thinking we were at when we created
them." - Albert Einstein

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: gcma-***@gmane.org

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: agilemodeling-***@topica.com

TOPICA - Start your own email discussion group. FREE!
http://www.topica.com/partner/tag02/create/index2.html
--^----------------------------------------------------------------