Project Management - Product, Dev and Design
Last updated
Last updated
This article covers the Project management and workflows used by the team.
The current project management tool used by the team is Clubhouse: app.clubhouse.io/b81
To understand how Clubhouse works, please visit https://help.clubhouse.io/hc/en-us and read the on-boarding sections and articles.
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:
Tickets are added from Product backlog after prioritisation
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):
Tickets are being worked on and code reviewed by the Mobile dev team
Bundled together into a TEST APP build for the team to QA.
QA results into Tickets being Accepted or Rejected (“Fix required”)
Accepted | Live (Prod build):
Tickets are accepted
Final Build is released to App Stores
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:
Tickets are added from Product backlog after prioritisation
Tickets move into Ready for Development after being discussed and estimated by the Mobile dev team
In Progress | Blocked | In Code Review | In QA:
Tickets are being worked on and code reviewed by the Engineering team
Tickets move to QA and are either rejected (“Blocked”) or Accepted
Accepted | Live:
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.
