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

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 layer should be done before the sprint start.

  1. Product Brief:
    1. Essential Output: PRD (product requirements document).
    2. Outcomes & Value derived:
      1. PRD has been shared with Team Lead, Designer, and QA to get any feedback.
      2. All feedback on the PRD has been fixed and shared with the team during the meeting.
  2. Design:
    1. Essential Output: Design product (Figma UI design).
    2. Outcomes & Value derived:
      1. The draft design has been shared with the Product team, Team lead, and QA to get any feedback.
      2. All feedback on the design has been fixed 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. Team to scope of the project, what can be done in the sprint, and give a clear estimation for each assigned task.
  4. Test Strategy
    1. Essential Output:
      1. Test planning.
      2. Test scenario and test case.
    2. Outcomes & Value derived:
      1. QA to understand the project requirement and expected behavior for the products.
      2. Clarity all the cases to the team.

Building

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

  1. Implementing:
    1. Essential Output: Main goals for the product is implemented on the HH platform and ready to be tested by QA.
    2. Outcomes & Value derived:
      1. Product implemented according to the PRD and design.
      2. The product has been smoke-tested to ensure the product's main goal is ready to be tested by QA.
  2. Testing:
    1. Essential Output: The product has been tested, 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 for the product are implemented properly according to the PRD and design.
  3. Defect Management:
    1. Essential Output: Clear distinction between what ticket should be delivered in the sprint, the low-value tickets are moved to the next sprint/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 froze (no more code change) and if there is any update, QA needs to test it again and re-approve the PR.
  2. Release test.
    1. Essential Output: Merged release build has been tested.
    2. Outcomes & Value derived:
      1. QA to perform the last test on the merged release build (sanity test, integration test, and smoke test) before release.
      2. Approved the PR for release build and the build can be released.