[[BackLinksMenu]]

[[TicketQuery(summary=SCHEDULE_MAINTENANCE_R2, 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 ==
As schedule maintenance is a routine task, the most of the requirements from previous iterations are applicable.
== Task requirements ==
 * Create page for this iteration (Already created, but includes planned tasks only [wiki:ITERATION_03]
 * Add the tasks for this iteration
  * unfinished tasks from the previous sprint (if any)
  * unplanned tasks - Unplanned tasks should be discussed with the team in order to decide which tasks that are planned for other iterations need effort in this iteration.
  * remote tasks - Remote tasks are decided in sprint opening.
Further information on what tasks should be added will be available in [source:/manage/reports/m03/] in sprint opening log. 
 * For each task you should create a ticket with link to a wiki page for this revision in decription field. Other required fields are:
  * Priority - [1 .. 5]
  * Importance - [10 .. 99]
  * Effort - [0.5+]
  * Component
== Task result ==
The result should be iteration page containing all needed tickets.

== Implementation idea ==
Use this page [wiki:SCHEDULE_WBS_TIME_ALLOC], discuss which tasks need attention and add them as unplanned tasks. (Do this at the sprint opening). Review and include tasks from the log.

== Related ==
[wiki:SCHEDULE_WBS_TIME_ALLOC]

== 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.)