7 Components: the Function Pages - Developers

Ultimately, with the work packages, they then have small individual
steps to be executed for the entire conference.
To make their work easier, they first designed and copied simple
forms, one for each work package. These forms contain
� an exact description of the task,
� what results are required from other tasks in order to perform
the respective task (inputs),
� products and results that are produced with this subtask (outputs),
� roles and responsibilities for the package,
� the timeframe of the individual task and
� the required resources.
Often, the direct predecessors and successors of the respective task
are noted. The paper forms are ideal for sorting on a wall and subsequently
developing the procedure, deadlines and financial plans.
A great deal of information can be filtered from these forms:
overall cost, material requirements, time schedules, etc. Now TWiki
comes into play again. The hunters and gatherers first transfer the
work packages to a to-do list that can be viewed by everyone involved
in the organization. The groups involved can note the status
of their respective subtasks there. This results in an updated report
on the status of the project.
The groups must clarify how detailed the list is to be. A graduated
list works well. Numbering can help in order to define precisely
which work package is being addressed in discussions. It is possible,
for example, that the publicity group and the content group both
have a work package called “Send emails.”
Note: These numbers must be assigned in a fixed manner and may
thus not be generated with the numbered list function.
The best thing to do is create a separate wiki page on which the project
numbers can be clearly noted. It might look like this:
19.1 Preparing Work Packages
Forms
To-do list
Project
number list
�
�
�
281