SPALTEN

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 39: Line 39:
 
==How to use SPALTEN==
 
==How to use SPALTEN==
  
 +
===Situation Analysis===
 +
 +
===Problem Containment===
 +
 +
===Alternative Solutions===
 +
 +
===Selection of Solutions===
 +
 +
===Consequences Analysis===
 +
 +
===Make Decision and Realization===
 +
 +
===Recapitulate and Learn===
  
  

Revision as of 11:29, 20 February 2021

Author: Felix Dressel

This page is under construction

(Abstract)

The SPALTEN problem-solving process was initially published in 2002 by Albers et al. as a method which is universally applicable to any sort of problem in product development and project management.[1] SPALTEN can be adapted in condition and complexity to any problem. Its strength is to gather and analyze the given situation as well as to create, rate and select possible solutions. The method also enables the user to divide one big problem into smaller ones. Consequently, it is easier to manage the problem and work out a solution.[2] It is confirmed, that due to its flexibility, engineers are able to apply SPALTEN throughout the entire product development process as well as across multiple other activities in project management.[3]


The term SPALTEN was designed as an acronym representing its different steps (in German). The method is structured by seven working steps, each of which can be carried out with different subordinate methods.[4] The seven steps are:

(S) Situation Analysis

(P) Problem Containment

(A) Alternative Solutions

(L) Selection of Solutions

(T) Consequences Analysis

(E) Make Decision and Realization

(N) Recapitulate and Learn


The following chapters of this article will elaborate how the SPALTEN problem-solving process is implemented, how the different steps are carried out in practice (course of action, examples, etc.) and what its limitations are. Additionally, other influencing factors like the problem-solving team, a regular check of information and a continuous idea storage will be introduced together with their relevance and application in this method. Depending on the length of the topics mentioned before, also a gamified approach (The SPALTEN Expedition) can be presented.


Contents

Overview

Problem Solving in Project Management

The SPALTEN Problem-Solving Methodology

How to use SPALTEN

Situation Analysis

Problem Containment

Alternative Solutions

Selection of Solutions

Consequences Analysis

Make Decision and Realization

Recapitulate and Learn

The SPALTEN Methodology in Project Management

Annotated bibliography

References

  1. Albers, A., M. Saak, N. Burkhardt, and D. Schweinberger (Eds.). 2002. Gezielte Problemlösung bei der Produktentwicklung mit Hilfe der SPALTEN-Methode
  2. Albers, Albert, Nicolas Reiß, Nicola Bursac, and Jan Breitschuh (Eds.). 2016. 15 Years of SPALTEN Problem Solving Methodology in Product Development
  3. Saak, Marcus. 2006. Development of a concept and of a prototype for a computer-aided tool for the efficient employment of the problem solving methodology "SPALTEN"
  4. Albers, Albert, Nicolas Reiß, Nicola Bursac, and Jan Breitschuh (Eds.). 2016. 15 Years of SPALTEN Problem Solving Methodology in Product Development
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox