Product Playbook — HMX Documentation

Onboarding Checklist

Your Progress

0%

1General Setup— required for everyone

HashMicro Email

Get your company email account before doing any downstream setup.

Google Account

Create a Google account using the HashMicro email address.

Hashchat

Create a Hashchat account using the same company identity.

PMT Access

Create a PMT account to participate in planning, assignment, and delivery tracking.

Apollo Account

Create an Apollo account — HashMicros internal AI assistant used across product, engineering, and support teams.

2Role-Specific Setup— pick your role, then tick off each item

Choose your role

Pick a role above to reveal the checklist.

Create GitLab account

Request access and register with your HashMicro email.

Install GitHub Desktop and clone repository

Install the client, authenticate, and clone the project repo you will work on.

Install code editor

Install your preferred editor (VS Code, PyCharm, or equivalent).

Create GitLab account

Request access and register with your HashMicro email.

Install GitHub Desktop and clone repository

Install the client, authenticate, and clone the project repo you will test.

Install code editor

Install a code editor to inspect source, run tests, and edit fixtures.

Create Figma account

Sign up with your HashMicro email and request access to the design workspace.

Request access to documentation panel

Ask for access to the HMX documentation panel so you can create, edit, and maintain product documentation.

Create GitLab account

Make sure your GitLab account is active and has access to the repositories used by your team.

Install GitHub Desktop and clone repository

Install the client, authenticate, and clone the codebase you will develop in.

Install code editor

Install your preferred editor (VS Code, Cursor, PyCharm, or equivalent) for daily development work.

Practical reading: the checklist is structured to get communication, planning, repository access, and execution tooling ready before work starts.

PMT Guide

PMT is a task management tool that enables teams to plan, prioritize, and deliver work by breaking tasks into manageable units and assigning clear ownership.

Sprint Rules

Before choosing a task type: every PMT task should follow the sprint rules first, then be classified into the right task type.

Important: 1 sprint = 1 week.

Cadence: a sprint is a time-boxed iteration for planning and execution, with a duration of one week.

Weekly cycle: Day 1 is used for planning, Day 1 to Day 4 for execution, and Day 5 for review and release decisions.

P1

Phase 1 - Sprint Planning (Day 1)

Start the sprint, check team capacity, propose goals or stories, get approval, and lock the sprint backlog before execution begins.

P2

Phase 2 - Sprint Execution (Day 1-4)

Run daily standup, assign PRD, share design feedback, prepare test cases, develop, test, review, and loop bugs back to development until the sprint scope is clear.

P3

Phase 3 - Sprint Review and Release (Day 5)

Demo the result, get feature approval, collect feedback, move revisions into the next sprint backlog, refine backlog priority, and close the sprint.

Decision loops: If goals are rejected, revise them during planning. If bugs are found or deployment fails, return the work to development. If review feedback is not approved, carry revisions into the next sprint backlog.

Task Types

NF

New Feature

Development of a completely new functionality.

IM

Improvement

Enhancement or optimization of an existing feature.

BG

Bug

Fixing a defect or unintended behavior.

TK

Task

Operational or technical work not directly tied to a feature or bug.

DS

Discussion

Alignment, clarification, or decision-making activity.

RL

To Release

Preparation and activities required for deployment or release.

Point Calculation

Point Label	Minimum Time
Momentarily	30 minutes
Lowest	1 hour
Low	2 hours
Medium	3 hours
High	4 hours
Highest	5 hours

Rule from source: any task that requires more than 5 hours must be broken down into smaller tasks.

HMX Development

The HMX section in the source handbook links to working references for product delivery. Two links are populated in the source page and are surfaced below.

HMX PRD

Product Requirement Document reference folder from the source handbook.

Open PRD Folder

HMX Test Case

Testing reference folder linked directly from the handbook.

Open Test Case Folder

HMX Standard Rules

Present as a heading in the source handbook, but no external link is attached there yet.

Open Source Page

Deployment Cycle

The handbook includes a dedicated HMX | Deployment Cycle section followed by a diagram image sourced from the original handbook.

Deployment cycle diagram from source handbook

The image above is pulled from the linked Notion handbook and embedded locally into this docs panel.