From Theory to Practice: How Scrum helps in solving real-world problems
From motivation to a mindset shift
Why I Pursued the Scrum Master Certification
Like many professionals in client-facing or cross-functional roles, I’ve often found myself at the centre of complex projects: juggling timelines, aligning stakeholders, and trying to deliver value in fast-changing environments.
But while I could intuitively manage those challenges, I sometimes felt like I lacked a shared language or framework to bring structure to the chaos.
That’s what initially drew me to the Scrum Master certification by Scrum Alliance. I was intrigued by how software teams handled complexity with clarity, velocity, and continuous improvement. I wanted to learn how to apply those principles to non-technical settings, particularly in project implementation, business operations, product rollouts, and stakeholder engagement.
My Takeaways from the Scrum Master Course
Beyond the Definitions
The course and certification didn’t just teach me processes and terminologies, it gave me a new lens for looking at problems at work and in life in general (upcoming article on this).
I learned that Scrum is not a rigid process, but a flexible, lightweight framework designed to solve complex problems and deliver value in uncertain environments, a core challenge for any fast-moving organisation.
Instead of rote rules, Scrum is grounded in two key pillars:
🔍 Empiricism
Make decisions based on what you observe, not assumptions.
- Create transparency around work
- Constantly inspect progress
- Be ready to adapt based on what’s learned
⚡ Lean Thinking
Reduce waste and focus on essentials to deliver value.
- Build the right things at the right time
- Ensure every effort directly contributes to delivering value to the user/ customer
Where Agile provides the why and what (values like customer collaboration and responding to change), Scrum provides the concrete how — a structured way to turn philosophy into tangible results.
The Scrum Mindset: More Than a Framework
My most significant takeaway was realising that Scrum is a mindset for leadership, collaboration, and delivering value.
While the Scrum Master role is distinct from that of a project or product manager, its principles are a blueprint for strategic execution, product management, and high-performing teams.
I now approach my work through the lens of a strategic enabler: fostering a culture of excellence, driving alignment, and championing continuous improvement.
Principles I’ve Adopted from Scrum
- Fostering a culture of ownership: Coaching teams in self‑management and cross‑functionality to encourage responsibility for outcomes.
- Optimising team performance: Making every planning, review, or retrospective purposeful, time‑bound, and an opportunity for inspection and adaptation.
- Ensuring focus and value delivery: Prioritising high‑value deliverables and meeting the Definition of Done consistently.
- Facilitating effective change: Removing impediments, breaking down silos, and aligning stakeholders towards shared goals.
The Mindset Shift
🔁 Iteration over perfection
Progress isn’t about launching the perfect solution. It’s about learning quickly, adjusting fast, and always delivering value.
🔍 Inspect and adapt
The best teams build in feedback loops, for both the users and internal stakeholders through retrospectives, metrics, and open dialogue.
👩🏻🏫 We all need a coach
Scrum Masters, mentors, or trusted peers offer what we often can’t give ourselves because when we’re doing, we’re not observing:
- Perspective: See yourself the way others do: clearly and constructively.
- Awareness: Identify patterns, blind spots, or normalised habits.
- Breakdowns that build you up: Deconstruct decisions, then rebuild stronger by asking better questions instead of having all the answers from the get go.
Applying Scrum in Real Life
Even in environments that don’t formally use Scrum, I’ve seen how agile principles help teams move with clarity, adapt to change, and focus on delivering value.
Get Yūgen-Iki’s stories in your inbox
Join Medium for free to get updates from this writer.
I’m now more intentional about:
- Creating alignment upfront
- Building trust and transparency within teams
- Prioritising iteration over perfection
Case Study: Commercial × Product Prioritisation Framework
The Challenge
I led the development of a framework to align commercial revenue goals with technical delivery capacity. The roadmap was already full, but urgent, high‑value projects still needed to be slotted in.
Without a structured process, decisions were made ad hoc, leading to misalignment, delays, and missed opportunities.
What Happened
We launched the framework, but the creation process lacked structure. There was no central intake process, feedback was fragmented, and urgent requests disrupted ongoing work.
How Scrum Could Have Helped
1️⃣ Problem Definition & Prioritisation
- Begin by defining the core problems to solve first (e.g., lack of intake process, unclear prioritisation criteria) before attempting a full solution.
- Identify the inputs required from each team e.g., Sales for revenue projections, Product for technical feasibility, Engineering for capacity timelines.
- Agree on the sequencing of deliverables so we knew which elements of the framework needed to be resolved first.
2️⃣ Product Backlog Refinement
A Scrum Master could facilitate recurring backlog refinement sessions with Sales, Commercial, Product, and Engineering to define potential framework components, prioritise them by value and readiness, and ensure all stakeholders had a shared understanding.
3️⃣ Sprint Planning & Milestones
- Sprint 1: Build the scoring model for revenue potential, client readiness, and technical effort.
- Sprint 2: Design the intake form and routing process for new client requests.
- Sprint 3: Develop the RACI plan to clarify decision-making and escalation points.
- Each sprint would end with a review to present progress, gather feedback, and adjust plans before the next stage.
4️⃣ Sprint Reviews
Present progress to senior leadership and regional stakeholders for input, ensuring the framework was scalable across markets.
5️⃣ Retrospectives
Gather continuous feedback on adoption challenges (e.g., request intake complexity, scoring clarity) and iterate quickly to improve usability and buy-in.
💡 Value‑Add
By applying Scrum, we could have:
- Brought clarity and focus by resolving the most pressing issues first.
- Improved cross-functional collaboration with structured feedback loops.
- Increased transparency on prioritisation logic and pipeline status.
- Reduced rework by validating each stage before scaling.
- Created a flexible, scalable framework aligned with evolving business needs, ultimately accelerating delivery and protecting revenue opportunities.
Moving Forward: My Growth Plan
Writing this article has made me more intentional in how I show up at work:
- Ask for feedback to continue growing.
- Offer observations that are supportive > directive.
- Hold space for reflection, because growth requires a pause.
I now see business challenges less as isolated puzzles, and more as systems to evolve through iteration, feedback, and alignment.
My next steps:
- Continue developing as a strategic, cross‑functional, agile‑minded leader by driving change enablement, leading projects that help teams successfully adopt new tools, processes, and strategies.
- Facilitate more structured retrospectives in my current role.
- Sharpen my skills in data‑driven decision making and stakeholder storytelling.
✨ In a world moving faster than ever, agility and scrum isn’t just a concept and methodology — it’s a mindset that might be our biggest asset.
