|
Size: 3098
Comment:
|
Size: 3386
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 27: | Line 27: |
| Time estimated:: 2md | Time estimated:: 1md |
| Line 58: | Line 58: |
| Line 59: | Line 60: |
| TaskA.2.3AnalysisDocument contains a long list of TDR requirements that influence our data modelling language. These should be reviewed, to see if our current design accomodates all the requirements. |
|
| Line 60: | Line 64: |
## 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. ["TaskA.2.3AnalysisDocument"] contains a long list of TDR requirements that influence our data modelling language. These should be reviewed, to see if our current design accomodates all the requirements. |
We need to go through the list and look up the full descriptions of the requirements, and we need to go through the current data model description, and we need to match the two. There should be two people assigned, such that we can discuss any issues. The time estimated is more a hope than an estimate, but say two people spend each an hour reading up on the material, they spend one hour on a meeting and agree all requirements are met, and one of them spend an hour writing the summary... |
Action review TDR requirements for Data Model
- Assigned
- BAM + ABR
- Prev assigned
- Tasks adressed
- ["TaskA.2.3"]
- Time estimated
- 1md
- Time used
- 0md
- Priority
- 5
- Status
- Description needs review
- Iteration
- 11
- Notes
TaskA.2.3AnalysisDocument contains a long list of TDR requirements that influence our data modelling language. These should be reviewed, to see if our current design accomodates all the requirements.
We need to go through the list and look up the full descriptions of the requirements, and we need to go through the current data model description, and we need to match the two. There should be two people assigned, such that we can discuss any issues. The time estimated is more a hope than an estimate, but say two people spend each an hour reading up on the material, they spend one hour on a meeting and agree all requirements are met, and one of them spend an hour writing the summary...
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.