KANBAN-STYLE PROJECT MANAGEMENT WITH GITHUB

“Visualize work, limit chaos, flow with purpose.”

This guide merges Agile Kanban with GitHub's collaboration tools and automation to create a fluid, iterative, and organized workflow.

🗺️ Overview

1️⃣ PROJECT SETUP

📁 Create Repository

Initialise your GitHub repo or clone an existing one.

git init
git remote add origin <repo-url>
git pull origin main

2️⃣ PLAN WITH KANBAN & ISSUES

📌 Create GitHub Project (Classic or Projects v2)

• Use Kanban-style columns:
  • Backlog
  • To Do
  • In Progress
  • Review
  • Done

🐛 Create Issues

Use Issues for:

• Features
• Bugs
• Enhancements
• Documentation

Structure:

### Title: Add user login
**Description:** Implement secure login with JWT.
**Labels:** `feature`, `frontend`
**Assignee:** @devname
**Estimate:** 4h

🎯 Group with Milestones

Each Milestone = a Release or Sprint

Milestone: v1.0
Due: 2025-07-30
Includes: Auth, UI, API Integration

3️⃣ GIT FLOW STRATEGY (TEAM-FRIENDLY)

🌳 Branch Structure

main          ← Production-ready code
develop       ← Integration branch
feature/*     ← New features (from `develop`)
bugfix/*      ← Small fixes (from `develop`)
hotfix/*      ← Emergency fixes (from `main`)
release/*     ← Prep branch for deployment (merge into `main`)

🌀 Example Workflow

# Start a feature
git checkout develop
git checkout -b feature/login-form

# Work, commit
git commit -m "feat: add login form"

# Push and create PR
git push origin feature/login-form

Create Pull Requests, link issues with Closes #issue_number in the PR description.

Merge rules:

• feature/* → develop
• release/* → main + develop
• hotfix/* → main + develop

4️⃣ AUTOMATE WITH GITHUB ACTIONS

🔄 Sample Workflows

✅ Lint, Test, Build on Push

.github/workflows/ci.yml:

name: CI

on:
  push:
    branches: [develop, feature/*, release/*]
  pull_request:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install deps
        run: npm install
      - name: Run Tests
        run: npm test
      - name: Lint
        run: npm run lint

🚀 Deploy on Release

.github/workflows/deploy.yml:

name: Deploy

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Build
        run: npm run build
      - name: Deploy
        run: ./scripts/deploy.sh

5️⃣ BEST PRACTICES

🧭 Visualise Flow

• Keep Issues updated in the Kanban board
• Use labels: frontend, backend, urgent, low-priority

🧪 Review Frequently

• Daily Standup = Review board + PRs
• Use PR templates with a checklist
• Tag reviewers + testers

📦 Bundle with Milestones

• Set due dates and use burndown charts (3rd party integrations like ZenHub)

🪄 Automate:

• Auto-move cards with Project automation
• Auto-close issues via PR merge messages

🌊 SAMPLE FLOW IN ACTION

1. Open Issue: "Add user login"
2. Assign to Milestone "v1.0"
3. Move card to "To Do"
4. Create branch: feature/user-login
5. Push commits, open PR → Link issue
6. Move to "In Progress", then "Review"
7. Run CI tests → Approve PR
8. Merge to `develop` → Issue auto-closed
9. On release: merge `release/v1.0` to `main`
10. Deploy via GitHub Actions
11. Move card to "Done"

🧰 OPTIONAL: ADD TOOLS FOR INSIGHT