Information Technology Reference
In-Depth Information
4.4.1 Budget Planning
Without budget (in sight) no project can start. The highest level relevant to
controlling is the overall budget with just one figure behind it and which may not
be exceeded at the end of the project. But in most cases this budget is broken down
into an investment (hardware) part and into a personnel cost plan. The personnel
cost plan is spread over the time line of the project and details requested and granted
project days per unit time (in most cases per month) per project resource. For each
day
s contingency corresponding daily rates in money are allocated. In this way
bottlenecks and—from feedback via time sheets—project days not used up can be
tracked. A regular re-planning during project progress is usually required.
'
4.5 Templates
The following templates are useful: Kick-off Agenda (Fig.
4.9
), Test Schedule
(Fig.
4.10
), Patch Cycle (Fig.
4.11
) and Status Report (Fig.
4.12
).
Agenda Acceptance Tests Kick-off
Introduction
Presentation of Schedule
Explanation of Test Process
Assigning Tester to Test Cases
Identification of Test Data
Technical Pre-conditions
Review Process
Patch Cycle
Access Rights
Fig. 4.9 Kick-off agenda
Step No.
Date
Time
Batch Description
Result
Evaluation
Fig. 4.10 Test schedule
