Seasonal Campaign Planning | Fixed Deadline Projects
Plan time-bound campaigns with backward scheduling and scope tiers. GitScrum tracks milestones, dependencies, and launch checklists for on-time delivery.
9 min read
Campaigns and seasonal projects have hard deadlines. GitScrum helps teams plan backwards from launch dates, coordinate cross-team efforts, and ensure timely delivery.
Campaign Planning
Backward Planning
PLANNING FROM DEADLINE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ EXAMPLE: Black Friday Campaign │
│ Launch: November 29 (Black Friday) │
│ │
│ WORK BACKWARDS: │
│ │
│ Nov 29 ← LAUNCH │
│ ↑ │
│ Nov 27 ← Final testing (2 days buffer) │
│ ↑ │
│ Nov 24 ← Code freeze (3 days before) │
│ ↑ │
│ Nov 22 ← QA complete │
│ ↑ │
│ Nov 15 ← Development complete │
│ ↑ │
│ Nov 10 ← Design complete │
│ ↑ │
│ Nov 1 ← Requirements locked │
│ ↑ │
│ Oct 15 ← Planning complete, work begins │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ BUFFER IS MANDATORY: │
│ Things will go wrong │
│ Build in slack for unknowns │
│ Never plan to finish on launch day │
│ │
│ TIMELINE MATH: │
│ 6 weeks total │
│ 1 week buffer │
│ 5 weeks actual work │
│ Scope must fit in 5 weeks │
└─────────────────────────────────────────────────────────────┘
Campaign Epic
CAMPAIGN PROJECT STRUCTURE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ CAMPAIGN EPIC: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ CAMP-001: Black Friday 2024 Campaign ││
│ │ ││
│ │ Launch: Nov 29, 2024 ││
│ │ Owner: @campaign-lead ││
│ │ Status: In Progress ││
│ │ Days remaining: 42 ││
│ │ ││
│ │ WORKSTREAMS: ││
│ │ ││
│ │ PROMOTIONS: ││
│ │ ├── CAMP-010: Discount engine ⏳ ││
│ │ ├── CAMP-011: Promo code system ⏳ ││
│ │ └── CAMP-012: Bundle deals ☐ ││
│ │ ││
│ │ LANDING PAGES: ││
│ │ ├── CAMP-020: Hero section ✅ ││
│ │ ├── CAMP-021: Product grid ⏳ ││
│ │ └── CAMP-022: Countdown timer ⏳ ││
│ │ ││
│ │ EMAIL: ││
│ │ ├── CAMP-030: Teaser campaign ✅ ││
│ │ ├── CAMP-031: Launch announcement ☐ ││
│ │ └── CAMP-032: Reminder series ☐ ││
│ │ ││
│ │ INFRASTRUCTURE: ││
│ │ ├── CAMP-040: Capacity planning ✅ ││
│ │ ├── CAMP-041: CDN configuration ⏳ ││
│ │ └── CAMP-042: Monitoring alerts ☐ ││
│ │ ││
│ │ MUST-HAVE: CAMP-010, 011, 020, 021, 040 ││
│ │ NICE-TO-HAVE: CAMP-012, 022, 032 ││
│ └─────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────┘
Scope Management
Fixed Date = Flex Scope
SCOPE NEGOTIATION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WHEN DEADLINE IS FIXED: │
│ │
│ ❌ "We'll work overtime to fit everything" │
│ ❌ "We'll skip testing to meet the date" │
│ ✅ "What can we cut to fit the timeline?" │
│ │
│ SCOPE TIERS: │
│ │
│ TIER 1 - MUST HAVE (Non-negotiable): │
│ Features required for campaign to function │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ☐ Discount calculation works correctly ││
│ │ ☐ Landing page loads and looks good ││
│ │ ☐ Checkout accepts discounted prices ││
│ │ ☐ System handles expected traffic ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ TIER 2 - SHOULD HAVE (High value, can simplify): │
│ Important but can be reduced │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ☐ Countdown timer (fallback: static banner) ││
│ │ ☐ Personalization (fallback: static content) ││
│ │ ☐ Bundle deals (fallback: simple discounts) ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ TIER 3 - NICE TO HAVE (If time permits): │
│ Enhancements, can defer │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ☐ Animated effects ││
│ │ ☐ Social sharing ││
│ │ ☐ Gamification elements ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ RULE: Cut Tier 3 first, then simplify Tier 2 │
│ Never compromise Tier 1 quality │
└─────────────────────────────────────────────────────────────┘
Dependencies
Coordination Points
CROSS-TEAM DEPENDENCIES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ CAMPAIGN DEPENDENCIES: │
│ │
│ FROM MARKETING: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ DEP-001: Final creative assets ││
│ │ Needed by: Nov 8 (for landing page build) ││
│ │ Owner: @marketing ││
│ │ Status: In progress ││
│ │ Risk: High if late - blocks landing page ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ FROM LEGAL: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ DEP-002: Terms and conditions approval ││
│ │ Needed by: Nov 10 (for discount engine) ││
│ │ Owner: @legal ││
│ │ Status: Pending review ││
│ │ Risk: Medium - can launch with placeholder ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ FROM INFRASTRUCTURE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ DEP-003: Additional server capacity ││
│ │ Needed by: Nov 20 (for load testing) ││
│ │ Owner: @devops ││
│ │ Status: Approved, pending provisioning ││
│ │ Risk: Low - on track ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ DEPENDENCY TRACKING: │
│ • Regular check-ins with owners │
│ • Escalate blockers immediately │
│ • Have backup plans for high-risk items │
└─────────────────────────────────────────────────────────────┘
Risk Management
Campaign Risks
RISK MITIGATION:
┌─────────────────────────────────────────────────────────────┐
│ │
│ CAMPAIGN RISK REGISTER: │
│ │
│ TIMELINE RISKS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Risk: Creative assets delayed ││
│ │ Impact: High (blocks development) ││
│ │ Mitigation: Placeholder content, weekly check-ins ││
│ │ Contingency: Simplified design with stock assets ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ TECHNICAL RISKS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Risk: Traffic spike crashes site ││
│ │ Impact: Critical (lost sales) ││
│ │ Mitigation: Load testing, auto-scaling, CDN ││
│ │ Contingency: Queue system, static failover page ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ BUSINESS RISKS: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Risk: Discount code exploited ││
│ │ Impact: High (financial loss) ││
│ │ Mitigation: Rate limiting, usage caps, monitoring ││
│ │ Contingency: Kill switch to disable codes ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ FOR EACH RISK: │
│ • What could go wrong? │
│ • How bad would it be? │
│ • How do we prevent it? │
│ • What do we do if it happens anyway? │
└─────────────────────────────────────────────────────────────┘
Launch Preparation
Pre-Launch Checklist
LAUNCH READINESS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ PRE-LAUNCH CHECKLIST: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ CAMP-PRE: Black Friday Launch Checklist ││
│ │ ││
│ │ TECHNICAL (Nov 27 - 2 days before): ││
│ │ ☐ All code deployed to production ││
│ │ ☐ Feature flags set (off until launch) ││
│ │ ☐ Load test passed ││
│ │ ☐ CDN cache warmed ││
│ │ ☐ Monitoring dashboards ready ││
│ │ ☐ Alerts configured and tested ││
│ │ ││
│ │ CONTENT (Nov 28 - 1 day before): ││
│ │ ☐ All content reviewed and approved ││
│ │ ☐ Discount codes loaded and tested ││
│ │ ☐ Email campaigns scheduled ││
│ │ ☐ Social posts scheduled ││
│ │ ││
│ │ OPERATIONS (Nov 29 - launch day): ││
│ │ ☐ On-call team identified and available ││
│ │ ☐ Rollback plan documented ││
│ │ ☐ Customer support briefed ││
│ │ ☐ Communication channel established ││
│ │ ││
│ │ GO/NO-GO DECISION: ││
│ │ Stakeholder sign-off: ☐ ││
│ │ Tech lead approval: ☐ ││
│ │ Marketing approval: ☐ ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ LAUNCH TRIGGERS: │
│ • Enable feature flags at specified time │
│ • Monitor dashboards │
│ • All hands on deck for first 2 hours │
└─────────────────────────────────────────────────────────────┘
Post-Campaign
Campaign Retrospective
POST-CAMPAIGN REVIEW:
┌─────────────────────────────────────────────────────────────┐
│ │
│ CAMPAIGN RETROSPECTIVE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ CAMP-RETRO: Black Friday 2024 Review ││
│ │ ││
│ │ RESULTS: ││
│ │ Revenue: $1.2M (target: $1M) ✅ ││
│ │ Traffic: 50K visitors (handled smoothly) ✅ ││
│ │ Uptime: 99.9% ✅ ││
│ │ Conversion: 4.2% (target: 3.5%) ✅ ││
│ │ ││
│ │ WHAT WENT WELL: ││
│ │ • Started planning 6 weeks early ││
│ │ • Buffer time saved us when assets were late ││
│ │ • Load testing caught issue before launch ││
│ │ • On-call team resolved one issue in 5 min ││
│ │ ││
│ │ WHAT COULD IMPROVE: ││
│ │ • Creative assets delivered 3 days late ││
│ │ • One promo code didn't work initially ││
│ │ • Mobile testing was rushed ││
│ │ ││
│ │ ACTIONS FOR NEXT CAMPAIGN: ││
│ │ ☐ Start creative requests 2 weeks earlier ││
│ │ ☐ Add promo code testing to checklist ││
│ │ ☐ Dedicated mobile testing day ││
│ │ ││
│ │ REUSABLE ASSETS: ││
│ │ • Discount engine (can reuse) ││
│ │ • Landing page template (can reuse) ││
│ │ • Monitoring dashboard (archive for next year) ││
│ └─────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────┘