wiki:INTERNAL_BACKLOG_STRUCTURE_R2

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

--

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

Error: Macro TicketQuery(summary=INTERNAL_BACKLOG_STRUCTURE_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

Internal backlog structure improves backlog usability

Task requirements

  • Add comment section for the open questions sheet
  • (Optional) Add an Improvements sheet which contains improvement suggestions. Required fields:
    • Name
    • Description
    • Date
    • Reporter
    • Status (applied, not applied, won't be applied)
    • Comments
  • Arrange people by teams in the internal backlog availability sheet
  • Split the Availability sheet into two sheets - one for the following month and one old.
    • This should be moved regularly - the month sheet into the other one
    • Mark non-working days in gray
  • Add section "Recent impediments" and split impediments too.
  • Mark resolved impediments somehow

Task result

Improved http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en

Implementation idea

Implement when noone is accessing the backlog

http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en

How to demo

Explain in the dev chat what is done

Design

  • Teams
    • Ti
      • pap
      • meddle
      • dido
      • deyan
    • T1
      • nenko
      • peko
      • vlado
      • didi
      • george
    • T2
      • pav
      • gogov
      • jani
      • sveto
      • danvisel
      • stefan
    • T3
      • boyan
      • kyli
      • tsachev
      • ivo
    • T4
      • tanya
      • mitex
      • mira
      • deni
      • todor
  • Availability - optionally fields will give automatically information about team availability

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