wiki:INTERNAL_BACKLOG_MAINTENANCE_R3
Last modified 14 years ago Last modified on 01/20/09 11:47:13

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

Error: Macro 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|) 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

Note that some of the requirements should be implemented regularly (each week).

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

Maintained backlog.

Implementation idea

All of the platform standards will be updated during this iteration.

INTERNAL_BACKLOG_MAINTENANCE_R2
INTERNAL_BACKLOG_MAINTENANCE_R1
INTERNAL_BACKLOG_MAINTENANCE_R0

How to demo

Show the backlog and explain what is done.

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