Aha Handbook

Project Management

We employ a mixture of Agile and Waterfall Methodologies. We are not strict adherents to any methodology and adapt the best of any method to our unique global, remote team.

Agile Scrum

  • We conduct daily Agile scrum meetings where we ask each team member what they did or completed since the last meeting, and what they plan to work on next.
  • Scrum meetings have strict 15 minute maximum durations.
  • Scrum masters are engineers and rotate every sprint.


  • 2 week per sprint
  • We use ZenHub to manage our sprints.
  • At the end of each week, we track and share each contributor’s burndown progress towards their sprint goals to the entire team.

ZenHub [Design, Engineering, Test]

  • We use ZenHub to maintain our progress of work.
  • A product management app (Kanban board) built on top of GitHub Project API integrations. All issues are linked to a GitHub issue.
  • The tasks to-do lists are organized for designers and engineers.
  • Each task starts off assigned to a (1) researcher, which gets passed to a (2) designer, (3) front-end developer, (4) back-end developer, (5) tester, (6) marketeer.
  • All issues are assigned to a parent epic, time estimate, and assignee.
  • Parents epics have deadlines in a roadmap.

Trello [Marketing]

  • Similar to JIRA, GitHub/Lab Issues
  • Each team member has a list in Trello that is sorted in order of importance. Each team member will work on his/her tasks in the order in the Trello board.


  • Our task management (using ZenHub issues) follows a waterfall structure where each feature is first researched by a PM or market researcher, to understand user needs and pain point, and competitive analysis of the market.
  • The PM will then pass on the feature requirement document to a UX/UI designer to design the feature. The product designers will first start with information architecture, then wireframes, and finally UI high fidelity mockups.
  • The design documents (Figma) are then given to front-end engineers to make the pixel-perfect components, and entire web page or native mobile app. Front-end engineers will build fake APIs at this stage to test the front-end UX.
  • Next, back-end engineers will build the requisite databases, logic, and API.
  • Finally, our test engineers will test and verify with the PM that the product is built as designed, with no bugs.

Prioritization and Triage - Initiatives, Epics, and Issues

  • Initiatives are product grouped devised by the PM, and prioritized by the PM.
  • Epics are groups of Issues created and organized by engineering.
  • Each initiative or sub-initiative contains many epics or issues.
  • PMs will prioritize the initiatives, while engineering will prioritize issues that belong to the high priority initiatives.