Info

Scrum Master Toolbox Podcast

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
2019
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: 2019
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.

 

May 31, 2019

We explore the Product Owner anti-pattern of using the Scrum Master as a secretary, and the pattern of a PO that feels the ownership of the product

The Product Owner pattern for the week

The relationship between Scrum Master and Product Owner is absolutely critical for the success of the team. When the PO treats the Scrum Master like a helper, rather than a collaborator lots of things go wrong. We also discuss why this anti-pattern happens, and how to prevent / overcome it.

The Product Owner anti-pattern for the week

The Product Owner title tries to guide to a person in that role to “own” the product. To feel the responsibility and ownership of the product to a level that helps them identify with the product and customers. The goal: to have a PO that pushes the boundaries of what’s possible.

In this episode, we discuss how we can help PO’s feel that ownership.

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 Jassy (Jan-Simon Wurst)

Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself:  the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.

You can link with Jassy (Jan-Simon Wurst) on LinkedIn, or XING and connect with Jassy (Jan-Simon Wurst) on Twitter.

May 30, 2019

Continuing the thread from Monday’s episode with Jassy, we discuss how feedback from the team is a critical source of information and inspiration for Scrum Masters. In this episode, we discuss how to collect feedback from the team, so that the feedback is not biased by your presence, and what are the 4 dimensions of Scrum Master success for Jassy

Featured Retrospective for the Week: Games that inspire insights

Jassy calls himself “not a friend of retrospectives by the book”. He claims to rarely use a “vanilla” format from somewhere else, but prefers to facilitate retrospectives that feel like a game, like a fun thing to do. We discuss metaphor games, and how they help teams find insights they would not find otherwise.

About Jassy (Jan-Simon Wurst)

Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself:  the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.

You can link with Jassy (Jan-Simon Wurst) on LinkedIn, or XING and connect with Jassy (Jan-Simon Wurst) on Twitter.

May 29, 2019

We reflect on the time it takes to effect meaningful change, and how Scrum Masters can help teams learn to be patient in the process. We also discuss some critical tools that help change take hold. Specifically, how transparency and customer/stakeholder engagement can drive change in a team.

About Jassy (Jan-Simon Wurst)

Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself:  the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.

You can link with Jassy (Jan-Simon Wurst) on LinkedIn, or XING and connect with Jassy (Jan-Simon Wurst) on Twitter.

May 28, 2019

In this episode, we talk about motivation and engagement. Jassy shares with us the most common anti-pattern he has seen in teams. It starts with a lack of identification or empathy with the product. Followed by the “we are doing this for someone else” dynamic, leading to further disengagement. Finally, we talk about some of the things that Scrum Masters can do to help their teams get out of that downward spiral.

Featured book of the week: Momo, by Michael Ende

In Momo by Michael Ende, Jassy found a story about time and effort that constantly inspires him in his role as Scrum Master. In the words of the then Norwegian Prime Minister Thorbjørn Jagland, in his New Year Address to the nation on January 1, 1997: "People are persuaded to save time by eliminating everything not useful. One of the people so influenced cuts out his girlfriend, sells his pet, stops singing, reading and visiting friends. In this way he will supposedly become an efficient man getting something out of life. What is strange is that he is in a greater hurry than ever. The saved-up time disappears - and he never sees it again."

About Jassy (Jan-Simon Wurst)

Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself:  the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.

You can link with Jassy (Jan-Simon Wurst) on LinkedIn, or XING and connect with Jassy (Jan-Simon Wurst) on Twitter.

May 27, 2019

When we move from a developer role to a Scrum Master role, many things change. In this episode, we talk about our relationship with our colleagues (the good and the bad), as well as the critical aspect of learning to ask for feedback from the team.

About Jassy (Jan-Simon Wurst)

Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself:  the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.

You can link with Jassy (Jan-Simon Wurst) on LinkedIn, or XING and connect with Jassy (Jan-Simon Wurst) on Twitter.

May 26, 2019

Scrum Masters all over the world make a significant effort to get better at facilitating retrospectives… Until they have to host a Distributed Retrospective. At that point, we learn that all you learned about facilitating retrospectives is still useful, but not nearly enough!

Preparing, hosting, and facilitating a Distributed Retrospective is a completely different challenge.

The 4 things that you need to make Distributed Retrospectives work

There’s no single recipe to make Distributed Retrospectives work. But there are certain ingredients you need to make sure you have in place. It’s important to try to have all of these 4 ingredients in place.

Those 4 ingredients are:

  1. get people to participate actively
  2. get everybody on video (if at all possible)
  3. pace them forward all the time (e.g. using strict timeboxes)
  4. use round-robin (or some other technique) to get everybody to talk

 

The most common anti-patterns in Distributed Retrospectives

As with all other ceremonies, there are some things that are hard to get right and often go wrong. Here’s a short list to keep in mind and prepare to counter-act:

About Aino Corry

Aino is a consultant and agile coach, and has Ph.d in computer science from the last century focused on design patterns and language constructs in programming languages, 20 years as a teacher in academia and industry

You can link with Aino Corry on LinkedIn and connect with Aino Corry on Twitter.

May 24, 2019

Product Owners that have a command and control mentality can derail the team. We discuss this and other topics on this Product Owner focused episode.

The Product Owner pattern for the week

Product Owners that focus on command and control will quickly become too busy to be able to help the team, but that’s usually made a lot worse when the Product Owner has multiple roles. These are the 2 anti-patterns we talk about in this episode.

The Product Owner anti-pattern for the week

When it comes to good Product Owner patterns, we discuss the need to be open to learning from the team, the market and stakeholders. We also discuss evidence-based product ownership.

In this episode, we refer to The Professional Product Owner by Don McGreal and Ralph Jocham.

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 Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an "Agile Transformation." As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

May 23, 2019

There are many challenges teams face that require Scrum Master support. Some of those are related to cross-team dependencies (one of the core aspects for Scrum Masters), but they can also be related to basic improvements in the ways of working. In this episode, we discuss how the team’s outlook on improvement is critical for Scrum Masters and what to look at when evaluating our own contribution to the team.

Featured Agile Retrospective format for the week: What are you looking for out of your work?

When starting with a new team, the questions you ask are critical. Bradley shares with us a format that helps team members understand each other, as well as define the work agreements they need to get them started on the journey to high-performance.

About Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an "Agile Transformation." As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

May 22, 2019

As we work with organizations in transition, we need to help teams and Product Owners make sense of the new ways of working. In this episode, we discuss how Scrum Masters can help Product Owners and teams find a way to collaborate when changing towards Agile. We share some tools that help large groups come together and learn to focus more on the impact they seek, rather than just the work they need to do.

About Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an "Agile Transformation." As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

May 21, 2019

Working with a team of contractors can be a saviour for some organizations. However, there are specific challenges that come with using “outsiders” to do significant projects in any organization. In this episode, we discuss one of the anti-patterns that come with teams of contractors: the lack of future outlook. We also discuss some of the important lessons Bradley learned and how to prepare for when you need to work with a team of contractors.

Featured Book of the Week: Drive by Daniel Pink

In Drive by Daniel Pink, Bradley found the 3 aspects of motivation that later helped him work with the teams he facilitates. In this episode, we also refer to Coaching Agile Teams by Lyssa Adkins and Mindset Growth by Carol Dweck.

About Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an "Agile Transformation." As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

May 20, 2019

The relationship between PO and the team is critical. So critical that if it does not work, it has the potential to derail the whole effort. In this episode, we talk about how to identify possible problems in collaboration between the team and PO, and how to help teams and PO’s collaborate.

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 Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an "Agile Transformation." As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

May 17, 2019

As usual on the Friday’s episodes, we explore Product Owner patterns and anti-patterns to help you work effectively with the Product Owner.

The Product Owner pattern for the week

This Product Owner was the manager for the team, but despite that, he was an effective PO. Listen in to learn how this PO stepped back to help the team contribute, and how he separated his PO responsibilities from his management responsibilities.

The Product Owner anti-pattern for the week

Product Owner’s personalities can have a big impact on the relationship with the team. In this episode, we explore what happens when the PO is self-centered and egotistical. We discuss the symptoms that indicate this anti-pattern and some of the things you may want to do as a Scrum Master to help the PO and team collaborate.

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 Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He's passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

May 16, 2019

Jeremy explains the questions that he asks himself when evaluating his contribution to the team. As Scrum Masters, these are some of the many questions that can help us assess our work and improve our approach to help make teams successful.

Featured Retrospective Format of the Week: The Speed Car retrospective format

The Speed Car retrospective format is one of the many metaphor exercises that helps teams get out of the details of what happened and think about the impact those events might have on their performance, just like many aspects have an impact on a race car.

In this episode, we refer to the classic book: Agile Retrospectives by Larssen and Derby.

About Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He's passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

May 15, 2019

OKR’s are a management tool that is gaining wide acceptance in the tech industry and other industries. The ideas are simple and should be simple to adopt, except they are not.

In this episode, we talk about what Jeremy learned about the roll-out of OKR’s at his company and how Scrum Masters can help adopt OKR’s the right way! Not a simple process.

About Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He's passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

1 2 3 4 5 6 Next »