How organizations view and develop their people dramatically shapes their ability to adapt, innovate, and thrive in a Scrum environment. Human Resources is no longer just about policies—it’s about unleashing talent and empowering leaders at all levels.
The phrase “human capital” became popular in the 1960s, but today, many HR experts advocate for language that recognizes people’s intrinsic value—emphasizing “talent” and “people” over “resources.”
In a survey conducted by the Society for Human Resource Management (SHRM), two core challenges highlight the world of HR today: retaining and rewarding the best employees and developing future leaders. These two concerns are really the same thing. Your best employees often become your future leaders.
When the surveyors asked organizations about their largest investment challenge, the number-one response was “obtaining human capital and optimizing human capital investments.”
We always encourage the organizations we work with to refer to people as people or talent rather than capital and resources. People aren’t commodities. They have individual skills, experiences, and innovations. The term resources, used to refer to people, is a relic. Start seeing your people as people, and see their creativity and talents as the irreplaceable value they bring to your organization.
How might shifting your language from “resources” to “talent” change the way your team feels about their work and contributions?
That said, the point made by the SHRM survey is still crucial. Different types of leaders are needed. We need leaders to make the hard product owner decisions discussed in portfolio management. We need servant leaders who work collaboratively to enable and empower teams, such as scrum masters. These people empower and enable self-organizing teams to come up with the best solutions. They value iterative approaches to building products based on rapid and regular customer feedback and know how to pivot and respond to that feedback quickly.
In many agile organizations, the most successful leaders focus less on giving orders and more on removing obstacles so teams can thrive. This shift in leadership style is at the heart of Scrum’s effectiveness.
Want to go deeper? The science behind servant leadership
Research shows that servant leaders—those who prioritize the growth and well-being of team members—help foster trust, psychological safety, and innovation. Scrum masters often embody this style, creating environments where diverse skills and perspectives are encouraged to flourish.
Recall a time when a leader empowered you or your team. What impact did their approach have on your motivation and performance?
Historically, technology companies have rewarded leaders who managed crises well. In turn, these leaders promoted others who managed crises with a sense of urgency. Although these firefighters certainly saved the day more than once, we argue that this situation caused an unbalanced shift toward crisis resolution rather than crisis avoidance.
The best leaders are those who excel at putting out fires and handling emergencies as they arise.
Organizations thrive when leaders focus on preventing crises—and mentoring teams to solve challenges before they escalate.
Some leading companies now recognize and reward leaders who build resilient, cross-functional teams that anticipate and prevent issues, rather than just those who react quickly when things go wrong.
What are some ways your team could shift from crisis management to crisis prevention in your current projects?
We need leaders in development who excel by learning new skills and mentoring others as they grow. We need collaborative leaders who can work in the dynamic environment of scrum. We need people who value complementary leadership styles. Egomaniacs need not apply. Companies need cross-functional swarming scrum teams to stay competitive. In other words, we need leaders who embrace the value of change.
A leadership philosophy where the main goal is to serve the team—empowering, enabling, and supporting people to reach their full potential.
A group composed of members with different expertise working toward a common goal, enabling rapid problem-solving and adaptability.
Think about recent leaders you’ve worked with. Which of their habits align with a servant leadership approach? Which do not?
- List three actions a recent manager or team lead took that empowered their team.
- Identify two actions that may have limited collaboration or innovation.
- Reflect on how these behaviors affected the team’s performance.
Reducing risky single points of failure saves money for all the reasons we’ve discussed so far. Teams that collaborate to solve a problem get quality products to market faster than teams that use traditional methods.
Journaling Challenge: Think about your current or past team. How can your team reduce single points of failure and foster a more collaborative, adaptable environment? What steps could you personally take to support this shift?
- Recognized why HR is central to Scrum and business agility.
- Explored the impact of different leadership styles on team performance and innovation.
Your best employees often become your future leaders.
Empowering people as unique talents—not mere resources—creates stronger teams, better leaders, and faster innovation in a Scrum environment.
The most valuable leaders in Scrum aren’t crisis managers—they’re mentors who foster collaboration, continuous learning, and adaptability.
Which leadership approach is most aligned with the Scrum framework?
What is “servant leadership” in the context of Scrum?
Tap to revealA leadership style focused on serving and enabling team members, helping them grow and succeed together.
What is a single point of failure, and why is it risky?
Tap to revealIt’s when a process or system relies on one person or component—if that fails, the whole system is at risk; Scrum teams reduce this by sharing knowledge and responsibility.
Why does Scrum value cross-functional teams?
Tap to revealThey bring together diverse skills and perspectives, allowing for faster problem-solving and adaptability in complex projects.