Info

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Every week day, Certified Scrum Master, Agile Coach and Business Consultant Vasco Duarte interviews Scrum Masters and Agile Coaches from all over the world to get you actionable advice, new tips and tricks, improve your craft as a Scrum Master with daily doses of inspiring conversations with Scrum Masters from the all over the world. Stay tuned for BONUS episodes when we interview Agile gurus and other thought leaders in the business space to bring you the Agile Business perspective you need to succeed as a Scrum Master. Some of the topics we discuss include: Agile Business, Agile Strategy, Retrospectives, Team motivation, Sprint Planning, Daily Scrum, Sprint Review, Backlog Refinement, Scaling Scrum, Lean Startup, Test Driven Development (TDD), Behavior Driven Development (BDD), Paper Prototyping, QA in Scrum, the role of agile managers, servant leadership, agile coaching, and more!
RSS Feed
Scrum Master Toolbox Podcast: Agile storytelling from the trenches
2024
March
February
January


2023
December
November
October
September
August
July
June
May
April
March
February
January


2022
December
November
October
September
August
July
June
May
April
March
February
January


2021
December
November
October
September
August
July
June
May
April
March
February
January


2020
December
November
October
September
August
July
June
May
April
March
February
January


2019
December
November
October
September
August
July
June
May
April
March
February
January


2018
December
November
October
September
August
July
June
May
April
March
February
January


2017
December
November
October
September
August
July
June
May
April
March
February
January


2016
December
November
October
September
August
July
June
May
April
March
February
January


2015
December
November
October
September
August
July
June
May
April
March
February
January


Categories

All Episodes
Archives
Categories
Now displaying: June, 2019
Jun 28, 2019

This week we talk about the dictator Product Owner and the Product Owner that enables his team by helping them set clear and understandable goals.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

The Product Owner Anti-pattern for the week: The mistrusting dictator anti-pattern

Trust between the Product Owner and the team is critical. When there’s a lack of trust, the PO is tempted to control instead of listening to the team. As Scrum Masters, we must look out for the signs that there’s no trust between PO and team, and act on it.

The Great PO pattern for the week: Focusing on clear and understandable goals

There are many things that great Product Owners do, but one of the most relevant is to set clear, and understandable goals for the team. In Great Product Owner segment, we talk about goals and collaboration. We also talk about how Great Product Owners distribute decisions to the team and rely on the team to help them in their work.

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Long Suciu

Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.

You can link with Long Suciu on LinkedIn.

Jun 27, 2019

Long suggests that Scrum Masters collect feedback from the team to assess their success. The method he suggests is the team NPS: “How likely are the team members to recommend that others join the team?” We also talk about how it is important to measure and reflect to reach a successful outcome for our work as Scrum Masters.

In this Article, you can read how Jason Little (a previous guest on the podcast) used the NPS survey to evaluate his own work.

In a previous episode with Jeff Kosciejew we also reviewed the use of NPS for Scrum Master performance self-evaluation.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

Featured Retrospective format of the Week: Liberating Structures

Retrospectives follow a specific set of activities, from the check-in to get everybody focused and in the mood to reflect, to the data gathering. These activities can be organized in many ways. In this episode, we talk about Liberating Structures, a set of activities that you can use in any of the steps of the retrospective.

About Long Suciu

Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.

You can link with Long Suciu on LinkedIn.

 

Jun 26, 2019

Change can happen at any time, it does not need to be large or involve many teams. As Scrum Masters, we help the teams change continuously. In this episode, we talk about a change of perspective in a Product Owner team that led to positive changes and create a collaborative environment. We also talk about what was the role of the Scrum Master when it comes to helping change happen in that team.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

About Long Suciu

Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.

You can link with Long Suciu on LinkedIn.

Jun 25, 2019

Although Scrum was developed in a software environment, the fact is that Scrum can be applied to many different types of teams. In this episode, we learn about how Long applied Scrum in a marketing team, and the anti-patterns he had to face in that environment.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website

Featured Book for the Week: Lean Startup by Eric Ries

If you got started with Scrum and then discovered Lean Startup, you probably found it to be in line with what you had practiced before. However, Long discovered the Lean Startup book by Eric Ries before learning Scrum, and it reshaped his thinking about what is possible.

About Long Suciu

Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.

You can link with Long Suciu on LinkedIn.

Jun 24, 2019

Having helped a team reach a high-level of performance, it is easy to think that the team will continue to perform for a long time. In this episode, we explore how a team change (a new Product Owner) can reverse a positive trend, and impact the team’s performance. Listen in to learn why that happened, and how you can prevent it from happening to your team.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.

About Long Suciu

Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.

You can link with Long Suciu on LinkedIn.

Jun 21, 2019

This week, the discussion about the Product Owner role is all about collaboration with the team.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.

The Product Owner pattern for the week

With two guests this week, we also cover 2 examples of a good Product Owner. Firstly, we talk about the importance of bringing information and data to the team to help them understand and be part of the decision making for the product.

Secondly, we talk about the need for Product Owners to allow the team to give their input, and be heard when it comes to product decisions. Great Product Owners allow their teams to contribute their own ideas and therefore feel invested in the success of the product.

The Product Owner anti-pattern for the week

The two anti-patterns we discuss this week are related to the collaboration (or lack thereof) between the team and Product Owner.

The first anti-pattern is about the Product Owner that was an outside “customer” (from another department) to the team. When that happens, there’s the temptation to let the PO lead, and not challenge them. Collaboration happens when the PO brings their view, listens, and then makes decisions together with the team.

The second anti-pattern is about the Product Owner as an expert. When the PO is an expert, they might feel they have to bring in all the answers, and therefore make it more difficult for the team to feel ownership and contribute to the product. It can also happen that the PO becomes a micro-manager. All signs to look out for.

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Katy Cabral & Joseph Contreras

Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.

Joe is an experienced scrum master, who strives each day to help and coach his squad to continuously improve how they work so that they can be awesome.

Joe is also a scrum master chapter lead at Fidelity Investments.

Jun 20, 2019

Scrum Master’s success is dependent on the team’s approach to solving their own problems. In this episode, we talk about how teams that take ownership of the process, make decisions on their own and find their own incremental improvements are a sign of a successful Scrum Master. But how do we get there? In the episode, we talk about tools that help Scrum Masters succeed.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.

Featured Retrospective Format of the Week: Wow, Wandering, Worried. Artifacts, events, roles

Joe and Katy share with us two retrospective formats. First, we discuss “Wow, Wandering, Worried. Artifacts, events, roles”, a format that turns the team’s attention to the items, or things they want to improve.

The second agile retrospective format is the “Picture retrospective” (example: The Sailboat Retrospective exercise). In this segment, we specifically talk about the use of pictures or drawings as check-in as well as data gathering and decision exercises.

About Katy Cabral & Joseph Contreras

Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.

Joe is an experienced scrum master, who strives each day to help and coach his squad to continuously improve how they work so that they can be awesome.

Joe is also a scrum master chapter lead at Fidelity Investments.

Jun 19, 2019

Sometimes, new teams are formed where some team members still have “legacy” tasks in their to-do lists. When that happens, it is the responsibility of the team (with the help of the Scrum Master) to figure out how to handle that work. There are many options to handle that situation. What is not ok is to let it grow, and spiral out of control. Teams own tasks, not individuals, therefore the Scrum Masters should help the team understand that legacy tasks are a team issue, not a personal issue.

In this episode, we refer to the concept of T-Shaped skillsets for individuals, and the Agile Retrospective format called “pre-mortem”.

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.

About Katy Cabral & Joseph Contreras

Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.

Joe is an experienced scrum master, who strives each day to help and coach his squad to continuously improve how they work so that they can be awesome.

Joe is also a scrum master chapter lead at Fidelity Investments.

Jun 18, 2019

A common anti-pattern Scrum Masters encounter in their teams is the inability to say “No!” This becomes an especially impactful anti-pattern when the team is unable to say “No!” to the Product Owner. When that happens we run the risk of allowing the team to ver overwhelmed, and eventually decrease the quality of their work.

In this episode, we discuss that anti-pattern and how Scrum Masters can help Product Owners and teams to avoid that from becoming destructive for the team.

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

Featured Book for the Week: Scrum: the art of doing twice the work, in half the time by Sutherland & Unmarketing, Scott Stratten

This week we have a tag team for guests and therefore we have two books to discuss. Katy recommends Scrum: the art of doing twice the work, in half the time by Jeff Sutherland.

That book helped Katy understand better her role as a Scrum Master.

Joe takes a different approach and recommends a book that is not about Scrum or Agile: Unmarketing - stop marketing, start engaging by Scott Stratten. This book helped Joe understand better the team he is working with, which is a marketing team.

In this episode, we also refer to Who the Hell Wants to Work for You?: Mastering Employee Engagement by Tim Eisenhauer and Overcoming the Five Dysfunctions of a Team: A Field Guide for Leaders, Managers, and Facilitators by Patrick Lencioni, a follow-up to a regular recommendation on the podcast: The Five Dysfunctions of a Team by Patrick Lencioni.

About Katy Cabral & Joseph Contreras

Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.

Joe is an experienced scrum master, who strives each day to help and coach his squad to continuously improve how they work so that they can be awesome.

Joe is also a scrum master chapter lead at Fidelity Investments.

Jun 17, 2019

When we want to help the teams we work with, sometimes we go too far. In this episode, we share a story of a Scrum Master that did just that, only to find out that it is critical that the teams take ownership over the solutions they choose to implement. No matter how much experience we have, as Scrum Masters, it is ultimately the team that needs to improve and live with their choices.

About Katy Cabral & Joseph Contreras

Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.

Joe is an experienced scrum master, who strives each day to help and coach his squad to continuously improve how they work so that they can be awesome.

Joe is also a scrum master chapter lead at Fidelity Investments.

Jun 16, 2019

There’s many insights to be had from looking at how Startups and Lean Product businesses develop software and bring products to the market. In this BONUS episode with Ash Maurya we learn about Lean Product Development from the author of Running Lean, one of the first published books around Lead Product Development.

Developing a book, the Lean way

When Ash got started he was not a famous author. He started a blog. By publishing his ideas on that blog and collecting feedback he understood the importance of the ideas that he was sharing and ultimately wrote his book: Running Lean: ITERATE FROM PLAN A TO A PLAN THAT WORKS.

In the blog, he shared his learnings from trying and failing at product development. From those blog posts came a book, but also a new tool, the Lean Canvas.

Lean Canvas, a better business modeling tool

The Lean Canvas came from Ash’s own experience and learning when trying to define, design and launch products and new businesses.

Lean Canvas is a 1-page business plan template that helps product developers come up with the key ideas or assumptions on which their business and product depend on. Ash adapted the Lean Canvas to improve the Business Model Canvas, developed by Alex Osterwalder. The Lean Canvas replaces elaborate business plans with a single page business model.

Lean Product Development: Agile made real

Lean Product Development is about iterating your product and business idea over time. From plan A to a plan that works, as Ash puts it. In that aspect, Lean Product Development became the embodiment of the original Agile idea of iterative development. We can argue that Lean Product Development continued what Agile started, but failed to realize: applying Agile as a philosophy of business and to all aspects of business, not just the software development process.

How Ash followed his own advice: Lean Stack, a Lean Product company

It is particularly fitting that Ash followed his own advice and applied his ideas to developing his own business. Lean Stack is a company that Ash created to market a Lean Canvas tool as well as to serve as the “home” to develop many more Lean Product Development tools. In this episode, we discuss some of those tools, but you can find many more at Lean Stack, which has a free trial for you to get familiar and learn about Lean Canvas.

Going beyond Running Lean, the book: Scaling Lean

Later on, a few years after publishing Running Lean, Ash wrote and published Scaling Lean, where he collects new tools and solutions to the most common problems he’s seen in the field when applying Lean Product Development. In that book he specifically discusses Lean metrics, and how to communicate ideas using leading metrics, not trailing metrics.

We discuss why “revenue” is not a good metric for Product Development (even if it is a critical metric, albeit “lagging”).

In this segment, we also learn about Ash’s new book the upcoming book on Product Discovery where he introduces new tools such as the Customer Forces, a new canvas for Lean Product companies to use when developing their products.

Resources for further study

For those interested in learning more about Lean Product Development, Ash recommends the Lean Analytics and Lean Customer Development books, which explore specific aspects of Lean Product Development not discussed in the Running Lean or Scaling Lean books.

About Ash Maurya

Ash Maurya, is a serial entrepreneur and author of the startup cult classic Running Lean, pairs real-world examples of startups like Airbnb and Hubspot with techniques from the manufacturing world in this tactical handbook for scaling with maximum efficiency and efficacy. This is vital reading for any startup founder graduating from the incubator stage and product developers working for growth businesses.

You can find more about Ash Maurya at LeanStack.com where you can also find a free trial for the Lean Stack product.

Jun 14, 2019

We explore the technical-dictator Product Owner anti-pattern and also talk about how great Product Owners get ready and come prepared for the meetings with the teams.

The Product Owner pattern for the week

When Product Owners come prepared to the meeting, you know they are doing their job well. They bring numbers, the rationale behind certain decisions, maybe even different options for priority to be chosen based on the feedback from the team. In this episode, we refer to the work by Jeff Patton and Jeff Gothelf, who’ve both been on the podcast before. You can find Jeff Patton’s Podcast episode here. You can find Jeff Gothelf’s podcast episode here.

The Product Owner anti-pattern for the week

Many Product Owners come from a technical background. This means that they know a lot about the technical aspects the team needs to consider. However, when the PO starts to question the team’s estimates or decisions, that’s a recipe for failure. Listen to how Nick handles that situation, and get some tools and practices you can apply right away!

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

 

Jun 13, 2019

Is the team providing feedback openly to each other and stakeholders? That’s one of the key success questions that Nick asks when evaluating his own success as a Scrum Master.

That leads him to find approaches to help teams open up and share their perspective on the work.

In this episode, we also refer to a paper on how to help teams improve their performance. It is based on the same principle that top athletes apply every day: pushing, then resting. A cycle that is guaranteed to improve performance over time.

Featured Retrospective Format for the Week: The Island Expedition metaphor format

Nick likes to focus on creativity for the retrospectives he facilitates. He’s found several metaphor-focused formats that work, but one he especially likes is The Island Expedition.

Metaphor-focused formats help the teams be more creative by taking them out of their regular context and pushing them to imagine themselves in a different context.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Jun 12, 2019

Scrum Masters that move onto organizations that are just in the start of Scrum adoption may find that it is not an easy process, even when you have top-management support.

In this episode, we talk about what goes wrong when we focus on change from the top, and forget that the teams (whom we work with), might be against the change. Top management support is not enough for Scrum adoption!

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Jun 11, 2019

When adopting Scrum, some organizations focus on the process, the meetings that come with Scrum. But, unfortunately, they also often forget about the meaning and the reason for those meetings, ending up just renaming the old meetings with new names.

This anti-pattern is common, and we should be able to detect it and counter it in our organizations. In this episode, we discuss how to detect and reverse the “same meetings with different names” Scrum adoption anti-pattern.

Featured Book of the Week: Management 3.0 by Jurgen Appelo

In Management 3.0 by Jurgen Appelo, Nick found a book filled with practical tips that help Scrum Masters (and managers) to work with the team every day, and make their work easier. In this episode, we also talk about the source for retrospective format ideas: Retromat.org; and about a book that inspires Nick every day: The Little Prince by Saint-Éxupery.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Jun 10, 2019

Scrum Masters work with teams every day. The way teams feel about the work they do is extremely important for them to be engaged and motivated. However, sometimes we overlook that and fail. In this very personal story by Nick, we learn about what happens when Scrum Masters overlook and even ignore the motivation and engagement of the team.

About Nick Vitsinsky

Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.

You can link with Nick Vitsinsky on LinkedIn and connect with Nick Vitsinsky on Twitter.

Jun 7, 2019

We explore the absent Product Owner anti-pattern and discuss a case when it was OK to have the Product Owner also play the role of a developer in the team.

The Product Owner pattern for the week

We often hear that the Product Owner cannot be a developer at the same time. However, in some cases, that’s not a problem. In this episode, we talk about the Product Owner that was also a developer, and what made that PO a great PO despite the dual role.

The Product Owner anti-pattern for the week

When the Product Owner is too busy, the team suffers. In this episode, we talk about the anti-pattern of the absent Product Owner, and how Scrum Masters can help the team and the Product Owner in that situation.

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn and connect with Mili Shrivastava on Twitter.

Jun 6, 2019

One of the most common, and sometimes forgotten, sensors for a Scrum Master is the daily meeting. Mili asks us to consider how the team members show up for the daily. Are they excited about the day that is starting? Or happy about the results of the day that is ending?

How are you using the Daily stand-up to assess your impact on the team?

Featured Retrospective Format for the Week: KALM

Keep your teams focused on the problems they want to solve with this simple format. KALM stands for Keep, Add, Less, More. These are the keywords that Mili asks the team to consider when reflecting on the previous Sprint.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn and connect with Mili Shrivastava on Twitter.

Jun 5, 2019

Planning for a Sprint is not an easy task. There are many unknowns, even at the Sprint level, and team members justifiably feel uncomfortable discussing commitments, when they know there will be unexpected events during the Sprint.

How can Scrum Masters help teams learn the value, and the mechanics of planning? That’s what we discuss in this episode.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn and connect with Mili Shrivastava on Twitter.

Jun 4, 2019

Inevitably, teams will bump into problems over time. It is how teams and their stakeholders react to those anti-patterns that matters. In this episode, we explore the importance of retrospectives in helping teams identify, understand, and ultimately resolve the anti-patterns they fall into.

Featured Book of the Week: Thanks for the Feedback: The Science and Art of Receiving Feedback Well

In Thanks for the Feedback by Douglas Stone and Sheila Heen, Mili found a good tutorial on how to give, and receive feedback. Handling feedback, whether it is giving or receiving, is one of the most common tasks Scrum Masters deal with, and help team members deal with. Therefore, this book should be part of the reading list of all Scrum Masters.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn and connect with Mili Shrivastava on Twitter.

 

Jun 3, 2019

Often, teams get too eager to deliver. So eager, they end up planning too much for one Sprint. What usually follows, is that teams leave a lot of stories unfinished at the end of the Sprint, which in turn affects the next Sprint.

In this episode, we explore how Scrum Masters can progressively get the teams to understand what creates that anti-pattern and how to overcome it so that teams start finishing more, if not all, the stories during the Sprint.

About Mili Shrivastava

Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.

You can link with Mili Shrivastava on LinkedIn and connect with Mili Shrivastava on Twitter.

 

1