I have predicted for some time (although not brave enough to do so publicly) that the manner in which the finance and other industries conduct their business operational processes, both Architecturally at all levels and from a Software Development perspective, would cause spectacular business failure in some form or another at some point. As it turns out that amongst other things it was a lack of understanding and communication about the Business Architecture and Business Models that have appeared to cause this failure. 

This paper explores some of the potential causes, and why people don’t speak up too loudly… (and can’t be too explicit). Obviously it has become easier now that we have the evidence and proof, but will anyone listen and more importantly act on improving their Enterprise Architecture – specifically the Business Architecture? 

Read further in this blog: Is lack of EA partly to blame for the Finance Industry collapsing quite so spectacularly?

You can find the detail here: http://www.ibm.com/developerworks/rational/practices/ but they describe a practice as:

"Generally speaking, a practice is set of techniques for accomplishing a goal. Usually a part of a larger process, a practice represents a chosen way to pursue a related goal. For example, suppose you want to write a story. Some possible practices are:

• Draft an outline, then evolve each section.
• Draw a cartoon of key story elements, then write the story.
• Create a character and a conflict, and then write the story from start to end.

A storyteller could choose one of these practices, or a combination of them. For each practice, there can be tool-specific guidance (tool mentors), that tell you how to create outlines in a word processor, or how to create cartoons using a graphics tool and clip art library.  In terms of software development, a practice:

• Addresses one aspect of the software development lifecycle: e.g., requirements management, use-case driven development, change management, etc.
• Evolves as improvements are discovered over time
• Is based on what has been proved successful, not on abstract scientific principles."

The AgileEA will develop the Enterprise Architecture set of Practices in this manner going forward. Partitioning apects of Enterprise Architecture into logical groups of closely related ideas, and issuing them as stand alone Components that can be used individually or together in concert.