Systematic improvement works with a few kinds of information, the entities of the aim42 domain model. The diagram shows how they relate; select an entity to jump to its definition. The introduction tells the same story in a simpler picture.
Core concepts
The terms aim42 uses throughout its practices and patterns.
- Issue
-
Any problem, error, fault, risk, suboptimal situation or their causes within the System, its Processes or the Organization related to it, for example management, operational, development, administrative or organizational activities.
- Frequency: how often the issue occurs.
- Cost: see cost of an issue.
- Issue is resolved by one or several Improvements.
- Cause
-
Root cause of an Issue, in contrast to a symptom; the fundamental reason for one or several issues.
- Risk
-
A potential problem, an Issue that has not occurred yet. Improvements can change associated risks for the better or the worse, and even create new risks.
- Probability: how likely the risk turns into a problem.
- EarlyWarning: indicator that the risk is occurring and turning into a problem.
- Risk is a kind of Issue.
- Improvement
-
Any remedy, opportunity, tactic or strategy to improve the System by resolving one or several Issues.
- Cost: see cost of an improvement.
- Improvement resolves one or several Issues, partially or completely.
- Improvement is a remedy for the System.
- Improvement modifies or creates Risks.
- Cost of an issue
-
Simply said: the degree of pain an issue causes. More formally: the cost of the issue in any unit appropriate for business, such as money or effort, related to a frequency or period of time. For example, the cost of every occurrence of the issue, or the recurring cost per week.
- Cost of an improvement
-
The cost of the improvement, remedy, tactic or strategy, in monetary units.
The system and its context
What is being improved, and the people, processes and rules around it.
- System
-
The system under improvement.
- System consists of Software, Configuration, Hardware and Documentation.
- System suffers from Issues.
- System complies with one or several Goals.
- System is managed and affected by Processes.
- Software
-
All source code that makes up the System under improvement, hopefully stored in version control.
- Configuration
-
Settings and parameters that adapt the Software to its environment.
- Hardware
-
Structure and kind of hardware required to develop, test and operate the System.
- Documentation
-
Any (hopefully written) information about the System, its goals, requirements, architecture, implementation, operation or management.
- Organization
-
The organization or entity responsible for or owning the System.
- Name
- Organization has explicit and implicit Goals.
- Organization imposes Processes and Constraints.
- Organization is a source of Issues.
- Stakeholder
-
People or roles interested or participating in the System or any of its associated Processes.
- Name, Role, Interests, Experience
- Stakeholder belong to the Organization responsible for or owning the System.
- Stakeholder know about and inform about Issues and Improvements; stakeholders often know about existing problems and opportunities for improvement.
- Process
-
Processes, conventions or activities for developing, maintaining, operating or managing the System.
- Process is a source of Issues.
- Goals
-
What the Organization or Stakeholders expect from the System; why the System exists at all.
- Constraints
-
Technical or organizational constraints restraining management, design, implementation or operation of the System.
- Constraints restrict the System, associated Processes or the Organization.