The level of software quality attainable is a reflection of an organizational business decision. There are many factors that influence this decision, including development, build and testing environments effectiveness, resources and their associated skillset, integrity, motivations and experience levels, commercial agreements, and adopted processes and productivity tools.
Lynne Cazaly spoke at the recent Agile New Zealand conference on the importance of clarity and sense-making in a world where VUCA (volatility, uncertainty, complexity, ambiguity) is the norm. She presented ideas on how to convey messages more effectively using visual tools and gave the audience a quickfire class on communicating using simple images.
Agile is the hand that works in the glove. SOA is the glove, the scope is enterprise wide. Most principles of SOA and Agile are not in conflict. When they are, they keep each other sane. Agile development without a clear vision of the goals and objectives of the company is futile. SOA without a clear vision how to make it real using agile development principles is a waste of time and money.
Dr. Linda Rising talks about experiments conducted many years ago, presenting how deep, powerfully affecting, and difficult to avoid are human “prejudices” and “stereotypes”. 1
Developers and the business use numbers differently, leading to poor communication. Here the "Spirit of Agile" tells a developer the trick: translate non-computational issues into number language. 3