What Scrum Actually Requires The Scrum Guide defines: 3 Artifacts: 1.
Product Backlog - Ordered list of everything that might be needed 2. Sprint Backlog - Selected items for sprint + plan to deliver 3.
Increment - Sum of completed items (Definition of Done met) 5 Events: 1. Sprint - Time-box for work (1-4 weeks) 2.
Sprint Planning - Define Sprint Goal, select items 3. Daily Scrum - 15-min daily sync 4.
Sprint Review - Inspect increment, adapt backlog 5. Sprint Retrospective - Inspect process, plan improvements 3 Roles: 1.
Product Owner - Manages Product Backlog 2. Scrum Master - Ensures Scrum is understood/enacted 3.
Developers - Create the Increment Most 'Scrum tools' only support: - A backlog (maybe) - Sprints as a filter - A board That's not Scrum. That's Kanban with a deadline.
GitScrum: Real Scrum Implementation Product Backlog Management The Product Backlog: - Single source of requirements - Ordered by value/priority - Continuously refined - Visible to everyone GitScrum Product Backlog: ┌─────────────────────────────────────────────────────────┐ │ Product Backlog Filter: All Search │ ├─────────────────────────────────────────────────────────┤ │ ⋮⋮ 1. User Authentication 5 pts ✓R │ │ ⋮⋮ 2.
Payment Integration 8 pts ✓R │ │ ⋮⋮ 3. Dashboard Analytics 5 pts ✓R │ │ ⋮⋮ 4.
Email Notifications 3 pts ✓R │ │ ⋮⋮ 5. User Profile Settings 3 pts │ │ ⋮⋮ 6.
Admin Panel 13 pts │ │ ⋮⋮ 7. Mobile App MVP 20 pts │ │ ...
│ │ ⋮⋮ 47. Legacy Data Migration ?
pts │ └─────────────────────────────────────────────────────────┘ ⋮⋮ = Drag to reorder ✓R = Ready for sprint Backlog features: - Drag-and-drop ordering - Story point estimates - Ready indicator (definition of ready met) - Quick add from anywhere - Bulk actions - Filters (unestimated, by epic, by label) Refinement Support: - Mark items as refined - Track refinement dates - Estimate during refinement - Split large items into smaller - Link to specs/wiki Sprint Planning Sprint Planning outputs: 1. Sprint Goal 2.
Selected items (Sprint Backlog) 3. Plan for delivering GitScrum Sprint Planning: ┌─────────────────────────────────────────────────────────┐ │ Sprint Planning: Sprint 15 │ ├─────────────────────────────────────────────────────────┤ │ Sprint Goal: │ │ ┌───────────────────────────────────────────────────┐ │ │ │ Launch user authentication and payment flow │ │ │ └───────────────────────────────────────────────────┘ │ │ │ │ Capacity: 32 pts (based on avg velocity) │ │ Selected: 21 pts │ │ │ │ ┌─────────────────────┬─────────────────────────────┐ │ │ │ Product Backlog │ Sprint 15 Backlog │ │ │ │ │ │ │ │ │ 1.
User Auth (5) → │ ✓ User Auth (5) │ │ │ │ 2. Payment (8) → │ ✓ Payment (8) │ │ │ │ 3.
Dashboard (5) → │ ✓ Dashboard (5) │ │ │ │ 4. Email (3) → │ ✓ Email (3) │ │ │ │ 5.
Profile (3) │ │ │ │ │ 6. Admin (13) │ │ │ │ └─────────────────────┴─────────────────────────────┘ │ │ │ │ Capacity remaining: 11 pts [Start Sprint] │ └─────────────────────────────────────────────────────────┘ Planning features: - Sprint Goal text field - Velocity-based capacity suggestion - Drag items from Backlog to Sprint - Real-time capacity meter - Over-commitment warning - Team availability adjustments - Planning session mode (read-only for non-planners) Sprint Backlog The Sprint Backlog: - Forecast of work for sprint - Plan to achieve Sprint Goal - Owned by Developers - Updated daily GitScrum Sprint Backlog Board: ┌────────────────────────────────────────────────────────────────┐ │ Sprint 15 Goal: Launch auth and payment │ │ Progress: 12/21 pts Burndown: On track Days: 5/10 │ ├──────────┬──────────┬──────────┬──────────┬──────────────────┤ │ To Do │ Progress │ Review │ QA │ Done │ │ (6 pts) │ (3 pts) │ (0 pts) │ (0 pts) │ (12 pts) │ ├──────────┼──────────┼──────────┼──────────┼──────────────────┤ │ Email │ Dashboard│ │ │ User Auth │ │ (3) │ (5) │ │ │ (5) ✓merged │ │ @maria │ @john │ │ │ @tom │ │ │ PR open │ │ │ │ │ Profile │ │ │ │ Payment v1 │ │ (3) │ │ │ │ (5) ✓merged │ │ │ │ │ │ @sarah │ │ │ │ │ │ │ │ │ │ │ │ Payment v2 │ │ │ │ │ │ (2) ✓merged │ │ │ │ │ │ @sarah │ └──────────┴──────────┴──────────┴──────────┴──────────────────┘ Board features: - Customizable columns - WIP limits per column - Story point aggregation - Git activity indicators - Assignee avatars - Quick task creation - Swimlanes by epic/assignee Daily Scrum Support The Daily Scrum: - 15 minutes - Same time/place daily - Answer: What did I do?
What will I do? Any impediments?
GitScrum doesn't force a daily meeting, but supports it: Daily View: - Yesterday's completed items - Today's in-progress items - Blocked items highlighted - Each person's focus visible Async Standup Option: - Post update in GitScrum - See team's updates - No meeting required - History preserved Activity Feed: - Who did what, when - Commits linked - PRs visible - Natural progress visibility Sprint Review The Sprint Review: - Inspect the Increment - Adapt the Product Backlog - Collaborate on next steps GitScrum Sprint Review Support: ┌─────────────────────────────────────────────────────────┐ │ Sprint 15 Review │ ├─────────────────────────────────────────────────────────┤ │ Sprint Goal: Launch auth and payment │ │ Status: ✓ Achieved │ │ │ │ Completed Items (4) Total: 15 pts │ │ ✓ User Authentication - @tom 5 pts │ │ ✓ Payment Integration v1 - @sarah 5 pts │ │ ✓ Payment Integration v2 - @sarah 2 pts │ │ ✓ Dashboard Analytics - @john 5 pts (added) │ │ │ │ Not Completed (2) Total: 6 pts │ │ ○ Email Notifications - @maria 3 pts │ │ Reason: Blocked by SMTP config │ │ ○ User Profile Settings 3 pts │ │ Reason: Deprioritized for dashboard │ │ │ │ Metrics │ │ Velocity: 15 pts (planned: 21) │ │ Completion: 71% │ │ Scope change: +5 pts (Dashboard added) │ │ Blockers: 1 │ └─────────────────────────────────────────────────────────┘ Review features: - Completed vs planned comparison - Sprint Goal achievement status - Individual item completion with who delivered - Incomplete items with reasons - Velocity calculation - Scope change tracking - Blocker summary - Exportable report Sprint Retrospective The Sprint Retrospective: - Inspect how sprint went (people, process, tools) - Identify improvements - Plan changes GitScrum Retrospective: ┌─────────────────────────────────────────────────────────┐ │ Sprint 15 Retrospective │ ├─────────────────────────────────────────────────────────┤ │ What went well? │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ + Payment integration smoother than expected │ │ │ │ + Good collaboration between frontend/backend │ │ │ │ + Auth completed ahead of schedule │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ What could be improved?
│ │ ┌─────────────────────────────────────────────────────┐ │ │ │ - SMTP config delayed email feature │ │ │ │ - Mid-sprint scope change was disruptive │ │ │ │ - Need better Definition of Ready │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ Action Items │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ ☐ Set up staging SMTP before Sprint 16 - @tom │ │ │ │ ☐ Add 'infra ready' to Definition of Ready - @PM │ │ │ │ ☐ Cap mid-sprint additions to 5 pts - Team │ │ │ └─────────────────────────────────────────────────────┘ │ │ [Save Retro] │ └─────────────────────────────────────────────────────────┘ Retro features: - Structured format (went well / improve / action items) - Anonymous option - Voting on items - Action item tracking - History of past retros - Improvement trend analysis Definition of Done Configurable DoD: Definition of Done: ☐ Code complete and committed ☐ Unit tests written and passing ☐ Code reviewed and approved ☐ Documentation updated ☐ Merged to main branch ☐ Deployed to staging ☐ QA approved GitScrum can auto-check: - PR merged (from Git integration) - Tests passing (from CI integration) - Code reviewed (from PR status) Definition of Ready Backlog items need DoR before sprint: Definition of Ready: ☐ User story written ☐ Acceptance criteria defined ☐ Story points estimated ☐ Dependencies identified ☐ Technical approach discussed Mark items as Ready in backlog. Filter to show only Ready items for planning.
Story Points & Estimation Estimation in GitScrum: - Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) - Or T-shirt sizes (XS, S, M, L, XL) - Or custom scale Planning Poker (async): - Team members vote - Reveal together - Discuss outliers - Reach consensus Velocity tracking: - Points completed per sprint - Rolling average - Trend visualization - Capacity planning input Burndown & Burnup Charts Burndown: Points │ 21 │━━━ │ ━━━ 15 │ ━━━●━━ │ ━━━ 10 │ - - - - - (ideal) │ ━ 0 │──────────────────────── Day 1 5 10 14 Burnup: Points │ ┌─ Done 21 │ ─────●━━ │ ───── 15 │ ───── ┌─ Scope │━━━━━━━━━━━━━━━━━━━ 10 │ │ 0 │──────────────────────── Day 1 5 10 14 Charts show: - Actual vs ideal progress - Scope changes - Projection to completion - Risk indicators Scrum + Git Integration GitScrum's unique value: Commits link to User Stories: - Reference 123 in commit - Story shows all commits - Progress visible via code PRs update Sprint Backlog: - PR opened → In Review - PR merged → Done - Definition of Done: PR merged Velocity verification: - Points 'done' backed by merged code - No phantom velocity - Real delivery measured Vs Jira for Scrum Jira: ✓ Full Scrum support ✓ Enterprise features ✗ Complex configuration ✗ Slow interface ✗ Expensive ($17.50+/user) ✗ Requires Scrum training ✗ Git requires plugin GitScrum: ✓ Full Scrum support ✓ Simple interface ✓ Fast ✓ $8.90/user ✓ No training needed ✓ Git integrated natively ✓ 2 users free Vs Trello for Scrum Trello: ✓ Simple board ✓ Easy to start ✗ No native Scrum support ✗ No sprints ✗ No velocity ✗ No burndown ✗ Requires Power-Ups for basics GitScrum: ✓ Scrum-native ✓ Still simple ✓ Full sprint support ✓ Velocity tracking ✓ Burndown charts ✓ Git integrated Vs Azure DevOps for Scrum Azure DevOps: ✓ Full Scrum support ✓ Microsoft integration ✗ Complex for small teams ✗ Azure ecosystem lock-in ✗ Pricing complex GitScrum: ✓ Full Scrum support ✓ Works with any Git ✓ Simple for any size team ✓ No lock-in ✓ Clear pricing Pricing for Scrum Teams 2 users: $0/month (free forever) 3 users: $8.90/month 5-person Scrum team: $26.70/month 10 users: $71.20/month Includes: - Full Scrum implementation - Product Backlog management - Sprint Planning - Sprint Backlog boards - Burndown/Burnup charts - Velocity tracking - Retrospectives - Git integration - All features No 'Scrum add-on'. No 'Advanced metrics' tier.
Getting Started with Scrum 1. Sign up (30 seconds) 2.
Create project 3. Add Product Backlog items 4.
Estimate with story points 5. Create first Sprint 6.
Drag items to Sprint 7. Start Sprint 8.
Track on board 9. Review at sprint end 10.
Retrospect and improve From signup to first sprint: 15 minutes. $8.90/user/month.
2 users free forever. Scrum the way it was meant to be.
The GitScrum Advantage
One unified platform to eliminate context switching and recover productive hours.
