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.