Scrum

You've held SMC, SAMC, and SPOC. You're three years past your first Scrum project. Now you're scaling Scrum across teams, programs, or portfolios — and the framework's defaults stop holding.

Your team uses Scrum. Their team uses Kanban. The team upstream uses something they call 'Scrumban' but won't admit is mostly Waterfall. SAMC is the credential that certifies you actually know what each one is for.

One Scrum team turned into three. Three turned into seven. Now you're coordinating standups across teams, and the impediment list is no longer something one person can carry.

You used to own one backlog. Now there are four Product Owners reporting into you and they're prioritizing against different signals. Someone has to make the call.

You're on a Scrum team and you've been making it work by watching how the experienced people operate. The framework was never explained to you. SDC is the credentialed answer.

Scrum keeps coming up in your work and no one has ever sat you down and explained what it actually is. SFC is the no-cost foundation that fixes that before you decide whether to go further.

You're the person who keeps sprints moving when stakeholders shift priorities, who clears impediments before they slow delivery, and who holds the framework when everyone else wants to skip the ceremonies. SMC is the credential that names that role.

You're the one explaining to engineering why a feature stakeholders called 'priority one' last week is now 'maybe later.' The backlog is yours. So is the answer when someone asks why their thing isn't on it.

You're past 'do the ceremonies apply.' You're asking how to redesign operational workflow using Scrum without breaking the system that's already running.

Your ops team has heard about Scrum but no one has explained whether ceremonies designed for software delivery actually apply to running infrastructure, keeping a plant floor moving, or holding a support queue. SODFC answers that question without costing you anything.