Ever wondered what a Scrum Master actually does all day? Beyond the buzzwords and theoretical frameworks, what does the role really look like in practice? Today, we're diving deep into the daily reality of being a Scrum Master with insights from Ferran, who works within AdventHealth's digital group.
If you're considering a career as a Scrum Master, currently in the role, or simply curious about how Agile teams function in real healthcare organizations, this insider perspective will give you the authentic, unfiltered view you've been looking for.
The Reality of a Scrum Master's Daily Schedule
Morning Routine: Preparation is Everything
Ferran's day starts before the team even logs on. Here's how a typical morning unfolds:
"On a great simple day, I wake up before daily standup. I look at the board, look at notes from the previous day. From there, I write down what I need to talk to the team about to get ready for daily standup, whether it be their blockers or their notes from the previous day."
This preparation phase is crucial and often overlooked. Successful Scrum Masters don't just facilitate meetings—they come prepared with:
- Board analysis: Reviewing sprint progress and identifying potential issues
- Note compilation: Tracking previous day's concerns and follow-ups
- Blocker identification: Spotting impediments before they become critical
- Team member check-ins: Preparing for individual conversations
The Daily Standup and Beyond
While the daily standup is typically a 15-minute meeting, Ferran reveals that the real work often happens afterward:
"Then it turns into takeaways. So one-on-one conversation, what we talked about at daily standup, that could be another 15 to 30 minutes depending on how many people had information."
This post-standup phase includes:
- Individual follow-ups with team members who raised concerns
- Dependency mapping and coordination with other teams
- Board updates and documentation
- Proactive issue identification for mid-sprint problems
Afternoon Activities: The Heavy Lifting
After lunch, the day intensifies with structured activities:
- Agile ceremonies (sprint planning, retrospectives, reviews)
- Product Owner collaboration on roadmapping
- Cross-team coordination meetings
- Strategic planning and escalation to management
"If neither of those happen on a normal day, then I'm usually talking to the PO on road mapping needs from them things that I'm seeing from a scrum master perspective. And if that isn't even happening, then I'm road mapping myself as execution."
Sprint Planning: The Art and Science of Commitment
The Team Development Journey
One of the most insightful aspects of Ferran's experience is how teams evolve in their planning capabilities:
"Any scrum master will talk about like the storming, forming, norming and then performing stages of team development. So within being able to plan your commits, commit and complete it within that two-week iteration is a growing process."
This progression affects how teams:
- Estimate work accurately over time
- Build trust in their collective abilities
- Develop realistic expectations for sprint capacity
- Learn from past iterations to improve future planning
The Planning Process: Where It Really Starts
There's an interesting debate in the Scrum community about when sprint planning actually begins:
"Some people say it doesn't start at sprint planning. Fair, it starts at backlog refinement. So it depends on who you're talking to when does that conversation or plan on your commitment start?"
Ferran prefers the formal approach:
"I like to say it formally starts at planning where you are saying I can finish. I will commit to this for the next two weeks. And backlog refinement is more theory. We're still refining."
The Estimation Debate: What to Point and What Not to Point
A Real-World Policy Change
One fascinating aspect of Ferran's current experience is AdventHealth's decision to stop estimating certain types of work:
"Throughout digital group we will not estimate task bugs okay moving forward... So on my teams we do point task so that'll be something new for me to bring to the team so no more pointing task."
This change highlights several important considerations:
Arguments for not pointing tasks and bugs:
- Difficult to estimate accurately
- Don't directly add customer value
- Time tracking provides actual data instead of estimates
Arguments for pointing everything:
- Maintains visibility into true team capacity
- Prevents undercommitment in sprints
- Acknowledges that all work requires time and effort
The Comparison Trap
This policy change also revealed a common organizational pitfall:
"People would say to me, well Ferran as scrum master, how do you allow your teams to undercommit if they're committing only 30 points?... your team is committing 30 points and other teams... is completing 70 something points."
This scenario perfectly illustrates why comparing teams is problematic in Agile environments. Each team has different:
- Estimation scales and practices
- Types of work and complexity
- Team composition and experience levels
- Definition of what gets pointed
Building Strong Team Foundations
The Power of Working Agreements
"Your working agreement sets your expectation. No one wants to let down the team. No one wants to be that terrible teammate."
Working agreements are crucial for new teams, covering questions like:
- How do we want to work together?
- What makes a good teammate?
- What happens when key people can't attend ceremonies?
- How do we handle conflicts and disagreements?
Ferran emphasizes that these can range from highly detailed to simple principles like "don't do stupid, be a nice person."
The Art of Spike Definition
One area where many teams struggle is defining learning tasks (spikes) properly. Ferran shares a practical example:
"The spike was learn of amplitude... the acceptance criteria was understand what an event understand what an event property is understand how to create tags within our code for amplitude and how to merge it."
This specificity prevents the common problem of developers spending time learning but not gaining the specific knowledge needed for upcoming work.
The Human Side of Scrum Mastery
Recognizing Burnout and Supporting Team Members
Perhaps the most powerful insight from Ferran is about the human element of the role:
"There was a developer he is leveling up in his career. He's been doing amazing things as a developer. And I checked in with him... And he just seemed worn, weathered, and burnt out... And I literally just said, 'Take two days.'"
This example highlights how Scrum Masters must:
- Observe beyond the surface of daily standups
- Make time for genuine check-ins with team members
- Act decisively when team members need support
- Balance project needs with individual well-being
Creative Team Connection Techniques
Ferran uses innovative approaches to keep teams connected:
"Today tell me what is your idea of paradise? So I say while you're giving me your update of yesterday, today and blockers, give me a couple lines of what is to you a paradise."
This technique serves multiple purposes:
- Provides mental breaks during routine meetings
- Builds personal connections between team members
- Offers insights into individual team member states
- Creates opportunities for natural check-ins
The Mindset of an Effective Scrum Master
Embracing the Support Role
Perhaps the most profound insight about being a Scrum Master comes from Ferran's reflection on recognition:
"You are the cheerleader that no one sees. You are the writing champion that no one sees. You get none of the glory. You're a sidekick... In true agile, you and the product owner are counterparts. You guys are equal and opposites."
This requires a specific mindset:
- Comfort with behind-the-scenes influence
- Satisfaction from team success rather than personal recognition
- Understanding of the complementary relationship with Product Owners
- Focus on enabling others rather than being the star
"What makes a good scrum master is someone who does not need to be the light. They do not need to be the sun but they know they add value to their team."
Task Switching: The Reality of Interruptions
One authentic moment in the conversation perfectly captured daily reality:
"We get phone call, we jump into the call, we finish that call, we come back and we continue. Task switching at its finest... that's life as a scrum master, right?"
This constant availability and context switching is part of the role, requiring:
- Flexibility in daily planning
- Strong organizational skills to track multiple conversations
- Patience with interrupted workflows
- Skill in quickly re-engaging with previous tasks
Key Takeaways for Aspiring and Current Scrum Masters
Essential Skills to Develop
- Preparation and organization: Success starts before meetings begin
- Active observation: Look beyond what people say to what they need
- Facilitation skills: Guide conversations toward productive outcomes
- Emotional intelligence: Recognize when team members need support
- Advocacy abilities: Represent team needs to management and other stakeholders
Daily Habits That Make a Difference
- Start each day with board analysis and note review
- Schedule buffer time for spontaneous team needs
- Create opportunities for human connection within routine meetings
- Document insights and decisions for future reference
- End each day with reflection and preparation for tomorrow
Mindset Shifts for Success
- Embrace the support role rather than seeking spotlight
- Focus on team empowerment over personal recognition
- View interruptions as opportunities to add value
- Prioritize people over processes while maintaining structure
- Think systemically about team dynamics and organizational impact
Conclusion: The Real Impact of Scrum Masters
Ferran's insights reveal that being a Scrum Master is far more nuanced and human-centered than many job descriptions suggest. It's about creating the conditions for team success through careful preparation, genuine care for individuals, and the wisdom to know when to step in and when to step back.
The role requires a unique combination of organizational skills, emotional intelligence, and humble leadership. While Scrum Masters may not always get the glory, their impact on team effectiveness, individual growth, and organizational success is immeasurable.
For those considering this career path, ask yourself: Are you energized by enabling others' success? Do you find satisfaction in solving problems behind the scenes? Can you maintain focus on people while managing processes? If so, the Scrum Master role might be your perfect fit.
The Agile transformation happening in organizations like AdventHealth needs skilled practitioners who understand that methodology is just the beginning—the real magic happens in the daily interactions, careful observations, and human connections that make great teams possible.
Watch the Full Episode
Listen to the full episode for more insights from this conversation.
