how agile software development address issue of complex business proccesses ?

organisation now a days want to outsource their business processes. some want to automate them. previously , the issues were not complex. but , with merger acquisitions , changing ( volatile ) business environs , the business model changes frequesntly. Alistair , you have mentioned in one of your papers " Software development as community petry wiritng " about business cultures , people cultures & historical values.
how agile addresses all these issues in this chaos rather today's melting pot of technology environment ?

"Agile" software development is about getting software out effectively and soon. I would think that the more complex the business situation, the more important to have the "soon" part of that story.
Alistair

what I meant was how the critical business processes are identified as the business model is constantly changing ?
how it is adjudged in agile ?

I'm a big fan of "key people know where they are hurting and what is most important". In my experience, they KNOW what needs to be done.
If they don't, then they make mistakes, and lose big time.
I don't know of any process to change the outcome of this situation.

This seems to highlight the importance of being close
to the customer. The requirements are the qualities
desired in the software to help that person do some
work that the business needs. That person and their
expertise are part of the "business model" from
the inside.
Open source software can often succeed when the same
people doing the development are the ones who will
use the software. They know that they don't need an
animated paper clip!
Thanks,
Joe