http://msdn.microsoft.com/architecture/default.aspx?pull=/library/en-us/dnbda/html/motionlite.asp
Abstract
The work in Motion Lite is really pretty simple. Look at a business's project portfolio today, personalize a capability map for that business, link each project to a capability, and then ask some or all of the 20 questions about those projects. We use the new "lens" created by the 20 questions to look at the project portfolio, revealing what we did not know before, and we act accordingly.
Introduction
Motion Lite is a two-day methodology derived from the more intensive Motion methodology.
Motion Defined
Motion uses business architecture to expose the business model of an organization, and then applies that information either to resolving a specific problem, or to informing decisions related to project prioritization and selection. Motion includes a patent-pending business architecture model, a template-rich methodology, and a variety of tools for capturing the business architecture and business model information in a highly stable, objective, and metric-rich format. That business architecture information can be linked to process, organization, and IT architecture information. By design, everything about Motion is technology-agnostic and mostly acronym-free.
Motion Lite Defined
Motion methodology projects are typically eight weeks in length, and involve modeling your business architecture and choosing a project with the maximum value. In comparison, Motion Lite is a two-day short course, to introduce the concepts of business architecture as used by Motion, and to get you started on project prioritization using this technique. During the first day, you will build a high-level capability map of your business, leveraging one of over a dozen industry-specific templates in the Motion library. During the second day, you will look at the business value, maturity, and interconnectedness of your capabilities—among other specific attributes—and use that information to see how the Motion technique changes the way you think about project prioritization and selection.
[...]