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

ID

Category

Descriptions

Dependency

Status

Handled By

Additional notes

20220101_0Discoverbrainstorm on "food in HK"
2 Jan 2022: donewhole team(ODT) Concept Map: food in HK
20220101_1Discoveridentify constraints
3 Jan 2022: doneteam leader (M1)(ODT) Constraints: Assumptions, Limitations, ...
20220101_2Discoverbrainstorm on possible directions on contextual review
4 Jan 2022: donewhole team(ODT) Possible Directions on Contextual Review
20220104_0Discovercontextual review on "cuisine"20220101_26 Jan 2022: doneM1(ODT) Contextual Review: Cuisine
20220104_1Discovercontextual review on "hiking"20220101_26 Jan 2022: doneM2(ODT) Contextual Review: Hiking
20220104_2Discovercontextual review on "tourists"20220101_26 Jan 2022: doneM3(ODT) Contextual Review: Tourists
20220106_0Discoversummarize key findings/insights on contextual review

20220104_0

20220104_1

20220104_2

7 Jan 2022: doneteam leader (M1)(ODT) Key Findings/Insights from Contextual Review
20220107_0Discoverplan on user interviews
8 Jan 2022: donewhole team(ODT) Plan for Primary Research (user interview)
20220108_0Discoverinterviews on retirees20220107_014 Jan 2022: doneM2

(ODT) User Interviews and Notes - Retirees

(ODT) User Interview and Notes - User #1 (retiree)

20220108_1Discoverinterviews on families20220107_013 Jan 2022: doneM3

(ODT) User Interviews and Notes - Families

(ODT) User Interview and Notes - User #2 (family with young kids)

20220108_2Discoverinterviews on youths20220107_015 Jan 2022: doneM4

(ODT) User Interviews and Notes - Youths

(ODT) User Interview and Notes - User #3 (graduation trips)

20220115_0Discover

contextual review on "electronic products"

  • with focus on those which may be of interests to retirees and youths)

20220108_0

20220108_2


20 Jan 2022: doneM4(ODT) Contextual Review: Electronic Products
20220115_1Discover

contextual review on "sightseeing"

  • may focus on "sightseeing" by retirees and "families"?

20220108_0

20220108_1

17 Jan 2022: doneM5(ODT) Contextual Review: Sightseeing
20220107_1Discoverfind more detailed statistics on tourists who visited HK in previous years

7 Jan 2022: started

8 Jan 2022: completed first part, still have 2 more to go; hopefully can finish in 1 week

13 Jan 2022: completed

M2(ODT) Contextual Review: More Detailed Statistics on Tourists
20220113_0Discover

contextual reviews on "family-friendly activities"

    • take into considerations on any insights gained from interviews on families
20220108_116 Jan 2022: doneM3(ODT) Contextual Review: Family Friendly Activities
20220113_1Discoversummarize key findings/insights on user interviews

20220108_0

20220108_1

20220108_2

20220115_0

20220115_1

20220107_1

20220113_0

20 Jan 2022: donewhole team(ODT) Key Findings/Insights from User Interviews
20220113_2Definedefine persona20220113_122 Jan 2022: donewhole team(ODT) Persona
20220113_3Definedefine design brief

20220113_1

20220113_2

22 Jan 2022: donewhole team(ODT) Design Brief
20220113_4Developbrainstorm on possible directions on solutions

20220113_2

20220113_3

22 Jan 2022: donewhole team(ODT) Mindmap of Possible Directions on Solution
20220122_0......................







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
  • No labels