Information Technology Reference
In-Depth Information
detailed
measures
detailed
measures
leftover
tasks
30%
15%
8%
Fig. 6.3
Data clean-up
Depending on the detailed analyses manual corrections or error amendments of
the bootstrap code with successive repetitions of the data bootstrap should take place.
In many cases manual maintenance of the uploaded data is required when for
example additional data items have been included which were not present in the
old system.
For migration similar criteria as for data bootstrapping and the validation process
have to be applied. Here again later data clean-up can not be excluded. It may even
be in the nature of the task at hand that major data clean-up has to be carried out in
any case if the coded migration algorithm is not capable to produce a clean data
mapping in the first place. In such cases after migration (and this is also the case for
data bootstraps as well) a sub-project “Data Clean-up” has to be set up, which takes
care of the erroneous data records in the new system according to defined quality
criteria. Unfortunately this may have to happen during regularly running produc-
tion. Clean-up progress is depicted in Fig.
6.3
.
6.4 Task Tracking
The simplest way is to record all necessary tasks in a task list (EXCEL
) (template
©
see Sect.
6.5
).
To follow up on the status three categories are sufficient:
• Open,
• Work in progress,
• Closed.
In addition finished tasks can be marked by crossing them out to have a better
overview.
Another essential tool is budget tracking. Its format has been introduced already
Special emphasis has to be placed on customising a suitable test system. This
will be dealt with in Chap.
7
.
