Concept: Unified Method Framework (UMF)
The Unified Method Framework (UMF) is a practice framework in which different practices from many different contexts and developed by many different organizations can co-exist, sharing a common infrastructure.
Relationships
Main Description

The Unified Method Framework (UMF) is an extensible integration framework that defines a “common language” for the interoperation of Practices . 

umf_graphic 


The UMF provides:

  • A common library structure for plug-ins
  • Shared categorization schemes and standardized views
  • Common standards and QA criteria
  • Common development guidance linked to licensing levels, governance and overall approach to quality
  • Compatible and cooperative authoring processes
  • A shared set of core method elements for building related processes

In its broadest sense, the UMF is a virtual library of all methods developed within its constraints.

The benefits of the UMF are the same as for any practice framework.  Specifically:

  • Defines a consistent approach for how plug-ins are structured that allows true plug-and-play between content authored by different groups and ensures that remotely authored content integrates seamlessly into the overall library
  • Reduces complexity and increases understandability of the methods as all methods are constructed/structured in a similar way
  • Maximizes reuse as common elements are shared across practices and practices are shared across processes.  Practices also provide a coarser-grained unit of reuse and customization than just work products
  • Increases configurability as practices can be easily configured to produce many different types of method assets (i.e., processes) to match specific needs. Practices are loosely coupled and interchangeable.  Practices are easily “swapped out” and can be "mixed and matched" to create the best solution.  Specifically, processes can be assembled to best suit the end user's needs -- specific practices, role assignments, categorization (domains, work product kinds, disciplines, work products, role sets), etc.  Processes can be assembled to best suit your needs -- specific practices, role assignments, categorization (domains, work product kinds, disciplines, work products, role sets), etc.
  • Supports incremental method authoring. Practices are written independently from each other.  Practices are dependent on a shared core and not on each other.
  • Supports incremental adoption of a process. The process is divided into practices that can be adopted individually and incrementally.  You can start small with a few practices and then grow/scale, adopting one practice at a time