đź“—
Processes
  • Intro
  • Getting Started
    • Your first day
    • General work ethic
    • Important contacts
    • Important Links
    • Team Communication
    • Remote work code of conduct
  • Product processes
    • Roles & Responsibilities
    • Meeting Structure
      • 1:1 Meetings
      • Design Kick-Off
      • Design Review
      • Dev Kick-Off
      • Estimation Meeting
    • How to Introduce a Feature
    • Writing Effective User Stories
    • Writing a Design Overview
    • Prioritization (with RICE)
    • How to roughly estimate as PM & Designer
    • Design Sprints
      • Setup/ Preparations
      • Monday
      • Tuesday
      • Wednesday
      • Thursday
      • Friday
      • Sprint Decision Making Process
      • Recruiting customers for Friday's interviews
    • Project Management - Product, Dev and Design
    • Definition of Ready (for development)
  • Stakeholder requests
  • Submit a Bug Report or Feature Request
  • Data Protection: User Deletion Requests
  • Testing structure
    • Testing mobile
    • Manual Regression Tests
  • Technology
    • Development Process
Powered by GitBook
On this page
  • Mobile App workflow:
  • Engineering workflow:

Was this helpful?

  1. Product processes

Project Management - Product, Dev and Design

PreviousRecruiting customers for Friday's interviewsNextDefinition of Ready (for development)

Last updated 4 years ago

Was this helpful?

This article covers the Project management and workflows used by the team.

The current project management tool used by the team is Clubhouse:

To understand how Clubhouse works, please visit and read the on-boarding sections and articles.

Mobile App workflow:

This is the home of our Mobile app engineering boards, which include the BEAT81 App (Customer app) and the Workout App.

The workflow follows the following states:

Backlog | Ready for development:

  1. Tickets are added from Product backlog after prioritisation

  2. Tickets move into Ready for Development after being discussed and estimated by the Mobile dev team

In progress | Fix required | Code Review | QA (Test build):

  1. Tickets are being worked on and code reviewed by the Mobile dev team

  2. Bundled together into a TEST APP build for the team to QA.

  3. QA results into Tickets being Accepted or Rejected (“Fix required”)

Accepted | Live (Prod build):

  1. Tickets are accepted

  2. Final Build is released to App Stores

Engineering workflow:

This is the home to our main engineering flow, mainly including web releases and backend changes that do not require a special rollout and QA process.

Backlog | Ready for Development:

  1. Tickets are added from Product backlog after prioritisation

  2. Tickets move into Ready for Development after being discussed and estimated by the Mobile dev team

In Progress | Blocked | In Code Review | In QA:

  1. Tickets are being worked on and code reviewed by the Engineering team

  2. Tickets move to QA and are either rejected (“Blocked”) or Accepted

Accepted | Live:

  1. Accepted tickets are released to prod and moved to LIVE

Product and Infrastructure workflows:

These are homes to every future feature, bug and chore added to the backlog. These workflows' goals are to triage tickets and set a priority before they are moved to the engineering and mobile apps workflows for discussion, estimation and production.

app.clubhouse.io/b81
https://help.clubhouse.io/hc/en-us