As a leader with a background in science, Nathan is wired to evaluate every variable. He looks for solutions, weighs trade-offs, tests hypotheses, and scrutinizes ideas from every angle. While this analytical rigor is a strength, Nathan notes the potential for a bottleneck:
"If you can see the pros and cons of every decision," Nathan explains, "it can lead to analysis paralysis."
Seeking a way to move from deliberation to delivery and help his team supercharge their management of complex work, Nathan enrolled in the Certified ScrumMaster® (CSM®) course. He wanted a structured, data-backed framework to help his team navigate the unknown.
The turning point: evidence over intuition
For Nathan, the shift wasn't just about learning scrum events; it was about changing how leadership is practiced. He realized that the most effective way to lead a team through complexity is to move away from "top-down" ideas and toward shared evidence.
"It's not good enough to say, 'Here's my idea—let's implement it,'" Nathan said. "It's better to introduce an evidence-based approach."
Applying structure to the "Swiss Army knife" team
As a software engineer and technical lead, Nathan heads a versatile team of seven engineers. They are the company's "Swiss Army knife," often deployed to tackle the most specialized, undefined projects.
The CSM course provided Nathan with the tools to answer three questions:
- Decision-making: How do we ensure we are making the right choices when the path isn't clear?
- Continuous improvement: How do I empower my team to evolve their own processes?
- Workflow: How do we wrap structure around unstructured work to improve efficiency and results?
Through the CSM's hands-on learning and practical instruction, Nathan found a way to turn his scientific mindset into a functional engine for team agility, ensuring that even the most complex work is met with a clear, disciplined flow.
A better way to figure out what works
Nathan and his team were already collaborative, adaptable, and providing outstanding value to their organization. But for someone with a scientific mindset, Nathan wanted a clear way to evaluate and improve how well the team was working together to deliver value and results.
He and his team were already using scrum, and he wanted to take a deeper dive into the framework to help his team fine-tune the value they could derive from it.
What clicked wasn't just the structure. It was what the structure enabled.
Scrum creates a system for learning.
Through feedback loops, transparency, and regular inspection and adaptation, teams can see what's actually happening—not what they assume is happening—and adjust accordingly.
Nathan solidified his understanding of the scrum events, artifacts, and accountabilities, and got tips and information he could immediately bring back to his team.
"I've made a lot of changes within my team after the CSM course, and it's been going great so far! Leadership and other teams have actually seen the changes I've been implementing, and they are now asking for my input for company-wide process changes and they are wanting all of our POs to get a CSPO."
– Nathan B., CSM Student
Clarity that scales across teams
While not strictly part of the scrum framework, the Definition of Done (DoD) and acceptance criteria covered in the CSM class were what Nathan needed to bridge the gap between abstract goals and finished products. These tools empower a team to self-manage with total transparency.
To illustrate how easily teams misinterpret goals, Nathan's instructor posed a simple question: "When is the laundry done?"
The answers varied:
- Clean and dry
- Clean, dry, and folded
- Clean, dry, folded, and put away
This simple exercise revealed a profound truth: without a shared standard, "done" varies depending on who you ask and their relationship toward the work being completed. Stakeholders have differing views of "what's at stake?" based on their role and interest in a project.. For a software team, this ambiguity leads to technical debt and missed expectations.
Through the course, Nathan learned to distinguish between two critical guardrails that keep a team on track:
- Acceptance criteria: These help the team ensure they are building the right thing. They are specific to a single task or feature, defining the unique requirements for that piece of work.
- Definition of Done: This ensures the team is building the thing right. It serves as the universal quality standard—such as code reviews and defect resolution—that applies to all work across the board.
"It's helped fix our planning; we're not thinking about all of these trivial things that should just be a given. If we're doing a certain research story, we can say our Definition of Done for this research should meet our agreed criteria, here's what should come out of it, and here's how we talk about it as a team, versus having to have that discussion every single time we come up with research."
By codifying these standards, Nathan has freed his team from the friction of the "obvious," allowing them to focus their mental energy on what they do best: solving complex problems.
Using data to improve continuously
For Nathan, the real power of scrum shows up after the work is done.
That's where the data lives.
He and his team actively use sprint data to understand how they're working and how they can improve.
They ask:
- Did our forecast reflect reality?
- Where did work carry over, and why?
- Are our stories sized in a way that supports steady progress?
In one sprint, their burndown chart revealed a pattern: work stayed high throughout the sprint, then dropped sharply at the end.
The takeaway? Their stories might be too large.
So they adjusted.
That's how their high-performing team has always operated: not by guessing, but by experimenting and learning in real time. The scrum framework and Nathan's CSM insights provided further structure for improving through experimentation and data.
Even their approach to measuring progress reflects that mindset. They focus on completed work—not partial effort—so they can get a clearer picture of actual throughput and continuously refine how they plan.
Seeing problems sooner, so you can solve them
Nathan knows that scrum isn't there to fix everything. It actually makes problems visible—faster. It surfaces inefficiencies and bottlenecks through transparency, inspection, and adaptation.
"Scrum helps identify those problems quickly," he says. "It helps us clearly see them the more that we do it."
And that visibility is what enables real progress.
Because once you can see the problem, you can address it, one improvement at a time.
Leading through enablement
Nathan's role spans technical leadership, scrum facilitation, and collaboration with product teams.
Scrum helps him refine how he shows up in that role by leaning into servant leadership:
- Coaching team members as they grow
- Removing blockers
- Creating space for the team to solve problems together
He has further refined his facilitation approach, intentionally guiding conversations to ensure he steps back and that the team is able to contribute even more fully.
Even practices like timeboxing have become tools for alignment; not constraints, but ways to ensure the team invests time where it matters most.
What's next: continuous improvement with data
Nathan isn't finished refining his approach.
He's planning to pursue the Advanced Certified ScrumMaster (A-CSM), with a clear focus: leveraging sprint data to improve how his team works.
He's especially interested in:
- Predicting future work based on past performance
- Improving consistency in estimation
- Understanding how to handle work that carries across sprints
Because for Nathan, the goal isn't to follow a framework perfectly but to use it as a system for continuous improvement.
A smarter way to work
Nathan doesn't utilize scrum practices to change things overnight or because a prescribed set of steps is guaranteed to work. Scrum provides a data and evidence-based way to figure out what works.
In complex environments, there are no perfect answers. There are only better questions, better signals, and better ways to adapt.
Scrum gave Nathan and his team a way to see those signals clearly and act on them.
And that's what's turning their work into something more than delivery. It's turning it into continuous improvement.
Your next step
Nathan's story isn't unique because of where he started. It's powerful because of the shift he chose to make.
Agility isn't a framework—it's a way of thinking that helps individuals and organizations adapt, improve, and deliver meaningful value.
If you're ready to grow your leadership, sharpen your skills, and lead teams through complexity, the next step is yours to take.
Explore training, connect with a global community, and start building the kind of impact Nathan did.
About the author
We’re committed to equipping professionals and their organizations with the education, skills, and community needed to succeed in today’s ever-evolving workplaces.