• Home
  • Training
  • Coaching
  • Tool Box
    • Tools
    • Working Remote Resources
  • Events
    • Webinars
  • About
    • Join Our Team
  • Contact
    • 317 (983-2459)
  • Log in

June 11, 2019 by Beth McDonough 1 Comment

What Are a Scrum Master’s Roles and Responsibilities?

Three primary roles exist within the Agile realm of Scrum: Product Owner, Scrum Master, and the Team. According to Agile’s core foundations, the Scrum Master is meant to facilitate rather than dictate, focusing on empowering teams to be autonomous and to self-organize. Scrum Masters should encourage team members to endorse an Agile mindset, prioritizing individuals and interactions over processes and tools to create a powerful, iterative environment.

Let’s drive some clarity on what this means and break down the roles and responsibilities for this team-based servant leader.

A Scrum Master should:

Maintain the pulse of Team dynamics.

When a group of people works on a project, a storm of different styles and personalities interacting together can lead to varying or unhealthy Team dynamics. The job of the Scrum Master is to keep tabs on the health of these dynamics and jump in to facilitate conflict resolution and opportunities for growth where necessary. Scrum Masters don’t force change, they empower individuals to do their best work to help build a high-performing Team.

Remove obscuring obstacles from the path.

In order to make it to the finish line of a sprint goal, distractions need to be blocked and impediments alleviated to avoid stumbles along the way. It’s the Scrum Master’s responsibility to remove these roadblocks and maintain a focused path for Team members to reach their goals. Setting up the Team for success is a pivotal responsibility of the Scrum Master, and sometimes that can mean simply clearing the way for individuals to do what they do best.

Facilitate the flow of work within the team.

The Scrum Master’s primary role is to be a facilitator. Part of this general facilitation includes leading Team meetings, establishing clear goals, and assisting the efforts of both the Product Owner and the individual members of the Team. In assisting the Product Owner, the Scrum Master can help prioritize workload backlogs and manage project scopes to better align with the desired results and definition of the value of the current project. By challenging outdated processes, utilizing feedback from the team, and keeping best practices relevant, the Scrum Master enhances performance and flow for the team.

Scrum Master's Roles

Protect each team and their work from external distractions.

Scrum Masters should act as representatives of their Team in Scrum of Scrums (SoS) meetings and other executive discussions. The Scrum Master collects and communicates information between Teams, and between upper-management and the Team. This coordination with outside parties creates a protective barrier which allows members of the Team to focus on their work and the project at hand without the concern of impending distractions that may cause delays or task expansion.

Coach team members on self-management.

A Scrum Master doesn’t exist to be “the boss”. Their goal should be to foster individual ownership and personal responsibility within each of their Team members. Accomplishing this might involve teaching specific techniques to the Team for problem-solving while equipping them with the capabilities and confidence to tackle and resolve issues themselves. Self-discipline is a pillar of Agile, and the Scrum Master exists to implement these values and practices.

To learn more about this role and how to empower your organization’s growth within Agile, sign up for a Scrum Master course or contact the team at beLithe for information.

 

Filed Under: Blog, Scrum Tagged With: agile, Agile Culture, certified scrum master, scrum

May 12, 2016 by Chris Daily Leave a Comment

Culture Eats Agile for Breakfast at Agile Cincinnati

beLithe’s Culture Roadshow Series

We’re on the road sharing our passion for how culture can truly change (and save) businesses.  Culture is the missing link in many agile transformations and our goal is to educate our agile friends so they don’t make the same mistakes we did. Come see us if we’re in a town near you, we would love to meet you!

Title: Agile Eats Culture for Breakfast

Group:  Agile Cincinnati

Topic: VersionOne’s 9th Annual State of Agile Survey found that the number one barrier to further agile adoption is lack of ability to change organizational culture. Workplace culture is often an afterthought in agile transformations but is critical to making it work and making it stick.

Presenter walks the audience through experiences and lessons learned while transforming the culture in one for-profit and one non-profit organization to an agile, highly engaged (and fun!) workplace. Audience members will learn how to approach managing the complexities of cultural transformations by employing agile methodologies (specifically the Scrum framework) and Lean Startup principles. Lessons learned can be employed immediately in any work environment.

Speaker: Tana Linback’s background directing human resource and operational functions while developing company-wide people strategies provided a strong foundation in workplace cultural development before shifting her focus to software and product development. Tana has experience leading successful cultural transformations in agile environments and implementing Scrum in non-software development business functions. Tana has a BA in Corporate Communications from Purdue University and is a Professional Scrum Product Owner.

 

Tagged With: agile, Agile Cincinnati, Agile Cincy, Agile Culture, culture

May 1, 2016 by Chris Daily Leave a Comment

Culture Work: The Fine Line Between Cheese and Charm

mmag

Last week I got the opportunity to talk culture at the Mid-Michigan Agile Group’s monthly meeting organized by Joe Hershey.  I always look forward to talking about culture in agile environments and getting to watch all the light bulbs light up one by one in the audience as folks relate to the experiences I share during my presentation.  The best part of the presentation is always the very end when I open up the floor for comments and Q&A.  I love hearing about other’s experiences and thoughts on culture and engagement.

One of the questions I received really stuck with me.

Professional Tester Jeff MacBane (@JMacBane) asked…. “How do you prevent the work the team is doing on culture from being cheesy?”

I’d like to think that the work I do around culture is never perceived as cheesy because it is always genuine and coming from the heart – I’m passionate about building happy places to work.  But the fact is some of the practices used to cultivate certain behaviors in a culture are downright cheesy and can be over the top. Think about the old “trust fall” team building activities… yuck!  Even some of the more low-key activities like bringing in a cake and balloons to celebrate a team milestone can be perceived as cheesy.

So what’s my advice?

  1. All culture work (and leadership behavior in general) must be authentic and come from genuine place.  Lead from the heart and the rest will follow.
  2. Remember that culture is NOT the fun “social committee” activities – culture is much bigger than that.  Culture is the “social glue” that holds an organization together and guides decision making and behaviors of the parts of the system.  Be careful not to associate the social committee-like activities with the word culture – you don’t want folks thinking about these words synonymously.
  3. Accept that some cheese is a good thing.  What would a pizza be without some mozzarella? It’s good to have a little cheese sprinkled in your culture activities.  What matters is that the behaviors of our leaders and culture cheerleaders are genuine and consistent with the values we say we are working toward.

As Jeff said, he’s seen too much “cheese” in culture efforts in the past but he also thinks that a little bit of cheese is a good thing and not having that is a missed opportunity.  Good luck finding your balance between the two!

Tana

Filed Under: agile, culture Tagged With: Agile Culture, culture, Culture Roadshow

November 27, 2015 by Chris Daily Leave a Comment

We’re coming out! Culture was the missing agile link.

Over my career, I have worked in a variety of organizations of different sizes in the financial and healthcare industries.  As I have progressed throughout my career, I have participated in and witnessed a number of agile transformations on my journey. There was always one thing that seemed to get in the way of new ideas or approaches to work, regardless of whether those ideas would be helpful to the organization or not.  And it never mattered whether the idea came down from on high or from the bowels of the organization.  I knew there was something in the way but I couldn’t put my finger on what exactly it was.  The challenges weren’t always the same.  And in most cases there were multiple challenges at the same time.  The challenges ranged from lack of consensus across an organization to one individual with the power to shut down the initiative.

Because I had just come from an agile engagement where this elusive thing (still with no name) was an obstacle to our agile successes, when I arrived at Thrive HDS, I was determined to try to figure out an easier way.  I found that the HR Director, Tana Linback, was already laying the foundation that I would need to introduce agile to the organization.  Tana was focusing on this touchy, feely, squishy thing called culture.  While I had always taken pride in constructing an environment (culture) for the team to be successful, I had not considered the bigger picture and that the culture of the entire workplace is key not just the culture of my team.  Did I catch a break or what?  I had found someone who had experience and loved to focus on an area that was the missing piece of the agile transformation puzzle.  Well, I caught another break soon after.  Tana had heard about Agile and Scrum, but didn’t know much about it but was intrigued.  My agile journey was changing direction in a major way.

APLN pres

Fast forward to November 12, 2015.  Tana speaks at APLN, a Chicago Agile User Group (check them out here http://www.meetup.com/APLN-Chicago/) delivering a presentation titled “Culture Eats Agile for Breakfast”.  The presentation shares our experiences and what we learned while working at Thrive HDS and IHIE, highlighting the key role culture plays. Throughout the presentation and the Q&A that followed, I noticed a lot of nodding heads and smiles of agreement in the audience.  A number of folks in the crowd had similar experiences.  (Several posted their reactions here http://www.meetup.com/APLN-Chicago/events/225673469/)

Tana did a great job of capturing and then sharing the experiences and lessons learned.  As we talked on the drive back to Indy, we both agreed this was a great first step.  It’s time to take step 2.

Chris

Filed Under: agile, culture Tagged With: agile chicago, Agile Culture, agile indiana, agile indianapolis, Agile Professional Learning Network, culture

UPCOMING EVENTS

Mar
26
Mar 26 : 08:50am EST - Mar 26 : 08:50am EST
Learn More
Mar
26
Mar 26 : 08:50am EST - Mar 26 : 08:50am EST
Learn More
Mar
26
Mar 26 : 08:50am EST - Mar 26 : 08:50am EST
Learn More
Mar
26
Mar 26 : 08:50am EST - Mar 26 : 08:50am EST
Learn More
Mar
26
Mar 26 : 08:50am EST - Mar 26 : 08:50am EST
Learn More

Call Us:

(317) 983-2459

#SLINKYTHINK:
DIRECTLY TO YOUR INBOX

We love Agile. We're obsessed with delivering value to you.

Sign up for insightful thought leadership on people, culture, and Agile. It's what we do.

Footer Form

© COPYRIGHT 2015-2020 BELITHE, LLC · All Rights Reserved · Privacy Policy