|
Size: 3201
Comment:
|
Size: 3764
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Assigned:: ABR: 3 PKO: 1 JRG: 4 |
Assigned:: JRG: 3 ABR: 2 ## Assigned:: ABR: 7 KFC: 3 PKO: 1 JRG: 4 |
| Line 8: | Line 8: |
| ## The tasks from the WBS that are adressed by this action Tasks adressed:: ["Tasks/4/3"] ["Tasks/4/4"] ## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated |
|
| Line 9: | Line 12: |
| ## The tasks from the WBS that are adressed by this action Tasks adressed:: ["Tasks/4/3"] |
## Time remaining on this action. Use the format Xmd, to indicate the number of man-days estimated. Time remaining:: 5md |
| Line 12: | Line 15: |
| ## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated Time estimated:: 8md |
## Time estimated:: 8md Time estimated:: 5md |
| Line 16: | Line 18: |
| Time used:: | Time used:: 10 md (ABR) |
| Line 20: | Line 22: |
| Line 22: | Line 23: |
| Status:: Not described |
Status:: In progress |
| Line 25: | Line 25: |
| Iteration:: 23 |
Iteration:: 23,24 |
| Line 28: | Line 27: |
| Notes:: | Notes:: |
| Line 33: | Line 30: |
| 1. Discuss design, especially with regard to error scenarios. Describe design on a wiki page. Review design. 1. Discuss which components (lo-level bitstorage, hi-level bitstorage,..) should take care of what bitstorage-functionality. Design interfaces for these components. Review the design. 1. Discuss and decide how we will test the code in this action, to handle different error scenarios. Unit tests? Stubs? Possibly insert points regarding test below in this list. 1. Implement teh stuff. 1. Review the code of this action. attachment:Bitstorage_publish.png attachment:Bitstorage_upload.png == Checklist For Working On An Action == The Life Cycle of an Action: |
|
| Line 34: | Line 40: |
| 1. Discuss design, especially with regard to error scenarios. Describe design on a wiki page. Review design. 2. Discuss which components (lo-level bitstorage, hi-level bitstorage,..) should take care of what functionality. == Checklist For Working On An Action == The Life Cycle of an Action: |
|
| Line 48: | Line 47: |
| Please make sure that you address the below issues, when working on an action: | |
| Line 49: | Line 49: |
| Please make sure that you address the below issues, when working on an action: |
Action High level bit storage
- Assigned
- JRG: 3 ABR: 2
- Prev assigned
- Tasks adressed
- ["Tasks/4/3"] ["Tasks/4/4"]
- Time remaining
- 5md
- Time estimated
- 5md
- Time used
- 10 md (ABR)
- Priority
- 1
- Status
- In progress
- Iteration
- 23,24
- Notes
- Discuss design, especially with regard to error scenarios. Describe design on a wiki page. Review design.
- Discuss which components (lo-level bitstorage, hi-level bitstorage,..) should take care of what bitstorage-functionality. Design interfaces for these components. Review the design.
- Discuss and decide how we will test the code in this action, to handle different error scenarios. Unit tests? Stubs? Possibly insert points regarding test below in this list.
- Implement teh stuff.
- Review the code of this action.
attachment:Bitstorage_publish.png attachment:Bitstorage_upload.png
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.