All Groups


Links a contributor to another object to give credit for having contributed, and defines in what manner. We don’t measure how much, except to distinguish between Author (lots) and Contributor or Supplement (less) and Correction (little).


Person who has contributed material to Core Practice, including the user community providing feedback


Categories relate to the CMM Common Feature system of classifying Practices. They are included as another metric for assessing maturity, and assessing balance of Practices (does a Process have some of each category). They may not be retained in the model if they are judged not to be useful.


TBD. Must be able to self-assess without consultants. Will user managers be able to readily self assess using just the Practices? (assuming we stay with the Process-level, Practice-based assessments). Or would it be better to have a set of questions that derive the assessment?

RADIX Object Model

The RADIX model is object-oriented. It allows inheritance and poly-morphism.

The interim OID nomenclature needs review by someone with OID expertise. We also need to allocate the high-level qualifier for all OIDs. Address of corepractice.org URL or get an OID allocated by say IANA?

Alternative proposal: switch to using Drupal (our CMS) node numbers as OIDs. 

  • they appear in the URL so everyone can see them (unless we implement Drupal pathalias)
  • they don't change (unless migrate a subset of data to a new system)

Interim nomenclature is:

RADIX Frameworkâ„¢

RADIX Framework™ is the name for the underlying system for describing all Core Practices. Core Practices are organised into sets, or Groups, according to their target user group. For example, the first Group of Core Practices is Core Practice for Small Business. We hope other user groups will contribute their own Group of Core Practices.
The definition of any Group of Core Practices should be based on the RADIX Framework.
RADIX Framework™ provides:
• This specification document
• A maturity model
• A template for process models
• A spreadsheet format for defining a Group’s processes and practices

The BSF Rules

1.      No Separation. “IT is the business
When an organisation is big enough to have an IT department then it makes sense for that department to have its own processes.   It is also possible (likely?) that that group will split away from the business to some degree. In SMEs this is less of a phenomenon. Process is process with no distinction between a business process and an IT process (there aren’t both an HR payroll process and a business payroll process). E.g.

Guiding Principles

Continuous Incremental Improvement
Keep costs low

Easy to understand

Pragmatic, practical.
Conservative: Generally accepted (“best”) practice.

Syndicate content