Bevan Williams: Helping an organization increase their speed with a change process you can use

When Bevan started working with this organization, he heard the CEO say that the development was too slow. So the change started with a clear mandate, which Bevan and the team took on and started working with. They used tools like Value Stream Mapping, and went through a process to involve the teams in defining and ultimately overcoming their slowness. In this episode, we refer to Clean Language and Systemic Modelling by Caitlin Walker.

About Bevan Williams

Bevan is an Agile Coach & Trainer at Think Agile. His career has been driven by his passion of creating inclusive environments where people can be at their best. 

You can link with Bevan Williams on LinkedIn and connect with Bevan Williams on Twitter.

Leland Newson: Introducing change in a Scrum team with Lean and Value Stream Mapping

While trying to help a team, Leland discovered a set of tools and ideas that helped him and the team find a new way to work that improved their performance. Focusing on improving the flow in the team, became a directed change approach that helped the team improve, and at the same time became a vehicle for introducing change in the team.

In this episode, we refer to: 

About Leland Newson

Leland is a SAFe Release Train Engineer and servant leader who is passionate about helping improve the work environment and helping teams uncover better ways to development software. He focuses on collaboration, shortening feedback loops, improving the flow of work through the system and increasing the team’s adaptability so they can quickly respond to changes and satisfy customers through early and continuous delivery of valuable software.

You can link with Leland Newson on LinkedIn and connect with Leland Newson on Twitter.

BONUS: Manuel Pais interview – Continuous Delivery for Scrum teams, Part 4

How do we get started with Continuous Delivery? Manuel suggests that we run a Value Stream Mapping session with all the teams involved in the release process to learn about the “current state” of the release process. 

We also review the most common challenges and blocks for teams that are starting to adopt Continuous Delivery. 

Read on to learn about the different motivations businesses have to adopt Continuous Delivery, and Manuel’s 3 steps from bi-weekly release to Continuous Delivery.

Continue reading BONUS: Manuel Pais interview – Continuous Delivery for Scrum teams, Part 4

BONUS: Morten Herman interview – Continuous Delivery for Scrum teams, Part 3

Morten’s adoption story starts with a team at eBay Denmark. The team had started working in a more continuous mode, but there was a lot of “release friction” as Morten calls it. You are probably familiar with that friction: it takes a long time to release; the site needed to be “closed” for every release; the team would need to come in at night during the weekend, etc. 

That’s the reality for many teams. No surprise they prefer to release less often. In this segment, we explore that story, and also the steps the team took to go from “high friction” to “no friction”. 

Read more to find out how Dev and Ops are different and why that matters when adopting Continous Delivery.

Continue reading BONUS: Morten Herman interview – Continuous Delivery for Scrum teams, Part 3

Victor Bonnacci uses Value Stream Mapping to understand the system he works within

There are many tools and approaches we can use to define and understand the system we work within. Victor explains how he uses conversations and Value Stream Mapping in his attempt to understand the system he works within.

About Victor Bonnacci

Vic coaches software teams at Bio-Rad Laboratories using Scrum and XP practices. He’s worked in IT for twenty years; first as a webmaster, programmer, project manager and currently as a scrum master and coach. Vic lives in Southern California where he is very active in the local community, and he hosts the Agile Coffee podcast.
You can link with Victor Bonnacci on LinkedIn, and connect with Victor Bonnacci on Twitter.
Be sure to follow Victor Bonnacci’s podcast: Agile Coffee.

Angel Medinilla on the tools that allow us to see and manage the system as a whole

Systems affect teams’ and individuals’ performance. We need to learn to see the system to be able to manage it. Angel shares with us the tools he uses to understand and measure the system performance in a way that includes all aspects, from concept to cash.
In this episode we mention the book Lean Software Development by Poppendieck et al.

About Angel Medinilla

Ángel Medinilla (Spain, 1973) has 18+ years working experience in the ICT market. In 2007 he started his own Agile Consulting firm. Today, Proyectalis is considered the leading Agile consulting and coaching company in Spain, and one of the most well-known in Europe and Latin America,
He is a regular speaker at Agile conferences all over the world
He is the author of Agile Management (Springer) and “Agile Kaizen: Continuous Improvement Far Beyond Retrospectives’ (Springer). He also contributed to Beyond Agile: Stories of Agile Transformations, (Modus Cooperandi).
In 2015 he co-founded Improvement21, whose goal is to bring the continuous improvement habit to all kind of organizations in order to create better cultures, teams, processes and products.
You can connect with Angel Medinilla on LinkedIn, and contact Angel Medinilla on Twitter.

Juha Heimonen on the importance of visualizing work

We must visualize our work in many different ways to be able to understand it. This is the key lesson by Juha when we talk about understanding the system of work.
He mentions several tools we can use to visualize our work: Value Stream Mapping and Kanban being two examples. And we discuss Torbjörn “Tobbe” Gyllebring’s presentation on Kanban that explains how to use Kanban as an improvement catalyst: Kanban is not your process, let me explain why.

About Juha Heimonen

Juha is a entrepreneur, programmer, kanbanista and a unicorn. He calls Software a garden, and says that he tries to be a gardener tending the soil as well as the specific plants.
He is active in the local agile community in Jyväskylä, Finland and also quite active on twitter.
You can link up with Juha Heimonen on LinkedIn and connect with Juha Heimonen on twitter.
You can find out more about his thoughts on Fellowship and how he applies that in his own business at Flowa’s website and blog.

Steve Holyer gives you 5 tools that you can use to assess the System

The 5 tools that you can use to assess the system are:

  1. Agile Fluency model: a model to assess the development of the teams you work with. To know more, check out AgileFluencyImmersion.com, a workshop that helps you and your teams learn how to achieve better results.
  2. Strategy Maps: A diagram that creates clarity on what are the defined, but also real goals for an organization.
  3. Design your coaching alliance: A method to help you, as a Scrum Master, understand what are the goals for your work with the teams, and to anchor your work on a clear vision and outcome.
  4. Impact Mapping: a method to help you discover and understand what are the high-value work items (User Stories or Features) for your teams to work on. This tool alone will have a great impact on your work with Product Owners.
  5. Value Stream Mapping: A way to analyse how the work is completed in an organization. Following the work from start to completion and creating a Value Stream Map of that work will give you insights into what are the impediments to value creation in your organization.

About Steve Hoyler

Steve Holyer serves as advocate, trainer and mentor for companies looking for a better ways of working, using Agile practices in a productive, fulfilling, and fun way.
He learned his craft serving as a Scrum Master with multiple teams and organisations, so he knows how to change an organisation from the inside. Steve now serves as an indie-label Agile Coach-for-Hire. He’s passion lies with coaching managers and teams to find ways to do software better.
You can contact Steve Hoyler on twitter, and find Steve Hoyler on LinkedIn. For more, check his Lift Off workshop.

Get The Booklet!
How to deliver on time and eliminate scope creep By scoping projects around outcomes and impacts, not requirements!
Get the Product Owner Booklet!
Avoid scope creep! And learn to scope projects around impacts and outcomes, not requirements!
Get These Valuable Lessons Today!
Down-to-earth, hard-earned Scrum Masters lessons and the Tips from the Trenches e-book table of contents, delivered by email
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works