wiki:INTERNAL_BACKLOG_STRUCTURE_R0

Version 21 (modified by todor, 17 years ago) (diff)

--

Analysis

Overview

Internal Backlog helps organizing and keeping track of the work.

Task requirements

Define how it will be tracked.
The backlog must be able to contain

  • Code Smells
  • Work Impediments
  • Availability
  • Sprint Logs
  • Open Questions
  • Read Docs (documents that developer must be familiar with)

Task Result

Google docs.

Implementation idea

Creating the necessary google docs.

How to demo

Access the Internal Backlog in Google Docs. Show different sheets of the document. Explain the names of the columns.

Design

Our ​Internal Backlog will be a google spreadsheet with different sheets for:

  • Impediments - Here we must write down the obstructions during the iterations so we can learn from our mistakes.
  • Code Smells - Here we must put examples of bad code samples like CODE_SMELLS. This code doesn't follow the rules defined in CODE_TASKS_REQUIREMENTS
  • Documents - Here we must keep a list with our important documents and where do we store them.
  • We will keep track of the resource availability through two sheets called daily and global availability.

There is some helpful information and documents in ImportantDocs
(for now, this will be subject of further discussions about our wiki structure).

Implementation

The explanation of the different sheets is in the task design.
​Internal Backlog Google Doc

Testing

Log

  • Analyzing : Tanya, toshko - 25 min + Tanya 20 min refactor
  • Designing : Tanya - 2h 10 min
  • Designing2: todor
  • Implementing : todor
    • Task review 2 points : Current task analysis, design and implementation presume that the Internal Backlog is different kinds of documents. If someone wants to see a part of it, he should look in the task's revision wiki page to determine where he should look for the information. I suggest creating a Wiki page named INTERNAL_BACKLOG? where all these links (google docs, wiki pages) should be linked with brief explanation what part of the backlog is stored there.
  • Implementing 2: todor
    • Task review 3 points : How to demo is not complete, Implementation section should contain more detailed information about implementation.
  • Implementing 3: Pac ( done 20m )
  • Testing :