Agile Beyond IT: Marketing, HR, and Agile Operations
Agile was born in software, but it works in any area that delivers value iteratively. Marketing, HR, legal, and operations already adopt Scrum and Kanban with significant results.
Agile Marketing
How It Works
- Campaign sprints — 2 weeks to plan, execute, measure
- Content backlog — posts, emails, events prioritized by impact
- 10-min daily — “what I published yesterday, what I’m publishing today”
- Retrospective — “did this campaign work? What should we change?”
Estimation
- T-Shirt sizing for campaigns (S = email, M = post, L = event, XL = launch)
- Lead time measures “from idea to publication”
- Velocity measures “campaigns delivered per sprint”
Agile HR
How It Works
- Recruitment sprints — hiring goals per sprint
- Job Kanban — “to triage → interviewing → offer → onboarded”
- Process retrospectives — “why do 40% of candidates drop out during the technical interview?”
Metrics
- Hiring lead time (from opening to offer)
- Throughput of filled positions per sprint
- Candidate satisfaction (survey)
Agile Operations
Kanban for Operations
Operations teams are natural Kanban:
- Tickets → demands from different sources
- WIP limits — how many demands can we handle simultaneously?
- SLA — maximum time per stage
Metrics
- Average resolution time
- Tickets above SLA
- Internal “customer” satisfaction
Estimation in Non-Technical Areas
Marketing
| Task | Size | Expected lead time |
|---|---|---|
| Blog post | S | 1-2 days |
| Email marketing | S | 2-3 days |
| Landing page | M | 3-5 days |
| Webinar | L | 1-2 weeks |
| In-person event | XL | 4-8 weeks |
HR
| Task | Size | Expected lead time |
|---|---|---|
| Screen resume | XS | 2 hours |
| Initial interview | S | 1 day |
| Full process | M | 1 week |
| Hiring + onboarding | L | 2 weeks |
Non-Technical Tools
- Trello — visual Kanban, easy to adopt
- Asana/Monday — project management for business teams
- Slack — communication and async dailies
- Google Sheets — simple velocity/throughput metrics
Challenges of Agile Beyond IT
Command-and-Control Culture
Managers used to assigning tasks resist self-organization.
Solution: Start with Kanban (less disruptive) before moving to Scrum.
No Backlog
Areas that work on demand (HR, support) don’t have a plan-able backlog.
Solution: Kanban with WIP limits and SLA, not sprints with fixed scope.
Different Metrics
“How many features” doesn’t make sense for marketing or HR.
Solution: Use throughput (how many demands handled) and quality (work outcome).
Conclusion
Agile works outside IT because it’s about delivering value iteratively with constant feedback, not about software. Adapt ceremonies, simplify metrics, and focus on results — not on following the Scrum book.