Changes between Version 3 and Version 4 of INTERNAL_BACKLOG_MAINTENANCE_R2

Timestamp:

01/05/09 15:21:53 (16 years ago)

Author:

deyan

Comment:

--

INTERNAL_BACKLOG_MAINTENANCE_R2

@@ -7 +7 @@
 Maintaining the backlog includes keeping the backlog in up-to-date condition, finding solutions, adding impediments and open questions on weekly meetings.
 == Task requirements ==
-* Each week 
- * Use weekly meeting logs to collect Impediments and Open Questions. 
- * Discuss how to resolve current unresolved impediments
- * Track the Daily availability and send reminder mails if needed
- * Remove colors from daily availability and replace them with symbols (This should be done for the cells that contain only color)
- * In implementation section fill in what have you done.
-
+ * Each week 
+  * Use weekly meeting logs to collect Impediments and Open Questions. 
+  * Mark resolved impediments
+  * Discuss how to resolve current unresolved impediments
+  * Track the Daily availability and send reminder mails if needed
+  * Upload a picture of the wall with weekly plan
+  * In implementation section fill in what have you done.
 == 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.))^
-
+Updated Internal backlog on weekly meetings.
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
-
+Send reminders before weekly meetings with requirements for the internal backlog.
 == Related ==
-^(Here you can add related tasks that could be useful or helpful.)^
-
+[wiki:INTERNAL_BACKLOG_STRUCTURE_R1]
 == How to demo ==
-^(In this section you must add instructions for the demo of the task.)^
+Show implementation section and explain what is done.
 
 = Design =