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 and wiki pages.

Implementation idea

Creating the necessary google docs and wiki pages.

Related

How to demo

Easy tracking

Design

• We can put examples of bad code samples in CODE_SMELLS
  
• We can define code smells and define code requirements in CODE_TASKS_REQUIREMENTS
  
• Google doc for tracking impediments. -> ​Veda-Internal-Backlog
  
• Google doc for tracking availability. -> ​Sprint Availability
  
• Wiki page where to store sprint logs -> SPRINT_LOGS?
  
• Wiki page for asking questions -> OPEN_QUESTIONS?
  
• Wiki page for storing useful links -> USEFUL_LINKS
  
• Wiki page for linking Read Docs -> READ_DOCS?
  

Implementation

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 :