wiki:PROCESS/InternalBacklog
Last modified 16 years ago Last modified on 03/21/09 13:52:38

Overview

Internal Backlog Google Doc helps organizing and keeping track of the work.

Impediments

Name - contains short descriptive name of the impediment written down with small letters and "-" instead of spaces.
Description - contains more detailed (most of the) information about the impediment. It may contain several sentences.
Date - this field must contain the date that the impediment is discovered. You must submit the impediments at the moment you saw them, so ideally this field includes the date when the impediment was submitted.
Reporter - contains the dev id of the one that has discovered and reported the impediment.
Impact - contains information about how severe the impediment is. There are three possibilities: low, medium and high.
Status - there are two possibilities: resolved - if the problem is solved, and unresolved - if the problem is still on line.
Assigned to - this field is optional and includes the dev id to the team member that is assigned to resolve the impediment.
Comments - this column includes comments about the impediment. All team members can write a comment, it is recommended if you have opinion on the topic to leave a comment.

Smells

Name - contains short descriptive name of the "smell" written down with small letters and "-" instead of spaces.
Description - contains more detailed (most of the) information about the "smell". It may contain several sentences.
Location - contains information about where the "smell" is located.
Date - this field must contain the date that the "smell" is discovered. You must submit the "smells" at the moment you saw them, so ideally this field includes the date when the "smell" was submitted.
Reporter - contains the dev id of the one that has discovered and reported the "smell".
Status - there are two possibilities: done - if the problem is solved, and open - if the problem is still not solved.
Assigned to - this field is optional and includes the dev id to the team member that is assigned to resolve the "smell".
Comments - this column includes comments about the "smell". All team members can write a comment, it is recommended if you have opinion on the topic to leave a comment.

Documents

Categories - Documents are separated in three different categories: SETUP, PROCESS, PRODUCT. Each include documents that are useful and must be read.
Document - this column contains the name of the document.
Link - provides link to the document.
Last Update - contains the date on which the document was last modified.
Description - contains short description about document purpose and contents.
dev id - contains the date that each team member has read the document for last time.

Daily Availability

Date - this column contains the corresponding date.
dev id - Desc - contains the description of the period for which the team member will be available. For example between 12h and 17h.
dev id - Time - contains the amount of hours that the team member will be available this day. For example 5h.

Open Questions

Question - contains the open question.
Date - this field must contain the date that the question appeared. You must submit the open questions at the moment you saw them, so ideally this field includes the date when the open question was submitted.
Question from - contains the dev id of the team member that submitted the question.
Impact - contains information about how important the question is. There are three possibilities: low, medium and high.
Status - there are two possibilities: done - if the question is answered, and open - if the question is still not answered.
Solution - contains detailed answer to the question.