Ken Schwaber

Lessons from Past Project Managers: Ken Schwaber

Picture of Claudio Gutierrez

Claudio Gutierrez

President & Founder — Valens Project Consulting

Facebook
Twitter
LinkedIn
Email

In the world of project management, few figures have had as transformative an impact as Ken Schwaber. As one of the co-creators of Scrum, Schwaber helped pioneer the Agile movement—a shift that has fundamentally redefined how teams manage work, deliver value, and respond to change.

 

For decades, project management was driven by rigid plans, detailed Gantt charts, and top-down control. But software development—and later, many other industries—needed something more adaptive. Schwaber’s work brought that change. He didn’t just give us a framework; he gave us a new mindset.

 

The Birth of Scrum

In the mid-1990s, Schwaber partnered with Jeff Sutherland to formalize Scrum, drawing inspiration from lean manufacturing, systems thinking, and empirical process control. Presented at the OOPSLA conference in 1995, Scrum introduced a lightweight framework built on transparency, inspection, and adaptation—a radical contrast to traditional waterfall project methods.

 

For project managers, Scrum was a game changer. It shifted focus from managing tasks to facilitating outcomes, from upfront planning to incremental delivery, and from command-and-control leadership to team

empowerment.

Core Contributions to Project Management

Ken Schwaber’s impact on project management can be summed up in a few transformative principles:

Iterative and Incremental Delivery

Schwaber emphasized short, time-boxed iterations called sprints, each producing a potentially shippable product increment. This approach minimizes risk, surfaces issues early, and allows teams to deliver value continuously—not just at the end of a project.

 

For project managers, this means managing by cadence, not just by milestones. It encourages frequent reassessment of priorities and fosters a culture of learning and adaptability.

 

Self-Organizing Teams

Scrum’s success hinges on the belief that teams closest to the work are best positioned to make decisions. Schwaber advocated for self-managing teams that take ownership of their goals, collaborate cross-functionally, and continuously improve their process.

 

This challenged traditional project management structures. Instead of directing every move, the modern project leader becomes a servant leader—removing roadblocks, facilitating communication, and trusting the team to deliver.

 

Empirical Process Control

Schwaber introduced empiricism as a foundation for Agile project management. With transparency, inspection, and adaptation at its core, Scrum encourages teams to base decisions on observed reality rather than assumptions or long-range predictions.

 

This philosophy allows project managers to pivot early and often, responding to customer feedback, technical challenges, and changing priorities with agility and confidence.

 

Founding the Scrum Alliance and Scrum.org

To scale the adoption of Scrum and preserve its principles, Schwaber co-founded the Scrum Alliance in 2001 and later Scrum.org in 2009. Through these organizations, he championed consistent training, professional certification (like the Certified Scrum Master and Professional Scrum Master), and a strong emphasis on Agile values.

 

These efforts helped integrate Scrum into thousands of organizations around the world—not just in tech, but in marketing, operations, HR, and even government.

 

A Vision for Ethical Project Management

What sets Schwaber apart is his commitment to the human side of work. He has consistently emphasized transparency, accountability, and continuous learning—not just as Agile principles, but as values that create better workplaces and more sustainable results.

 

In his later writings, Schwaber warned against “fake Agile”—organizations that adopt Agile terminology without embracing its deeper mindset. He urged leaders to support cultural transformation, not just process change.

 

For project managers, this is a crucial insight: Agile isn’t a toolkit—it’s a philosophy. It requires trust, humility, and a willingness to learn and adapt alongside your team.

 

Final Thoughts

Ken Schwaber helped reimagine what project management could be. He moved the field from predict-and-control to inspect-and-adapt, from planning-heavy roadmaps to fast feedback loops, and from task delegation to team empowerment.

 

Today, in a world where speed, flexibility, and innovation are essential, Schwaber’s contributions continue to guide how we deliver value, lead teams, and shape the future of work.

 

Agility isn’t just a method—it’s a mindset. And thanks to Ken Schwaber, that mindset has transformed project management for good.

 

Remember to follow us on LinkedIn for the latest project management insights and updates.

 

Leave a comment

Your email address will not be published. Required fields are marked *