Differences between revisions 5 and 6
Revision 5 as of 2009-06-23 10:34:14
Size: 3340
Editor: abr
Comment:
Revision 6 as of 2009-08-21 10:42:44
Size: 3440
Editor: abr
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 Time used:: 1md  Time used:: 6md
Line 22: Line 22:
 Status:: In progress  Status:: Finished
Line 42: Line 42:
 * It still uses the DOMS namespaces.
 * Testing: Not complete
 * Testing: Preliminary done
Line 46: Line 45:
 * Installation guide: Not complete
 * Pid generator: Not complete
 * Installation guide: First version complete
 * Pid generator: First version complete
Line 51: Line 50:
With the above progress, the first version of the service is defined to be ready for release and this task is finished

Action Finish ECM Code

Assigned
ABR(7md),KFC(4md)

Prev assigned

Tasks adressed
["Tasks/5/1"]

Time estimated
12md

Time used
6md

Priority
5

Status
Finished

Iteration
21

Notes

Problem

The ECM package have been extracted from the DOMS project. It now lives on ecm.sourceforge.net

Since it have been publically released, it should now be nearing production quality.

Progress

  • The system design: complete.
  • View: Lacks defenses
  • Validator: Lacks defenses
  • Templates: Lacks defenses
  • Testing: Preliminary done
  • Design docs: Lacks the design of the webservice docs
  • User manual: Complete
  • Installation guide: First version complete
  • Pid generator: First version complete

Conclusion

With the above progress, the first version of the service is defined to be ready for release and this task is finished

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.

Actions/Finish ECM Code (last edited 2010-03-17 13:09:08 by localhost)