Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

DRAFT DEVELOPMENT FLOW WIP

Activity Overview

Product development timeline

Note: The timeline image filename includes Y2023 because it references the original visual asset version, while this document follows the current knowledge base timestamp naming convention.

Shaping

Shaping is primarily design work. The shaped concept is an interaction design viewed from the user’s perspective. It defines what the feature does, how it works, where it fits into existing flows, and what can be done during the sprint. The shaping phase should be completed before the sprint starts.

  1. Product Brief:
    1. Essential Output: PRD (product requirements document).
    2. Outcomes & Value derived:
      1. The PRD is shared with the Team Lead, Designer, and QA for feedback.
      2. All PRD feedback is addressed and shared with the team during the meeting.
  2. Design:
    1. Essential Output: Product design (Figma UI design).
    2. Outcomes & Value derived:
      1. The draft design is shared with the Product team, Team Lead, and QA for feedback.
      2. All design feedback is addressed and shared with the team during the meeting.
  3. Task Breakdown:
    1. Essential Output: Task breakdown document.
    2. Outcomes & Value derived:
      1. The team understands the project well enough to make informed decisions on the development strategy.
      2. The team scopes the project and understands what can be delivered in the sprint.
      3. The team provides a clear estimate for each assigned task.
  4. Test Strategy:
    1. Essential Output:
      1. Test planning.
      2. Test scenarios and test cases.
    2. Outcomes & Value derived:
      1. QA understands project requirements and expected product behavior.
      2. Clarity on all test cases is provided to the team.

Building

Building and iterating how the project should be completed during the sprint.

  1. Implementing:
    1. Essential Output: Main goals for the product are implemented on the HungryHub (HH) platform and are ready to be tested by QA.
    2. Outcomes & Value derived:
      1. The product is implemented according to the PRD and design.
      2. The product is smoke-tested to ensure its main goals are ready for QA testing.
  2. Testing:
    1. Essential Output: The product has been tested, and the main goals for the product are implemented properly according to the PRD and design.
    2. Outcomes & Value derived:
      1. The product is tested, and the main goals are implemented properly according to the PRD and design.
  3. Defect Management:
    1. Essential Output: Clear distinction is made between tickets for this sprint and low-value tickets. Low-value tickets are moved to the next sprint or cooldown period.
    2. Outcomes & Value derived:
      1. Ticket prioritization.
      2. Low-value tickets are moved to the next sprint/cooldown period.

Releasing

  1. Merging:
    1. Essential Output: Merged release build.
    2. Outcomes & Value derived:
      1. Approved PRs are merged into develop and frozen (no more code changes). If there is any update, QA needs to test it again and re-approve the PR.
  2. Release Test:
    1. Essential Output: The merged release build has been tested.
    2. Outcomes & Value derived:
      1. QA performs the last test on the merged release build (sanity test, integration test, and smoke test) before release.
      2. The PR for the release build is approved and the build can be released.