|
Size: 2976
Comment:
|
← Revision 6 as of 2010-03-17 13:08:52 ⇥
Size: 3440
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Line 5: | Line 4: |
| Line 8: | Line 5: |
Assigned:: KFC |
Assigned:: KFC+ABR |
| Line 14: | Line 8: |
| Line 17: | Line 10: |
| Line 20: | Line 11: |
Tasks adressed:: ["TaskX/1"] |
Tasks adressed:: [[TaskE.1]] |
| Line 26: | Line 14: |
Time estimated:: not done |
Time estimated:: 2md |
| Line 32: | Line 17: |
Time used:: 0md |
Time used:: ½md (KFC) |
| Line 38: | Line 20: |
| Line 41: | Line 22: |
| Line 44: | Line 23: |
Status:: Not described |
Status:: In progress |
| Line 50: | Line 26: |
| Line 53: | Line 28: |
| Line 55: | Line 29: |
| Line 58: | Line 31: |
| Line 63: | Line 32: |
| Line 66: | Line 34: |
| We need to have a well-defined API about how the DOMS GUI may pull data from other environments, and push data to other environments. | |
| Line 67: | Line 36: |
| Since the immediate use of this component is to make it easy to pull data into/out of the GUI, it will probably be best if Mjølner can come with the first suggestion. | |
| Line 68: | Line 38: |
| Estimated time: * Meeting with Mjølner: ½md per participant * Documentation of conclusion: ½md * Reference implmentation: 1md |
|
| Line 69: | Line 43: |
| Assuming only one DOMS participant in meeting, this gives 2 md. | |
| Line 70: | Line 45: |
| Progress history: see [[TaskE.1]] | |
| Line 77: | Line 48: |
| Line 92: | Line 61: |
Action Import/Export APIs
- Assigned
- KFC+ABR
- Prev assigned
- Tasks adressed
- Time estimated
- 2md
- Time used
- ½md (KFC)
- Priority
- 2
- Status
- In progress
- Iteration
- 13
- Notes
We need to have a well-defined API about how the DOMS GUI may pull data from other environments, and push data to other environments.
Since the immediate use of this component is to make it easy to pull data into/out of the GUI, it will probably be best if Mjølner can come with the first suggestion.
Estimated time:
- Meeting with Mjølner: ½md per participant
- Documentation of conclusion: ½md
- Reference implmentation: 1md
Assuming only one DOMS participant in meeting, this gives 2 md.
Progress history: see TaskE.1
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.