What are the five C's of Scrum?

The five C's of Scrum are Collaboration, Communication, Commitment, Courage, and Continuous Improvement. These five principles form the backbone of how Scrum teams actually work together to deliver value.

Collaboration

Collaboration means real teamwork across all Scrum roles: Product Owner, Scrum Master, and Developers. It's not just sitting in the same room. It's the Product Owner working with Developers to clarify what "done" looks like, the Scrum Master removing blockers so people can focus, and Developers pushing back when a sprint goal isn't realistic. This cooperative effort is what gets common goals met.

Communication

Effective communication in Scrum isn't optional. Daily stand-ups, sprint reviews, and retrospectives create the structure for it. But structure alone doesn't work. You need people willing to say what's actually happening, not what sounds good. When a Developer admits they're stuck on a technical problem three days in, that's communication working. When a Product Owner hears feedback in a sprint review and actually changes priorities, that's communication working.

Commitment

Commitment means team members show up for their roles and responsibilities. It's not about blind loyalty to a sprint goal no matter what. It's about saying "I will do what I said I'd do this sprint" and then doing it. Each member commits to the sprint goal and to supporting teammates when someone hits a wall.

Courage

Courage is the one most teams underestimate. It's a Developer telling the Product Owner that a feature request will break the system. It's a Scrum Master saying the team needs to stop adding scope mid-sprint. It's a team member admitting they don't understand the requirement instead of pretending. Without courage, the other four C's fall apart. Innovation and real problem-solving only happen when people are willing to speak up.

Continuous Improvement

Continuous improvement is the discipline of getting better. Retrospectives are where this lives. You look at what worked, what didn't, and what you'll change next sprint. It's not about being perfect. It's about being slightly better than last sprint. Over a year, that compounds.

These five principles aren't theoretical. We've seen teams with strong collaboration and communication ship products faster. We've also seen teams skip retrospectives and watch the same problems repeat for months. The five C's work when all five are present. Miss one, and the others weaken.

If you're new to Scrum, understanding these five C's gives you a lens for why certain practices exist. If you're running a team that feels stuck, check which C is missing. Often it's courage or continuous improvement. ThinkLouder's Certified Scrum Master (CSM) course covers how to build these principles into your team's DNA. We've trained over 55,000 practitioners since 2001, and this framework shows up in every strong team we work with. Classes start at $349. For more details, visit our certifications page.

For deeper context on Scrum's structure, see Why Scrum instead of Kanban? or What is a sprint in productivity?