Skip to content

Planning

Jump to bottom
Pablo Mayrgundter edited this page Feb 8, 2024 · 1 revision

Our planning process is: Feature Requests/Bugs -> Requirements -> UX (epics, stories, tasks) -> UX-to-GitHub issue mapping -> Dev -> Production

Our main Planning project is here. We define our company's long-term, annual and quarterly goals using the OKR system.

We further break down long-term goals into product goals defined in terms of product Epics, Stories & Tasks and then develop at the Story & Task level during 2-week Sprints.

Tools

  • Discussions in Discord
  • General docs incl Requirements in Google Docs
  • UX is in Figma & Shortcut
  • High-level dev projects in Github projects
  • Dev tasks & bugs in Github issues

UX: Epics, Stories, Tasks

Epic

An Epic is a clearly defined value proposition to a user, e.g. "Bldrs Share can now open IFC" and comprises a major development effort to support that UX.

Story

Epics are broken into UX stories, that tell how a user accomplishes a significant step related to the Epic, e.g. "In Share, I got to the Open dialog, choose an IFC file, and click Open. Then it displays."

Task

Tasks are the fine-grained steps within Stories that represent atomic UI actions and responses, e.g. clicking on a button, after which a dialog is displayed.

Sprints

We turn UX Stories into GitHub Milestones and further map our planning to GH like this:

We maintain a leveled mapping from UX ↔ GitHub like this:

  • Shortcut Epics/Stories & Figma ↔ High-level Requirements in Google Docs
  • Shortcut Epic ↔ GitHub Project (Title = $EpicName - $Stage)
    • Shortcut Story ↔ GitHub Milestone (Title = $EpicName: $StoryName)
      • Shortcut UX Task ↔ GitHub UX Tracking Issue (Title = "UX: $TaskTitle", Body = List of Dev Task Issue Numbers)***
        • Dev Tasks ↔ GitHub Dev Issue
          • Pull Request(s), and cross-linked, Issues ↔ PRs

Example: Open (100)

One of our Epics is the Minimum Viable Feature for opening files. "100" is our shorthand for MVF, similar to a sketch or schematic capture in Architectural design. We'll revisit Open again at 200, 300 and 400 detail levels later.

Clone this wiki locally