Skip to main content
JobCannon
All skills

Agile & Scrum

Iterative development: sprints, standups, retrospectives

⬢ TIER 3Industry
Medium
Salary impact
4 months
Time to learn
Medium
Difficulty
3
Careers
TL;DR

Scrum is the process skeleton for iterative software development: sprints, ceremonies, backlog management. Career path runs Practitioner (participate in sprints) → Scrum Master (run ceremonies, remove blockers) → Agile Coach (scale across teams) over 3-6 months. The gap between "attends standups" and "certifiable Scrum Master" translates to $8-15k/year, particularly in midsize tech. Mastery includes SAFe/LeSS scaled frameworks for enterprise teams.

What is Agile & Scrum

Scrum is an iterative, time-boxed framework for software development: teams work in fixed sprints (usually 1-2 weeks), hold daily standups (15 min), conduct sprint planning (2 hours) and retrospectives (1.5 hours), and maintain a prioritized backlog. Core roles: Product Owner (orders backlog, maximizes value), Scrum Master (removes blockers, guards ceremonies), Development Team (ships). Scrum is lightweight by design—no mandatory documentation, no comprehensive upfront planning—making it ideal for volatile product environments where requirements shift. The gap between "attends standup" and "effectively runs sprint ceremonies + removes blockers" is real: Scrum Masters ($95-145k in US) command salary premiums over individual contributors because ceremony design and team dynamics directly impact velocity and morale. Scrum is the default framework in 90%+ of software teams, making it table-stakes for software engineering roles. The salary difference between Scrum practitioners ($90-120k) and Scrum Masters ($120-150k) is $20-30k/year in competitive markets. Beyond salary, learning Scrum is learning how to ship faster—teams properly running Scrum ship 30-50% faster than waterfall equivalents, giving you career positioning: "I ship fast" translates to promotions and seniority. Agile coaching (scaling Scrum across 10+ teams) is a $145-250k+ specialty with acute supply shortage. SAFe (Scaled Agile Framework) for enterprise teams adds another $15-25k to mid-level roles. Learning Scrum also makes you portable: every company from startups to Fortune 500 uses it, so the skill transfers.

đź”§ TOOLS & ECOSYSTEM
JiraAzure DevOpsLinearAsanaConfluenceMiroMuralRetrospective.appScrum@ScaleSAFeLeSSTrello

đź“‹ Before you start

đź’° Salary by region

RegionJuniorMidSenior
USA———
UK———
EU———
CANADA———

🎯 Careers using Agile & Scrum

âť“ FAQ

How long to go from zero to Scrum Master certification?
PSM I requires ~40-60 hours self-study (Scrum Guide, practice exams, maybe a bootcamp). Most people pass in 6-8 weeks of part-time prep. PSM II is harder — requires 2+ years Scrum Master experience, deeper process mastery, and typically 3 months harder study. No formal course required; the 80-page Scrum Guide is sufficient if you've lived it.
Scrum Master vs Product Owner vs Agile Coach — what's the difference?
Scrum Master (SM) removes blockers, guards ceremonies, enforces process. Product Owner (PO) orders the backlog, maximizes value. Agile Coach scales practices across multiple teams/squads. In small teams, one person might do all three. As you grow, split them. Coach is the rarest, highest-paid role.
Scrum vs Kanban — when do I use each?
Scrum is time-boxed (1-4 week sprints), best for product development with discrete deliverables. Kanban is continuous flow, better for ops/support with varying priorities. Many teams do Scrumban (Scrum container + Kanban flow inside sprints). Start Scrum if you're new; evolve if it doesn't fit.
Do I really need SAFe or LeSS if I have 2-3 small teams?
No. Core Scrum (one product owner, 1-3 teams, shared backlog) scales to ~50 people easily. SAFe/LeSS shine at 100+ people across multiple programs. If you're under 50, Scrum + good Confluence/Jira governance is enough. Adopt SAFe only if you have multiple product lines or can't align cross-team priorities.
How often do we really need retrospectives?
Every sprint (weekly for 1-week sprints, biweekly for 2-week). Non-negotiable. It's where you compound improvements — skip it and you'll repeat the same pain for 6 months. Format: 5-15 mins per team member sharing one thing that went well and one blocker. Rotating facilitator prevents SM burnout.
What if my team won't attend standups?
15-minute standups are lightweight; if people avoid them, something else is broken (meetings too long, not asynchronous-friendly, status theater). Run async standups for remote teams (Slack/Jira updates by 9am). If your team is all in-room, standing desks make it harder to linger — bad standup isn't about format, it's about culture.

Not sure this skill is for you?

Take a 10-min Career Match — we'll suggest the right tracks.

Find my best-fit skills →

Find your ideal career path

Skill-based matching across 2,536 careers. Free, ~10 minutes.

Take Career Match — free →