ToolStack
Shape UpGitHubStrong fit

Using GitHub for Shape Up

Dominant platform for source control and collaboration — used by 100M+ developers, making it the de facto standard for open-source and most commercial software teams. When combined with Shape Up, this makes GitHub a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Shape Up works best in GitHub when you leverage its custom workflows, roadmapping to implement the framework's key practices directly in the tool your team already lives in.

About Shape Up

Shape Up (Basecamp's methodology) works in 6-week cycles with fully shaped pitches — no backlogs, no sprints, no estimates. Teams get the full cycle to solve a problem however they see fit.

6-week cycles replace sprints — teams own the full scope and solution
Pitches (shaped work) replace backlogs — only shaped work enters cycles
Cooldown periods (2 weeks) between cycles allow exploration and cleanup
Fixed time, variable scope: teams cut scope to ship on time

How to set up Shape Up in GitHub

1

Set up your shaping workspace

Create a dedicated "Shaping" space in GitHub separate from delivery. Configure a custom workflow: Raw Idea → Being Shaped → Ready for Betting → Accepted → Cycle. Only PMs and shapers have write access to this space during the shaping phase.

2

Create pitch documents within the tool

In GitHub, create a card template for pitches that includes custom fields for: Problem statement, Appetite (S/M/L — where L = full 6-week cycle), Solution sketch link, Rabbit holes (known risks to avoid), and No-gos. Link the pitch card to the relevant cycle project when accepted.

3

Configure 6-week cycle projects

For each cycle, create a project in GitHub with a hard end date 6 weeks away. Use a Kanban board with columns: To Do, In Progress, Needs Review, Done — Shape Up teams self-organise tasks, so keep the board flexible. No backlog, no sprint planning — only the pitch scope.

4

Manage the hill chart (progress) and cooldown

Use GitHub's progress tracking to give a weekly "hill chart" update: which tasks are still unknown (uphill) vs being executed (downhill). At week 6, the cycle ends. Configure a "Cooldown" project template where teams file bugs, explore ideas, and clean up technical debt during the 2-week break.

Which GitHub features matter for Shape Up

GitHub has 2 of 2 core Shape Up features natively.

FeatureWhy it matters for Shape UpGitHub
Custom WorkflowsCustom stage definitions matching your process
RoadmappingStrategic planning and PI/initiative mapping
Kanban BoardsVisual flow board with column-based workflow
Custom FieldsTracking methodology-specific metadata
AutomationsReducing ceremony overhead with trigger-action rules

GitHub at a glance

G2 Score
4.7 / 5
Reviews
4k+
Free Tier
Yes
Starting Price
Free
Full GitHub review →GitHub website

Explore Shape Up

Shape Up full guide →

GitHub with other methodologies

GitHub for ScrumGitHub for KanbanGitHub for SAFe (Scaled Agile Framework)GitHub for OKRs (Objectives & Key Results)GitHub for Jobs-to-Be-Done (JTBD)GitHub for Lean StartupGitHub for Dual-Track AgileGitHub for Design ThinkingGitHub for LeSS (Large-Scale Scrum)GitHub for Spotify ModelGitHub for Extreme Programming (XP)GitHub for Crystal MethodsGitHub for Feature-Driven Development (FDD)GitHub for DSDM (Agile Business Consortium)GitHub for Six Sigma for ProductGitHub for Lean Product DevelopmentGitHub for Discovery-Driven PlanningGitHub for Opportunity Solution TreeGitHub for User Story MappingGitHub for Impact MappingGitHub for Kano ModelGitHub for RICE ScoringGitHub for MoSCoW PrioritisationGitHub for Value Proposition CanvasGitHub for Business Model CanvasGitHub for Wardley MappingGitHub for Customer Journey MappingGitHub for Event StormingGitHub for Domain-Driven Design for PMsGitHub for Continuous DiscoveryGitHub for Product-Led GrowthGitHub for North Star FrameworkGitHub for Goal Tree (Theory of Constraints)GitHub for GIST Planning