How can I nudge my team to be more Agile?

So I'm on this team that's supposedly Agile, but …

  • Our daily scrum goes 45 minutes
  • Somebody else plans our sprints
  • We don't have retrospectives
  • We don't do sprint reviews
  • My team has 25 people
  • We've got 6 Product Owners
  • Stories are assigned by the Scrum Master

How can I as a team member nudge my team to be more Agile?

In this interactive discussion we'll look at ways that individual team members can influence our teams to be more Agile by asking a few key questions. These questions will help us get a clearer understanding of how individual practices contribute to agility and how to approach change within out teams with respect, curiosity, and a sense of adventure.

 
3 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Workshop

  • Introduction:
    • Our discussion today comes from a deep and well-earned respect for the Agile Manifesto, Agile Principles, and the Scrum framework.
    • In reality, however, for many of us who are on supposedly-Agile teams, our practices are often very different than the picture painted by these concepts.
    • What are some ways that you and your teams don’t follow this framework or these principles?
    • So the question is: what can we do about this?
    • Let’s consider one of these as an example: no retrospectives
      • What effect does this have on me, the team, & the organization?
      • What are some ways we can approach this?
      • What does my team care about and how does this relate to their issues?
  • Before initiating any change, it’s important to be clear about: What do we want and why?
    • Participants divide into groups of 4-7 people.
    • SMALL GROUP DISCUSSION: Each group will pick an issue from the list and discuss the following questions. If they have extra time they can do the same for additional issues:
      • Why does this bother me?
      • What effect does this have on the team?
      • What effect does this have on the organization?
    • FULL GROUP REPORT: Each group will share their insights with the full session
  • Next, we need to ask ourselves: What can we do about it?
    • What are my options for action?
      • Let it go
      • Put it on the backlog of changes I want to push for
      • Change my own practices
      • Talk to others on my team one–on–one
      • Bring it up in a retrospective
      • Talk to leaders
    • What options are there in how the team approaches it?
      • What have we tried before and what did we learn from it?
      • Could we try a partial solution?
      • Could we ask the team for their ideas?
      • What could be done as an experiment?
      • How might we ensure that people feel safe trying something different?
      • What if team members don’t want to be a part of the change?
    • SMALL GROUP DISCUSSION: Each group will discuss the following questions about the issue(s) they discussed previously:
      • What are some ways that it can be improved?
      • Who can address it?
      • What can we do as individuals to begin the change?
    • FULL GROUP REPORT: Groups will share their findings with the full session
  • What can I say to convince them?
    • Putting it in context: How well are we doing?
      • Are we producing results regularly?
      • Are we able to adapt to change?
      • Are our results of good quality?
    • What’s important to them?
      • What do your teammates want?
      • What does your leadership want?
    • SMALL GROUP DISCUSSION: Each group will discuss how they might persuade others about the change(s) they’re proposing.
      • Why is this more important than other things?
      • What are the potential benefits?
      • How will this affect them?
    • FULL GROUP REPORT: Groups will share their findings with the full session
  • Wrap Up:
    • What are some things you got out of this workshop?

Learning Outcome

Participants will have experience doing the following:

  • Applying Agile principles to specific team situations
  • Considering how individual Agile practices affect team results
  • Prioritizing potential changes and
  • Reasoning about potential changes from the perspectives of the people they are trying to influence.

Target Audience

Scrum team members

Prerequisites for Attendees

Participants should have some familiarity with the Scrum framework and terminology.

schedule Submitted 4 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Kevin Sheen
    keyboard_arrow_down

    Kevin Sheen - How to avoid 'Hitting the Wall' in your Agile Transformation (or how to get 'unstuck')

    60 Mins
    Talk
    Intermediate

    Over the years as an Agile practitioner, I've seen mindsets change on Agile and what it should and shouldn't be used for. The good news is that the 'shouldn't be used for' list continues to go down. In fact - I'm encouraged by the trend from 'should not' to 'could' to 'absolutely should' - when it comes to applying Lean and Agile.

    But over that same time period, I've watched a number of organizations, populated with very smart, creative and passionate people, struggle with their own Agile journeys. Subsequently, I've spent a lot of time working with those organizations and introspecting on my own and with my team.

    "How do we make the Agile transformational journey more efficient, fruitful and more enjoyable for everyone?

    Ironically, the way most organizations look to start or advance a stuck Agile journey is to seek out a formula or 'best practices' to road-map their enterprise plan. Potentially you cringed as much as I did as I wrote the last sentence. Specifically, taking a plan-based approach to move away from a plan-based approach is an anti-pattern and somewhat the antithesis of the Agile mindset.

    So what should we do?

    The best way to speed up your Agile journey is not by reading articles, books, blog postings, attending conference sessions ;-) or to seek some kind of formula to put together a plan. While those things can educate and even inspire, they maintain the slower path - albeit one that generally 'feels safer' for some.

    A far better prescription is to follow an approach to the Agile journey that is in itself - Agile.

    While that may seem intuitive, there are also implications to 'how' you approach the challenge from an organizational perspective. The classic approach to 'train the development team' and everything else follows is prone to stalling for a variety of reasons.

    This session will explore both an Agile / Lean approach to 'Enterprise Agile Transformation' but also take a look at where to best start and how to progress more effectively in that transformation. Notice that I quoted 'Enterprise Agile Transformation' because there are some clues in the name that help us truly map out a far more effective and enjoyable approach to moving along your Agile journey.

    I promise you that this session will provide some concrete 'ah-hah' moments that in retrospect will not only make lot's of sense, but also be very pragmatic and do-able.

  • Liked Joanna Schwab
    keyboard_arrow_down

    Joanna Schwab / Michael Dreyer - Agile Team Frustrations - The Science Behind the Fuzzy Stuff

    60 Mins
    Talk
    Beginner

    We know that fulfilled employees are engaged, happy and inspired…and inspiring!

    Fulfilled work should not be an anomaly to be looked upon from the outside looking in, but the normal way we engage at work. How do we do this, especially in a team environment?

    We all need to learn how to build psychological safety and trust in our teams. Psychological safety is an emergent quality that develops over time, so it is important to know that every interaction you have with your team either builds trust or erodes it.

    In this session we will explain how Agile can be used to create effective teams by leaning on Cognitive Behavioral and Family Systems theories, explaining the science behind psychological safety, and giving you the tools you need to shift that suboptimal team dynamic.