UNITED WAY STL ACADEMY
  • Courses
  • Log In
  • Join Free
  • Home
  • Courses
  • Scrum Essentials

Scrum Product Development

Curriculum

  • 5 Sections
  • 25 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Planning Your Work
    4
    • 1.1
      The Product Roadmap
      10 mins
    • 1.2
      Breaking Down Requirements
      10 mins
    • 1.3
      Your Product Backlog
      10 mins
    • 1.4
      Product Backlog Common Practices
      10 mins
  • The Talent and the Timing
    4
    • 2.1
      The Developers
      10 mins
    • 2.2
      Getting the Edge on Backlog Estimation
      10 mins
    • 2.3
      Your Definition of Done
      10 mins
    • 2.4
      Common Practices for Estimating
      10 mins
  • Release and Sprint Planning
    5
    • 3.1
      Lean Startup
      10 mins
    • 3.2
      Release Plan Basics
      10 mins
    • 3.3
      Sprinting to Your Goals
      10 mins
    • 3.4
      Planning Your Sprints
      10 mins
    • 3.5
      Your Sprint Backlog
      10 mins
  • Getting the Most Out of Sprints
    4
    • 4.1
      The Daily Scrum
      10 mins
    • 4.2
      Team Task Board
      10 mins
    • 4.3
      The Sprint Review
      10 mins
    • 4.4
      The Sprint Retrospective
      10 mins
  • Inspect and Adapt: How to Correct Your Course
    8
    • 5.1
      Need for Certainty
      10 mins
    • 5.2
      The Feedback Loop
      10 mins
    • 5.3
      Transparency
      10 mins
    • 5.4
      Antipatterns
      10 mins
    • 5.5
      External Forces
      10 mins
    • 5.6
      In-Flight Course Correction
      10 mins
    • 5.7
      Testing in the Feedback Loop
      10 mins
    • 5.8
      Culture of Innovation
      10 mins

The Developers

Scrum Product Development

The Developers

🕐 12 min read
The Big Question

What makes a Scrum developer different from traditional team members—and why is cross-functionality so crucial for high-performing teams?

In many creative fields, the people who bring ideas to life are called the talent. In Scrum, developers hold that role—building, refining, and delivering the product that everyone relies on. But what does it really mean to be a Scrum developer?

💡 Did You Know?

The term “cross-functional” doesn’t mean everyone can do everything on day one—instead, it’s a journey of learning and sharing skills within the team.

Developers are at the heart of the Scrum process. They’re responsible for creating and developing the actual product, deciding how to build requirements and how much can be done in a sprint. A Scrum team’s success relies on these developers being dedicated to one goal at a time, working cross-functionally, and organizing themselves without a manager’s direct oversight.

Team size matters: Scrum teams usually have no more than ten people—a product owner, a Scrum master, and up to eight developers. Five or six developers are often ideal, keeping communication manageable and the team nimble. For each new member, communication lines multiply, making it harder to self-organize. Unlike traditional project management models, Scrum teams avoid the overhead of a project manager by keeping teams small and communication direct.

Technical Stuff icon
TECHNICAL STUFF

Self-organizing means the team decides how to do the work and who does it. Self-managing means the team is accountable for delivering the product through peer collaboration—without outside management guidance.

The uniqueness of Scrum developers

Scrum developers are empowered to develop new skills, set goals, and own their development process. They operate differently from traditional teams—taking credit as a team and taking full responsibility for results. Each developer is expected to be versatile, curious, and eager to share knowledge, creating an environment where teamwork and peer accountability drive performance every day.

In practice, high-performing Scrum teams grow their cross-functionality over time—often starting with specialists and gradually building broader skill sets to eliminate bottlenecks.

Dedicated teams and cross-functionality

Developers in Scrum focus on one product goal at a time. Context switching—also called thrashing—is discouraged, as it slows progress and dilutes focus. Whether functional management selects team members or not, a diversity of skills is essential so the team can be as self-sufficient as possible.

When a key developer on a traditional team takes a vacation, projects often stall. But in a cross-functional Scrum team, someone else can step in and keep the sprint moving forward—minimizing costly delays.

CREATING A MOTIVATING ENVIRONMENT

Daniel Pink writes about motivation in his excellent book Drive: The Surprising Truth About What Motivates Us (Riverhead Books). Here, Pink dispels the myth that the way to motivate people is through more and more money. Surprisingly, Pink found that the higher the monetary incentive, the worse the results. Money is a factor, but only enough to take the subject of money off the table.

As he continued to dig, Pink found three specific factors that produced the environment for the best-quality results, whether at home or work: autonomy, mastery, and purpose. Let your people determine how they will do their work, give them the space and time to master current and new skills, and communicate a sense of purpose in what they’re doing.

The scrum framework can enable the environment that Pink discusses. The scrum team is designed to be self-managing and autonomous with regard to how it does the work. Cross-functionality and developing new skills are fundamental. Developers understand what they’re working on (and why) through the product goal and direct communication with the product owner and stakeholders.

Remember icon
REMEMBER

People don’t necessarily start out being cross-functional; they grow into this state. Start with a team of diverse talents and then organically build that team toward being individually cross-functional.

Schematic illustration of developer skill progression.
Figure 4-1: Developer skill progression shows how individual skill sets expand over time, becoming more T-, Pi-, or M-shaped.

Whatever your business or organization, one fact remains: People will sometimes be unavailable. Building cross-functionality means your team can adapt to changes and prevent bottlenecks—if one person is out, another can step in to keep the work moving.

  • It allows product owners to prioritize according to business value, not just technical skills.
  • It encourages diverse input on optimal solutions.
  • It enables pair development for higher quality.
  • It helps team members grow by learning associative skills.
Want to go deeper? The science behind motivation in Scrum teams

Daniel Pink’s research highlights the importance of autonomy, mastery, and purpose for motivation. Scrum is designed to provide all three: autonomy through self-management, mastery through ongoing skill development and cross-functionality, and purpose via clear product goals and regular communication with stakeholders. This structure fosters engagement and sustained high performance.

⏱ 5 minutes
Activity: Map Your Team’s Skills

Assess your team’s cross-functionality and identify opportunities for growth.

  1. List each team member and their primary skills.
  2. Identify which skills are covered by more than one person—and which are single points of failure.
  3. Discuss as a team: What skills could each person learn next to reduce bottlenecks?

How does your current team handle unexpected absences or shifting priorities?

In what ways might focusing on cross-functionality improve your personal growth as a developer?

Reflect on a time when your team succeeded or struggled due to gaps in cross-functional skills. What did you learn from that experience, and how could you apply that lesson to your work in a Scrum environment?

0 words Take your time — depth matters more than length
Self-Organizing

A Scrum team trait where members collectively decide how to accomplish their work and who does which tasks—without a manager assigning roles or tasks.

Cross-Functionality

The ability of a team to cover all skills needed for product delivery, with each member capable of contributing in multiple areas, reducing bottlenecks and single points of failure.

❌ Common Misconception

Only project managers can coordinate and drive team performance; developers need direct management to stay on track.

✅ The Reality

Scrum teams are designed to be self-managing—developers collaborate directly and share responsibility for performance, quality, and delivery.

Flashcard

What is a self-managing Scrum team?

Tap to reveal
Answer

A team that takes full responsibility for delivering a product through peer collaboration, rather than relying on a manager for guidance.

Flashcard

What does cross-functional mean in a Scrum context?

Tap to reveal
Answer

It means the team has all the skills necessary to deliver the product and each member can contribute in multiple roles or skill areas.

Flashcard

What is team thrashing?

Tap to reveal
Answer

Thrashing is when developers are forced to switch between competing goals, which reduces focus and team productivity.

What steps could you or your team take to eliminate single points of failure and improve resilience?

Retaining that talent is one of the byproducts of good scrum.

  • Scrum developers own the how and how much of product work.
  • Self-management and cross-functional growth are essential for resilient teams.
Key Takeaway

Scrum developers thrive in self-managing, cross-functional teams where autonomy, mastery, and purpose drive collaboration and quality.

Key Takeaway

Building cross-functional skills is a process that transforms teams from collections of specialists into resilient, adaptable units capable of handling change and delivering value.

+50 XP

What is the optimal number of developers on a Scrum team for most situations?

Review the section on Scrum team size above to find the answer.

How might you contribute to creating a more cross-functional and self-managing team in your organization?

0 words
SHIFT

The Shift

  • Scrum developers are responsible for driving product creation through teamwork, autonomy, and shared ownership.
  • Optimal Scrum teams are small, cross-functional, and self-managing, enabling adaptability and reducing communication overhead.
  • Building cross-functional skills is a journey that empowers teams to handle change, avoid bottlenecks, and deliver high-quality results consistently.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

Product Backlog Common Practices
Prev
Getting the Edge on Backlog Estimation
Next

© 2026 United Way STL Academy | Powered by Sejal Learning Systems.

Modal title

Main Content