This is a project backlog for the project "One-Day Tour". Please refer to Notes.

Notes:

1. Basic concepts:
   1. A project backlog is a list of tasks which your team worked on, currently working on or is going to work on to achieve your project goal/vision.
   2. This is a dynamic document, and it is supposed to change over time. However, this is expected to be a record on what have been done, as well as planning for future works. Hence, for those which have been done, they are not expected to be changed or removed, so that other team members can reference to easily in the future.
   3. You should maintain and prioritize those tasks in the backlog regularly.
   4. You are expected to work out a way with your team members to manage your project backlog so as to effectively manage your project progress.
2. "Size" of a task
   1. Each task is supposed to be completed within one or a few days (or at most one week).
   2. If you estimated that a task has to take up at least one week to complete, please consider breaking it down into small ones
   3. If this is an on-going task, please update its status regularly in Status, and details in Additional notes.
3. ID
   1. A unique identifier of the task, in the form YYYYMMDD_X, where
      1. YYYYMMDD - date of creation of the task
      2. X - a number (starting from 0) indicating task created, for identification of task creating on the same date.
4. Status
   1. Status of a task, which can be
      1. started
      2. on-going
      3. pending
      4. done
      5. cancelled
   2. Be reminded to add date on which the status is updated
   3. This can also be a short summary (a few words or lines, but not a long paragraph) on status of your task, especially when the task is still on-going
5. Descriptions
   1. Before a task is "done", you can always revise its descriptions and its scope
   2. You may also breakdown the task into smaller ones for ease of management, or merge some previous tasks
   3. It is recommended that you keep a short description of the task as you will have many tasks during your project, and add link(s) to page(s) to further describe the scope
6. Dependency
   
   1. This is for indicating which task(s) a given task depends on. Note that those tasks listed here should be done BEFORE starting the task under consideration.
7. Handled By
   
   1. The person(s) responsible for working on this task
8. Additional notes
   1. After completing a task, you are recommended to provide information/summary on what you have done. This may include screen-capture, or captured video, references or web sites relating to this task, and source codes, to name a few examples
   2. Please add link to the page in this field entry, instead of putting all details in the table
   3. For an on-going task, this can be link to a page with "development log" with regular updates on the task