Tim was faced with a problem. How to be a leader without any formal power. All Scrum Masters and Product Owners who have felt the responsibility, but not any “line authority” have faced the same problem. You need to help move the project along, but you can’t tell people what to do!
In this episode we explore the concept of Lateral Leadership how it can help you as a Scrum Master or Product Owner.
Tim Herbig is the author of Lateral Leadership a recent book published by Sense and Respond Press.
Ben is a project manager with experience in developing digital services and products for worldwide clients. He’s learned some very important lessons and shares some of his key insights with you in this special episode, where we dive deep into the project manager role and the project management world.
Continue reading BONUS: Ben Aston on Project Management lessons that Scrum Masters can use
There are quite a few books out there about the Scrum Master job. However, the classic that many refer to over and over again here on the podcast is Scrum Mastery by Geoff Watts.
In the description of the publisher writes: “Scrum coach Geoff Watts has identified patterns that separate a good Scrum Master from a great one”.
As a podcast for Scrum Masters, we wanted to have Geoff on, to share the key insights in the book, but also what he learned since the book was first published in 2013.
But, before we go into those new lessons learned, let’s quickly review some of the key insights from the book
Read on for the detailed show notes and all the links…
When organizations start with Agile, they typically focus on the work that needs to be done at the team level. In many organizations we have “water-scrum-fall”, a little bit of Scrum squeezed inside two big buns of a plain waterfall.
The reason for that is that organizations don’t change as a whole. Typically Agile adoption starts in Engineering/R&D and slowly spreads throughout the organization. At some point, it bumps against the slow moving, but very powerful finance department. Where are all the financial decisions are made, including how to fund projects, and where Procurement has a key role. How do we change Procurement (buying software development) to fit Agile organizations?
That’s the topic we explore with Mirko Kleiner, a pioneer in the Lean-Agile Procurement movement.
Read on for the detailed show notes and all the links.
When Agile broken into the scene, it was mostly about the techniques to develop releases of the product quickly. However, that was a time when products were released only a few times a year at best. Today products evolve continuously and that changes how product Owners and Product Managers need to interact with the teams. In this episode, we explore some of the key lessons Jeff has learned working with product organizations all over the world. In short: Product Managers also need to adapt to Agile, it’s not just the teams!
Read on for the detailed show notes and all the links.
In this episode, we explore some of the critical lessons Jeff learned in his own career as a Product Owner. We review the missing aspects in most Product Owner role implementations and discuss the tools that have helped Jeff as a Product Owner first, and later his students.
Read on for the detailed show notes, and all the links
For several years, the Agile community has been struggling with the use of Agile practices – developed for small teams – in the large. Large organizations or multi-team efforts are the rule, not the exception in the software world. In this episode, we explore Nexus, a scaling framework developed by Scrum.org to tackle just that: the use of Scrum in larger organizations and multi-team product development efforts.
Read on for the detailed show notes and all the links.
For this first Christmas 2018 special we focus on scaling Agile, and specifically how the Scaled Agile Framework (SAFe) can help organizations take Agile and apply it in the large.
There are many systems that require multiple teams to work together. As more and more industries adopt software as a core part of their services and products, we also see many organizations developing many products concurrently, and large engineering organizations that require coordination across tens or hundreds of teams, including non-software teams.
In this episode, we discuss how SAFe can help you take Agile to that type of environments and organizations.
Read on for the detailed show notes, as well as all of the links.
Continue reading BONUS: Dean Leffingwell on scaling Agile and the Scaled Agile Framework, SAFe
As Scrum Masters we are constantly facing a changing environment. Every Scrum Master needs to learn about change, change methods and tools that work in practice. In this episode we dive deep into the change approach that Mike Burrows developed based on his experience as a coach and leader in the software industry.
Mike introduced what he called a “values-model” for Kanban adoption in his blog post titled Introducing Kanban Through Its Values.
In that blog post he introduced some of the ideas that today compose Agenda Shift, a more extensive approach to introducing a change approach that focuses on outcomes.
Read on for the details on Agenda Shift and Outcome-Oriented Change.
Continue reading BONUS: Mike Burrows on Agenda Shift, the outcome-oriented change approach
This is an episode about #NoProjects, #NoEstimates and introduces a unique, and 1-time-only workshop by Allan and Vasco that will take place in London in February 2019. Check out this page about the #NoProjects and #NoEstimates Workshop to know more.
In the past few years a few new trends have emerged in the Agile community that have challenged some of the basic assumptions of how software should be delivered. The first one, #NoProjects is challenging the idea that software work is best managed as a project. As Allan puts it in this episode: “Successful software does not end. It continues. And projects are for temporary endeavours, that have a known start and fixed end. That’s now how software is developed today.”
With that start to the episode you can expect that many unconventional (and inconvenient?) ideas will be shared in this podcast focused on the latest trends in how to manage software development.
