| Version 4 (modified by deyan, 16 years ago) (diff) |
|---|
Analysis
Overview
Make read documents. Make structure for some of the things. Think about open questions table.
Task requirements
The Internal backlog is located here: http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en
- Impediments sheet:
If there are solutions for unresolved tasks, mark them as resolved and insert hyperlinks to corresponding tasks (or task results) from the wiki.
- Smells sheet:
Review smells. Assign team members to fix open smells. (you can use dev mail list, or ticket system)
- Documents sheet:
Create a column for each team member. This column should contain last read date for this member.
- Daily Availability sheet:
Each member should have two columns. The first should contain amount of working hours for this date, the second should contain free text. Remind the members to fill in regularly their availability. (you can use mail list)
- Open Questions sheet:
Task result
(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))
Implementation idea
(It is advisable to include some rough implementations ideas.)
Related
http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en
INTERNAL_BACKLOG_MAINTENANCE_R1_LOG
INTERNAL_BACKLOG_STRUCTURE_R0 effort=2, ITERATION_01
INTERNAL_BACKLOG_STRUCTURE_R1? effort=2, ITERATION_03
INTERNAL_BACKLOG_STRUCTURE_R2? effort=2, ITERATION_04
How to demo
Show http://spreadsheets.google.com/ccc?key=p-0Oq38E1ayuX-E_kPfPxbg&hl=en and describe changes made
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository)
Testing
Comments
Log
