[[BackLinksMenu]]

[[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 =
== 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
 * 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.
 * 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.))^

== Implementation idea ==
^(It is advisable to include some rough implementations ideas.)^

== Related ==
^(Here you can add related tasks that could be useful or helpful.)^

== How to demo ==
^(In this section you must add instructions for the demo of the task.)^

= Design =

= Implementation =
^(Implementation results should be described and linked here (from the wiki or the repository))^

= Testing =

= Comments =
^(Write comments for this or later revisions here.)