Why Should Scrum Teams Continually Improve?

Published: Nov. 22, 2019, 1 p.m.

Recently, Dan received an email from a listener that posed an interesting question. In short, they said, \u201cWe\u2019re doing alright every sprint and the business is doing alright too \u2014 we\u2019re not really facing any competition. So, when the team asks, \u2018Why should we continually improve?\u2019 how can I help them through that scenario?\u201d This is a great question! Though this team is stable, have been working together for a long time, and are doing well \u2014 they\u2019ve reached a plateau.

\xa0

When you dominate your market and you feel there is no competition there can end up being a serious lack of continuous improvement (especially if the barrier to entry is really high!) And it\u2019s not totally unexpected that teams sometimes can get a little bit complacent \u2014 but it\u2019s the Scrum Master\u2019s job to challenge that. So, in today\u2019s episode, Dan, and his collaborator, Sam Falco, will be answering this question and addressing how you, as the Scrum Master, can help remotivate your team to amplify what\u2019s going well, shake things up, and make sure they\u2019re all doing more of what they love!

\xa0

Key Takeaways

Why should you continually improve?

In the case of competition (people may find an alternative to your company!)

Because there is always something you can look to improve (even if things are going well you can always amplify that)

How can you get your team to be interested in continuous improvement? What\u2019s important to note as a Scrum Master or team leader?

Watch out for change fatigue (sometimes it\u2019s good to simply celebrate stability)

Ask: \u201cWhat could we try differently?\u201d even if everything is going well (amplify what\u2019s already going well!)

Hold timeline retrospectives (i.e. with the team, plot the events that happened over a period of time and list them from most positive to least to see what people are feeling good or negative about)

By looking back further than a sprint, you can do an exercise called a journey map for the last quarter (or as far back as a year) to look for trends

Find the things that are going to be good for your team (i.e. a compelling interest beyond just the financials of the company)

If some members of the team are bored with the work they\u2019re doing, assign a new project or have them learn a new area of the business

Work with the Product Owner on the question of: \u201cWhat could we do to delight customers? What are they asking for?\u201d using the Kano model

Work with the Product Owner and coach them on the product road map/how to understand customer needs and creating more inspired product backlog items to fuel the motivation for continual improvement

Look for ways to tap into your team\u2019s intrinsic motivation (if you have a long-standing team it may be important to find out what motivates each individual member of the team [which could be autonomy, mastery, or purpose, according to Daniel H. Pink])

Remember that you are looking for the intrinsic motivators rather than the extrinsic motivators (which are things like time off or financial rewards)

Try flipping the script; do your retrospective around: \u2018What would destroy as us a team,\u2019 \u2018How can we mess up,\u2019 and \u2018What would make the next sprint a complete disaster?\u2019

Identify somewhere that the team can go and lead the way by holding the vision and finding areas of improvement (i.e. lead more than serve)

Be sure to keep in mind that change and improvement can take a long time

Find a representative within the team of developers who is interested in continuous improvement to facilitate change, model the behavior, and lead through attraction

\xa0

Mentioned in this Episode:

Kano Model

Drive: The Surprising Truth About What Motivates Us, by Daniel H. Pink

Moving Motivators Cards

Agile Coaches\u2019 Corner Ep. 43: \u201cThe Importance of the Product Owner Role in Scrum with Sam Falco\u201d

Agile 2019 Conference

Agile + DevOps East Conference

\u201cThe Experience Trap\u201d \u2013 Harvard Business Review

\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!