wiki:INTERNAL_BACKLOG_MAINTENANCE_R2

Version 3 (modified by deyan, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=INTERNAL_BACKLOG_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|) failed
current transaction is aborted, commands ignored until end of transaction block

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

  • 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.

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

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