Six simple yet powerful Strategies for Agile coaches to Boost Employee Engagement

Gallup’s latest Global Employee Engagement survey show that only 13% employees are fully engaged and rest are either not engaged or actively dis-engaged. Traditional Managers and leaders who command a position within organization, usually exercise a  bit of authority, power, as well as resources (rewards, bonuses, recognition, etc) towards engaging people. Leadership experts and executive coaches take a route that usually involves, motivating and inspiring people, building trust, uniting everyone in the organization towards common mission, values, and goals. These work great however, need a lot of time, effort and resources.

Agile Coaches on the other hand, are in different situation altogether. Most of the Agile coaches usually command no power and authority within the organization. Yet, they aspire and commit to missions such as creating highly collaborative, self-organizing and high performing teams, developing learning organizations, helping people change behaviors etc. Think about a team that simply won’t speak up, people who would always show up late to meetings, people who prefer to work from closed door offices, team members who prefer they can do anything but contribute on the team, architects who do not share the architecture details with anyone except the leaders. Oh Boy!! there are many such behaviors that hinder teams and organizations from becoming truly Agile.

In this session, I will share six simple, easy to implement strategies and associated instances how I discovered these strategies that I've found very powerful in my experience. Agile coaches and anyone with no power and authority can apply any of these strategies to boost employee engagement, neutralize the environment from Whilte Elephants and promote collaboration. The session will be interactive and will involve simple yet really fun activity. Get ready to cheer and make some noise!!

 
1 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

- Introduction: 5 min

- Strategies: 45 min (~7-8 min each) To put simply, the session would be like the story of the - SlumDog Millionaire movie, where the main character shares real life instances he went through. In this session, I'll go over six strategies listed below and associated instances that I've personally experienced and the powerful results that my team achieved.

   #1: Let 'em Express

   #2: Develop Clarity

   #3: Ask Them!!

   #4: Provide Frequent Feedback

   #5: Embed Fun

   #6: Surprise Them

- Activity: 10-12 min

- Activity debrief: 3 min

- Closing remarks and call to action: 3 min

- Q&A: 8 min

Learning Outcome

- Simple yet easy to implement strategies that can increase the employee engagement significantly.

- How can one engage team members to improve collaboration and create high performance without having authority and power?

- What particularly works well with introvert and 'not me' kind of team members?

- Facilitation skills that can come handy to increase engagement within the team.

Target Audience

Agile coaches, ScrumMasters, Leaders

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ravi Kumar
    By Ravi Kumar  ~  2 years ago
    reply Reply

    Hi Kamlesh,

    I find the topic intriguing and looking for some specifics on the 6 steps outlined. I do see that there are lot of pictures in your slides as placeholder and you are also doing an activity. Here are my suggestions....

    1. Can you point to blog or writeup articulating the 6 steps that is outlined for 45 min.
    2. What is the activity about? Help me understand the relevance of the activity to the topic.
    3. Can the activity be decoupled from the talk and still be able to produce the learning outcomes.
    4. Is it possible to reduce the session to 45min minus the activity if it is possbile.

    I find it a challenging from the audience perspective to sit through a 90min talk unless there is something very complleing which I am unable to see in the proposal. Detailing the above points might help in this. Can you take a crack at this and get back to us at the earliest.

     

    Best regards,

    Ravi

     

    • Kamlesh Ravlani
      By Kamlesh Ravlani  ~  2 years ago
      reply Reply

      Hi Ravi,

      Thanks for your review and the queries.

      Yes, the images are a placeholders and they remind me of the associated story and emotions that I can share with others. I love the analogy that I heard from Chet Hendrickson - CST, consider the Cards of User Stories as Product Owner's vacation photo album. As soon she looks at a photo from the album, the associated vacation memories come alive for her and she can share those memories (requirements when we talk about the User Story) with others.

      The session is not a pure talk, however it wouldn't qualify to be called a pure workshop either. After discussing each strategy, I'll give a minute for the attendees to reflect on their unique situation and identify the possibility and a way to implement that strategy in their context. As, for some of the strategies I'm sharing different ways one can implement it.

      The 10 min long activity is focused on Embeding Fun. A way for the audience to experience it for themselves the state of being fully ENGAGED just with one strategy and obviously having fun. However the activity itself can't deliver the whole message of the session.

      Having facilitated this full session with a 90 minute slot earlier, I'm comfortable with a 90 minutes slot. However if the review team strongly feels that a 60 minute slot is more appropriate, I'm willing to squeeze it in 60 minutes. I think, 45 minutes may only suffice to share the message, but won't allow time for experiential learning and identifying take-aways. Let me know on this.

      Also, as I'm presenting a topic on boosting engagement, I've to be first assured myself that the session will be engaging for the audience :) and having it delivered once in a public forum, I'm positive to keep the audience engaged during the session.

      Thanks,

      Kamlesh

  • Jerry Rajamoney
    By Jerry Rajamoney  ~  2 years ago
    reply Reply

    Hi Kamlesh,

    Nice topic. Is it possible for you to put down those "Strategies" in the outline? Without an insight to this it is very difficult to understand the depth of this talk.

    Thanks,

    • Joel Tosi
      By Joel Tosi  ~  2 years ago
      reply Reply

      Hi Kamlesh,

         Could you please link to your deck from the Phoenix session?  That would help out quite a bit.

      Best,

      Joel


      • Liked Mark Lines
        keyboard_arrow_down

        Mark Lines - Disciplined Agile Delivery: The Foundation for Scaling Agile

        60 mins
        Keynote
        Intermediate

        Organizations are applying agile strategies with large teams, geographically distributed teams, in outsourcing situations, in complex domains, in technically complex situations, and in regulatory situations.  Sometimes they’re successful and sometimes they’re not.  The Disciplined Agile Delivery (DAD) decision process framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable. The DAD framework is a hybrid which adopts proven strategies from Scrum, XP, Agile Modeling, Outside-In Development, Lean/Kanban, DevOps, and others in a disciplined manner.  In this presentation you’ll discover how DAD provides a solid foundation from which to scale agile, learn how agile teams work at scale, and identify several common scaling anti-patterns which should be avoided.

      • Liked Yuval Yeret
        keyboard_arrow_down

        Yuval Yeret - Kanban - A Way Towards DevOps in the Legacy Enterprise

        45 mins
        Talk
        Beginner

        DevOps is a higher form of agility. It is a blueprint for a great culture and and process between the different groups involved in the delivery pipeline. The big question is how to achieve it. If you are founding a startup today, it can be quite easy to take that blueprint and use it to create your process, hire the right versatile flexible people, and start delivering without any technical/automation debt or friction. But most of us are not founding new startups. Most of us already have a running operation with people, culture, process that matured over the years and despite its flaws is currently the way we do things. Changing that is non-trivial. For things to change people need to understand WHY change, what we are changing, and we need an effective process for managing the change itself (HOW to change). So what ARE we changing to? DevOps is highly focused on looking at the whole value stream from idea to value and ensuring effective flow through this pipeline. Kanban is ONE way of HOW to change. It starts by visualizing all the work flowing in the pipeline, then managing the flow focusing on finishing things end to end rather than starting in order to stay busy. It continues to what we call the “Work in process Diet” – Straining the flow more and more in order to identify obstacles to tighter and tighter DevOps culture/operation and faster feedback cycles. You can expect to come out of this session with ideas how to take your current operation and DevOpsify it in a safe evolutionary way using the Kanban method.

      • Liked Diana Larsen
        keyboard_arrow_down

        Diana Larsen - Coaching for "Best Fit" Agile: Applying the Agile Fluency(™) Model

        Diana Larsen
        Diana Larsen
        Partner
        FutureWorks Consulting
        schedule 2 years ago
        Sold Out!
        480 mins
        Workshop
        Intermediate

        Agile has a problem. When we started out with Agile, people used it because it made their lives and products better. Now people complain that Agile is about meetings, top-down mandates, and wasting time. We can do better. It’s time for a change.

        In response, Diana Larsen and James Shore developed The Agile Fluency™ Model and Martin Fowler published it, “Your Path Through Agile Fluency” (http://agilefluency.com). The model describes how teams grow in their understanding of Agile over time. It's a descriptive model, because it reflects what happens in the real world, and in it's an aspirational model, because you can use it to understand how to invest in improving your teams.

        We've found the model very useful for helping teams, managers, and executives understand what they can get from Agile and what they need to invest in order to get those results. The model's emphasis on concrete outcomes means executives are open—even eager—to devote the effort needed. Leaders appreciate being able to see the tradeoffs and make a strategic decision, and teams thrive when given meaningful goals and the time and resources needed to achieve them.    

        In this workshop, led by Diana Larsen, together we’ll dig deeper into the model, including:

        -       Agile Fluency Model Overview

        -       Bringing Agile Fluency into your organization

        -       Examples of Agile Fluency in real-world teams

        -       Examples of organizational investments

        -       Supplemental materials for metrics and assessments

        -       Agile principles and practices in the model

        -       New directions and support for the Agile Fluency Model