Changes between Version 3 and Version 4 of INTERNAL_BACKLOG_MAINTENANCE_R3

Timestamp:

01/19/09 12:13:39 (16 years ago)

Author:

deyan

Comment:

--

INTERNAL_BACKLOG_MAINTENANCE_R3

@@ -5 +5 @@
 == Overview ==
 Maintaining the backlog includes keeping the backlog in up-to-date condition, finding solutions, adding impediments and open questions on weekly meetings.
-Task requirements
+== Task requirements ==
  * Collect impediments of the previous iteration log and fill them in the Impediments section of the Internal backlog
  * Each week
@@ -16 +16 @@
  * Fill in the improvements sheet with the How to improve suggestions from the Sprint closing.
  * Update dates of last change of important documents.
-== Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
-
 == Task result ==
-^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^
-
+Maintained backlog.
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
+All of the platform standards will be updated during this iteration.
 
 == Related ==
-^(Here you can add related tasks that could be useful or helpful.)^
-
+[wiki:INTERNAL_BACKLOG_MAINTENANCE_R2] [[BR]]
+[wiki:INTERNAL_BACKLOG_MAINTENANCE_R1] [[BR]]
+[wiki:INTERNAL_BACKLOG_MAINTENANCE_R0] [[BR]]
 == How to demo ==
-^(In this section you must add instructions for the demo of the task.)^
+Show the backlog and explain what is done.
 
 = Design =