Skip to content
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.

Latest commit

 

History

History
51 lines (33 loc) · 3.23 KB

PROJECT_MANAGEMENT.md

File metadata and controls

51 lines (33 loc) · 3.23 KB
Raw

This page is archived. Please visit https://countable-ops-manual.readthedocs.io/

Project Management

Purpose

Set conventions for communication between project stakeholders to maximize our velocity towards objectives.

Scope

This document summarizes project management tooling and practices at Countable to assist with onboarding.

Process

  • Every project has a "Purpose" which must be documented and visible.
  • Every project has at least one Objective and Key Result every month.
  • We use Scrum like this.
  • Every day, try to get some feedback on your work.
  • Every day, coordinate with team mates on slack and prioritize.
  • Work together to minimize the amount of time anyone is blocked or waiting for someone's output as their input. The list of items in which people depend on each other's work is called the critical path.

Tools

GIT

For developers - We follow the git-flow branching conventions loosely. All projects should have a master (production) branch which releases are made from, and a develop (stable) branch for developers as a foundation to build features on. Feature branches are created from develop and merged back in via pull request when ready. Here are some examples of how we'd use GIT in different cases.

Trello

We use Trello for project management, as it allows unlimited access to boards by partners and clients, encouraging collaboration and transparency. See TRELLO.md.

Screencastify chrome extension

Especially when dealing with a remote team, customers tend to be more anxious about project progress and features implementation. To overcome this situation and to keep our customers aware of our current development status we can use this chrome extension to record short screencasts with a brief summary of the latest changes. After this, generate a shareable link and send to them through e-mail, in a weekly basis.

  • Don't spend more than 10 minutes to do it, since its just a short and simple video.
  • Be professional in your tone and language.
  • This methodology is particularly useful for front-end changes, since they're visible.
  • In case you're dealing with back-end related work, you can still do the screencast, but your approach should be different: You'll have to explain and summarize what you're working on, and show some important parts of the code that you developed.

Things We Want To Improve

  • Increase transparency of our work to clients, team mates, managers. Dashboard for client.
  • Performance metrics, data for retrospectives.
  • Automate timesheets, and invoices using Trello card data.
  • Automate moving trello cards based on commits.
  • Simple to explain to new people. Mostly automated. Avoid slowing down developers who are less oriented to PM process.
  • Link bitbuckets commits.
  • Easy for clients to submit a ticket. Bug or Feature, URL, screenshot.
  • Provide our customers with a constant feedback loop, updating them upon a new feature release or any significant changes on their current project.