Differences between revisions 13 and 17 (spanning 4 versions)
Revision 13 as of 2010-02-15 12:04:09
Size: 3364
Editor: kfc
Comment:
Revision 17 as of 2010-03-22 12:07:11
Size: 3347
Editor: kfc
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 Tasks adressed:: ["Tasks/4/2"]  Tasks adressed:: [[Tasks/4/2]]
Line 14: Line 14:
 Time remaining:: 2md  Time remaining:: ½md
Line 22: Line 22:
 Time Used:: 0.2md (KFC)  Time used:: 1.7md (KFC)
Line 28: Line 28:
 Status:: In progress but not Described  Status:: In progress

Action Low level bit storage

Assigned
KFC: 2

Prev assigned

Tasks adressed

Tasks/4/2

Time remaining
½md

Time estimated
2md

Time used
1.7md (KFC)

Priority
1

Status
In progress

Iteration
22, 24

Notes

TODO

Move the bitstorage scripts to the sourceforge package, jhjl has approved this.

Design docs

LowLevelBitStorageDesignDoc

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.

Actions/Low level bit storage (last edited 2010-05-11 09:10:17 by kfc)