## Please put instances of this page in the Actions/ subfolder
= Action IT Maintenance Department Meeting =
## The persons assigned to the action
 Assigned:: KFC: 3 JRG: 1½

## The persons that previously worked on this action
 Prev assigned::

## The tasks from the WBS that are adressed by this action
 Tasks adressed:: [[Tasks/2/1/1]], [[Tasks/2/1/2]], [[Tasks/2/1/3]], [[Tasks/2/1/4]], [[Tasks/2/1/6]], [[Tasks/2/1/8]]

## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated
 Time estimated:: 4½md

## Themd time used for this action so far. Same format as Time estimated
 Time used:: KFC: 1md, ½md(JRG)

## Thriority of this action. 1-9. 1 is highest.
 Priority:: ?

## The status of this action, legal values are 'Not described', 'Not started', 'In progress' and 'Finished'
 Status:: Finished

## The iteration that this actions belongs to
 Iteration:: 22

## Notes about this action, that should be viewable on other page22
 Notes:: 


## Detailed description of wanted output from the work to be carried out.
## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written.
We need to meet with the IT maintenance department, and get an agreement on:
 * Bitstorage - Finalize agreement on SSH scripts
 * Backup - What to back up? Obviously object files from Fedora, and probably configuration. Not necessary with installed system and databases/indexes (should be rebuilt as part of disaster recovery scheme)
 * Port allocation (Is 7900-7999 okay?)
 * Installation and upgrade procedures (What should we deliver? System consists of tomcat with webservices. GUI requires special tomcat, Fedora requires environment variable setting set before starting tomcat. We can deliver scripts to update configuration files in all webservices from one file, and also to deploy)

See [[2009-10-07 IT Maintenance Meeting]]

== Checklist For Working On An Action ==

The Life Cycle of an Action:
 * ''Assign people for action definition'': Done at start of iteration status meeting. Fill out '''Assigned'''
 * ''Define the action'': Describe information about what is to be done and how. Fill out '''Tasks Addressed''' and '''Time Estimated'''.
 * ''Review the definition'': Get another project group member to review the action definition, and update it.
 * ''Assign people for action implementation'': Done by project manager, usually the same persons who wrote the definition. Fill out '''Assigned''' and '''Prev assigned''' if new persons are assigned.
 * ''Implement the action'': See details below
 * ''Review the action'': Get another project group member to review what is implemented (code and documentation), and update it.
 * ''Finish the action'': Change the status to "Finished" and update the "time used" field on the action page.

Please make sure that you address the below issues, when working on an action:
 * Update the state of the action to "In Progress" when you start working on it.
 * Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.
 * Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. '''Hint:''' Continually updating the "Time used" field will make it easier for you.
 * Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.