= 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)
== Task Result ==
Google docs and wiki pages.
== Implementation idea ==
Creating the necessary google docs and wiki pages.
== Related ==
== How to demo ==
Easy tracking

= Design =
Our [http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en# 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 [wiki:CODE_SMELLS]. This code doesn't follow the rules defined in [wiki: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.
Our Internal Backlog will contain some wiki pages:
 * 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 Important Docs -> [wiki:ImportantDocs][[BR]] (for now, this will be subject of further discussions about our wiki structure)
= Implementation =
 
= Testing =

= Log =
[[Include(wiki:INTERNAL_BACKLOG_STRUCTURE_R0_LOG)]]