= Analysis =
== Overview ==
Internal Backlog helps organizing and keeping track of the work.
== Task requirements ==
Define how it will be tracked.[[BR]]
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)
== Requirements to the task result ==
Google docs and wiki pages.
== Implementation idea ==
Creating the necessary google docs and wiki pages.
== Related ==
== How to demo ==
Easy tracking
= Design =
 * Define where examples of code smells and code requirements to be stored.
 * Define where the developers can track their impediments.
 * Define where team can write its availability.
 * Define where sprint logs can be tracked.
 * Define where team can ask questions and make proposals. For example "bugzilla or mantis?"
 * Define where to link Read Docs (documents that developer must be familiar with)
= Implementation =
 * We can put examples of bad code samples in [wiki:CODE_SMELLS][[BR]]
 * We can define code smells and define code requirements in [wiki:CODE_TASKS_REQUIREMENTS][[BR]]
 * Google doc for tracking impediments. -> [http://spreadsheets.google.com/ccc?key=pXMDMxqLG-VHe7L4m_xcbbA&hl=en] Veda-Internal-Backlog [[BR]]
 * Google doc for tracking availability. -> Sprint Availability [[BR]]
 * Wiki page where to store sprint logs -> [wiki:SPRINT_LOGS][[BR]]
 * Wiki page for asking questions -> [wiki:OPEN_QUESTIONS][[BR]] 
 * Wiki page for storing useful links -> [wiki:USEFUL_LINKS][[BR]]
 * Wiki page for linking Read Docs -> [wiki:READ_DOCS][[BR]]
= Testing =