## Action
= Describe The DOMS Iteration Work Flow =

## 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.

Describe the work flow of a DOMS iteration and create a check-list of actions that should be performed when starting and ending an iteration. It may be useful to create a separate check-list for starting and ending the iteration.

The work flow description and the check-list(s) should be put into a separate page, and the [[Iterations]] page should have a link added to that page.

The description of the iteration work flow and the check-list(s) should comprise topics like (please add them I forgot):

 * Registration of actual time usage for each action at the end of an iteration and checking whether the estimates should be revised.
 * Ensure that all communication has been performed during the iteration according to the [[CommunicationPlan|communication plan]].
 * Make sure that all the communication that has taken place during an iteration has been properly logged on the relevant stakeholder pages. This will include creation of the log if it does not exists.
 * Revising [[CommunicationPlan|communication plan]] and making sure it is up to date.
 * Ensure that the [[StakeholderAnalysis|stakeholder analysis]] is up to date. That is, add new stakeholders, if any.
 * Check up on which actions that have been completed during an iteration and take appropriate action on those that have not. E.g. move them on to the next iteration.
 * The [[RiskAnalysis|risk analysis]] must also be revised at the end of an iteration to ensure that the project is aware of changes in the priority or consequence of known risks and gets new risks registered.



## Targeted WBS Tasks and Assigned Developers can be found on the iteration page for this action.