|
Size: 2989
Comment:
|
← Revision 10 as of 2010-03-17 13:09:34 ⇥
Size: 3359
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = Action Export webservice continued = ## The persons assigned to the action Assigned:: BAM+? ## The persons that previously worked on this action Prev assigned:: ## The tasks from the WBS that are adressed by this action Tasks adressed:: [[TaskX/1]] ## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated Time estimated:: 1/4 md ## The time used for this action so far. Same format as Time estimated Time used:: 0md ## The priority of this action. 1-9 Priority:: 5 ## The status of this action, legal values are 'Not described', 'Not started', 'In progress' and 'Finished' Status:: Finished. ## The iteration that this actions belongs to Iteration:: 16 ## Notes about this action, that should be viewable on other pages Notes:: only mock-up ## Detailed description of wanted output from the work to be carried out. This action is a follow-up to check that we have a working export mock-up. The mock-up is a quadriga export from objects with quadriga file content model in the spolebaand example. A quick test tells me that we have such a mock-up functionality. There is however the question of export return value. Should the export functionality write and return the file (and throw an exception if the file could not be written) or should some status message be returned? |
|
| Line 3: | Line 24: |
| = Action Export webservice continued = ## The persons assigned to the action Assigned:: KFC+BAM ## The persons that previously worked on this action Prev assigned:: ## The tasks from the WBS that are adressed by this action Tasks adressed:: ["TaskX/1"] ## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated Time estimated:: not done ## The time used for this action so far. Same format as Time estimated Time used:: 0md ## The priority of this action. 1-9 Priority:: 5 ## The status of this action, legal values are 'Not described', 'Not started', 'In progress' and 'Finished' Status:: Not described ## The iteration that this actions belongs to Iteration:: 16 ## Notes about this action, that should be viewable on other pages Notes:: ## Detailed description of wanted output from the work to be carried out. ## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written. |
It has been agreed that the service returns the 'export-file', and this action can be closed. -- [[bam]] <<DateTime(2008-12-11T08:49:12Z)>> |
| Line 77: | Line 27: |
| The Life Cycle of an Action: | |
| Line 78: | Line 29: |
The Life Cycle of an Action: |
|
| Line 88: | Line 36: |
| Line 91: | Line 38: |
| Line 94: | Line 39: |
| Line 96: | Line 40: |
| Line 98: | Line 41: |
Action Export webservice continued
- Assigned
- BAM+?
- Prev assigned
- Tasks adressed
- Time estimated
- 1/4 md
- Time used
- 0md
- Priority
- 5
- Status
- Finished.
- Iteration
- 16
- Notes
- only mock-up
This action is a follow-up to check that we have a working export mock-up. The mock-up is a quadriga export from objects with quadriga file content model in the spolebaand example. A quick test tells me that we have such a mock-up functionality. There is however the question of export return value. Should the export functionality write and return the file (and throw an exception if the file could not be written) or should some status message be returned?
It has been agreed that the service returns the 'export-file', and this action can be closed. -- bam 2008-12-11 08:49:12
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.