|
Size: 2973
Comment: DOMS action added
|
Size: 3563
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Assigned:: ABR: 3 PKO: 1½ JRG: 1½ | ## Assigned:: ABR: 3 PKO: 1½ JRG: 1½ Assigned:: KFC: 2 |
| Line 10: | Line 11: |
| Tasks adressed:: ["Tasks/4/2"] | Tasks adressed:: [[Tasks/4/2]] ## Time remaining on this action. Use the format Xmd, to indicate the number of man-days estimated. Time remaining:: |
| Line 13: | Line 17: |
| Time estimated:: 6md | ## Time estimated:: 6md Time estimated:: 2md |
| Line 16: | Line 21: |
| Time used:: | ## Time used:: 4.5md(ABR), ½md(JRG) Time used:: 1.7md (KFC) |
| Line 19: | Line 25: |
| Priority:: ? | Priority:: 1 |
| Line 22: | Line 28: |
| Status:: Not described | Status:: In progress, waiting for JHLJ |
| Line 25: | Line 31: |
| Iteration:: 22 | Iteration:: 22, 24 |
| Line 29: | Line 35: |
Had meeting with JHLJ, agreed to the new version of the bitstorage system. Reviewed the lowlevel code, and made followup revisions. Added a file locking facility, that might become redundant. == TODO == Move the bitstorage scripts to the sourceforge package, jhjl has approved this. == Design docs == LowLevelBitStorageDesignDoc |
Action Low level bit storage
- Assigned
- KFC: 2
- Prev assigned
- Tasks adressed
- Time remaining
- Time estimated
- 2md
- Time used
- 1.7md (KFC)
- Priority
- 1
- Status
- In progress, waiting for JHLJ
- Iteration
- 22, 24
- Notes
Had meeting with JHLJ, agreed to the new version of the bitstorage system.
Reviewed the lowlevel code, and made followup revisions. Added a file locking facility, that might become redundant.
TODO
Move the bitstorage scripts to the sourceforge package, jhjl has approved this.
Design docs
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.