Changes between Version 1 and Version 2 of INTERNAL_BACKLOG_MAINTENANCE_R3

Timestamp:

01/19/09 10:16:47 (16 years ago)

Author:

deyan

Comment:

--

INTERNAL_BACKLOG_MAINTENANCE_R3

@@ -2 +2 @@
 
 [[TicketQuery(summary=INTERNAL_BACKLOG_MAINTENANCE_R3, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]
-
-
-
 = Analysis =
-^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^
-
 == Overview ==
-^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
-
+Maintaining the backlog includes keeping the backlog in up-to-date condition, finding solutions, adding impediments and open questions on weekly meetings.
+Task requirements
+ * Collect impediments of the previous iteration log and fill them in the Impediments section of the Internal backlog
+ * 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 you have done. 
+ * Fill in the improvements sheet with the How to improve suggestions from the Sprint closing.
 == Task requirements ==
 ^(Necessary requirements that the task must fulfill.)^