Differences between revisions 2 and 3
Revision 2 as of 2008-08-12 07:14:32
Size: 1990
Editor: kfc
Comment:
Revision 3 as of 2008-08-18 07:00:35
Size: 2852
Editor: kfc
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Line 4: Line 5:

Line 5: Line 8:
Line 7: Line 11:

Line 8: Line 14:
Line 10: Line 17:

Line 11: Line 20:
Line 13: Line 23:

Line 14: Line 26:
Line 16: Line 29:

Line 17: Line 32:
Line 19: Line 35:

Line 20: Line 38:
Line 22: Line 41:

Line 23: Line 44:
Line 25: Line 47:

Line 26: Line 50:
Line 28: Line 53:

Line 29: Line 56:
Line 32: Line 60:


Line 33: Line 64:
Line 34: Line 66:





Line 41: Line 79:


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.
Line 43: Line 92:

Line 44: Line 95:
Line 45: Line 97:
Line 46: Line 99:
Line 47: Line 101:
 * When finishing the action, change the status to "Finished" and update the "time used" field on the action page.

Action TITLE

Assigned
TSH+JRG

Prev assigned

Tasks adressed
["TaskX/1"]

Time estimated
not done

Time used
0md

Priority
?

Status
Not started

Iteration
0

Notes

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.

ActionTemplate (last edited 2010-03-17 13:13:03 by localhost)