We use a few different project management tools to keep us on track and in sync. We’re always trying out new ones too — DM Catherine if you’ve got a favorite you think would make a great addition to the team!
Great company, great product. Keeping in sync with one another on big, long term projects can be challenging–and this is where Basecamp comes into play. It will look different for every team, and every project — but our main guidelines for using Basecamp look something like:
- Teams: You’ll be added individually to the teams you work directly with. Within a Basecamp team, you’ll find a few things:
- Message Board: Meeting notes and agendas can be found here
- To Do’s: Essential for staying on task! You can tag and assign to-do’s to individuals or groups–check them off when complete. Everyone on the team can see the to-do list, even if they’re not assigned to one directly.
- Schedule: You can create a schedule with due dates/deadlines for your to-do list. Anyone on the team can subscribe to the calendar (it will auto-populate to your GCal), which gives equal visibility to teammates for all parts of a project.
- Docs & Files: Upload any pertinent docs/files to the team–any teammate can then easily access the necessary files straight from Basecamp. Farewell, back and forth emails!
- Projects: Team members can also be added to shared projects. Same layout as teams, just project-specific.
- Campfire: this serves as our back-up team chat should Slack ever go down. Max will send out a team message reminding everyone to log into SkyVerge HQ and continue chatting via Campfire.
Additionally, every team member will be added to SkyVerge HQ. At the beginning of each week, Max posts updates on company-wide announcements, important policy changes, general goings-on, and individual shout-outs to team members for their great work. Any time he posts an announcement, everyone will get an email as well. Nifty! Our hope with the Weekly Update is to increase transparency and communication across the different teams here at SkyVerge. You can see past Weekly Updates here. (Must be logged into Basecamp to access.)
GitHub houses our code in various repositories, including all of our WooCommerce plugins, the Plugin Framework, internal tools such as sake, and the Jilt rails app. All development takes place in branches/pull requests, all code reviews and many engineering discussions take place in pull request conversations, and the repository wiki’s are used to house technical documentation. Previously issues/project boards were used heavily, but we’re currently (early 2019) in the process of transitioning all of those uses into Clubhouse, as described in the next section.
We use Clubhouse to track feature projects within Jilt. Clubhouse is excellent for tracking multi-part projects, and involve team members from other areas, such as marketing. It helps us (a) keep the entire team apprised of project progress, making it easily discoverable, and (b) makes it obvious which projects require more than code (e.g., marketing announcements or a launch plan).
You can read more here about why we started using Clubhouse, and how it differs from GitHub or Basecamp. (Must be logged into Basecamp to access.)
We use Trello to track feature requests for WooCommerce plugins & customer feedback for Jilt. Trello is wonderful for freeform organization of ideas & other loosely-defined projects, but we try to use tools with a bit more structure these days.