This is the case of a team that was working well. They understood Agile, they had experience, they practiced Agile. However, there was a problem. The Product Owner was missing. What happened? What were the problems, and what change management approach was used to help the team and the PO collaborate? Listen in to explore this and learn about how role playing can help you tackle tough situations with your team.
About Shubhang Vishwamitra
Shubhang is a passionate agile practitioner originally from Bangalore, India. Who’s worked in Japan and Finland and is currently based in London and working as scrum master.
Shubhang has an extensive background in software development and agile delivery model in smartphone, travel and finance industries. He believes that having a technical background helps to connect with teams and ease the flow of discussion in solving complex problems.
Visualization is one of those tools we often ignore, or dismiss because it does not fit the distributed world we live in. However, that’s one of the most important ways to get a change started. In this episode we explore how adding a simple visualization (Kanban Board) helped a team to go from Chaos to a flow of work.
In this episode we refer to Modern Agile, a community of practitioners asking: what’s next for Agile?
About Sarah O’Brien
Sarah is passionate about helping teams work together to bring value to their work lives. She has worked in the Scrum Master role for the past 6 years after transitioning out of waterfall as a senior software engineer. Her (not so) secret goal is to help people bring agile practices home.
Change is a big scary word in many organizations. But why is that? In this episode we talk about change in a different way. We explore what change would be, if it were the basic operating model of the organization. We talk about Nils Pflaeging’s work, about Complexity and how it affects the way organizations work in reality (as opposed to theory). As Jella says: “Change should be like adding milk to coffee.”
Jella has a background in linguistics (totally non-tech) and calls herself “agile native” (having never worked any other way, at least in software development). She works as a Scrum Master since 2014 at Qudosoft in Berlin. She has worked with both colocated as well as distributed teams.
Working with a team is hard enough when the organization is stable and not going through a major upheaval. But when an organization is in massive change, how can we keep teams motivated and engaged with the work? In this episode we discuss the story of a team that was “alone” in the middle of a major organizational change, and what they did to keep the motivation and even going far beyond the call of duty. An inspiring story of how, sometimes, change comes from the team itself!
Lynoure has worked in many roles in the IT, from operations, scrum mastering and requirements analysis to programming, even a little as a tester. She’s worked in agile teams since 2000 and loves being an adapter type, bringing in a wider perspective into her projects and to help different types of personalities to work together.
The adoption of a new process can be a great example of how change happens and is gradually accepted, and then adopted by the teams and team members. In this episode we explore a Kanban adoption, and how the process of Kanban also had an impact on the change itself.
In this episode we talk about ScrumBan, a development approach that tries to pick the best components of both Scrum and Kanban.
About Kathy Andersen
Kathy works as a Scrum Master with a team implementing a billing management system for a company called Hudl. Hudl is headquartered in Lincoln, Nebraska and provides video review and performance analysis tools for coaches and athletes to review game footage and improve team play. Kathy took an uncommon route to the software world, and since then she has had the luck of working on a diverse set of projects and teams. You’ll find her speaking at conferences and participating in the agile community.
Work life is a serious thing. We spend (at least) one-third of our time awake at work, and in some cases much more time than what we spend with our families most days of the year.
Now imagine what would happen if your work would be falling apart. You have too much work, and are being constanly interrupted. Your authority and ability to contribute is undermined. And on top of it your place of work is literally crumbling: the roof collapsed and what is left is being innudated by dirty water that runs off from the roof’s debri.
Meet Ibu Elsye! Ibu Elsye is the lady dressed in black in the picture or “Mrs.” Elsye if you don’t speak Indonesian ;).
She’s General Manager of a hospital, Rumah Sakit Bungsu (aka The Bungsu), that Marcus Hammarberg helped, in Indonesia. General Manager; what is that, in a hospital? I’m happy you asked: basically she’s in charge of everything that is not health care. Food, laundry, maintenance, security staff, drivers … you name it.
In The Bungsu, if you need something fixed – go to Ibu Elsye.
But Ibu Elsye’s work life was not going very well…
Sometimes we have to work on team-level changes. Changes about how to release for example. In this episode we explore one such change, and everything that we need to be aware of when working with team, stakeholders and a process that needs to improve. We may think that team-level changes are simpler or easier than other types of changes, but are they really?
About Umer Saeed
Umer is a Scrum Master, joining us from London, UK, currently working for one of the largest TV broadcasters in the UK, ITV. He has 5 years experience working in Agile environments spanning across Sports, Broadcasting, Travel and Publishing.
Sometimes we do a great job, we help the teams reach a cross-functional collaboration, they are able to release production ready code but… Did we really reach our goal?
Jeff tells a story of a change process where some of the critical ingredients of change were in place, but it was something else that was missing. Listen in to learn about the anti-pattern that revealed itself later on.
About Jeff Maleski
Jeff is passionate about working with and building up both individuals and teams using ideas from Jurgen Appelo’s Management 3.0 and Dan Pink’s Drive. When leading project teams, Jeff strives for empirical based planning and forecasting, continuous learning, and delivering high quality software products that exceed expectations. Jeff believes in leading by actions and focusing on building relationships with others.
In this episode we discuss a step-by-step approach that Lucas took to help him navigate change in an organisation where he worked. We discuss each step, why it is important, and how it helped Lucas in his quest to help the organisation change.
Lucas has been a developer, manager, and agile coach and trainer with Boeing. Currently works a Professional Scrum Trainer with Scrum.org and is the owner of LitheWorks. Lucas enjoys helping people and organizations improve the way they work to be more creative, effective, and efficient.
A software company wins a bid to build a software product. They realise that the time and money they have to deliver that project is way shorter than what they have done in the past. What do you do?
Many companies start their Agile journey in a similar situation. They have chewed too much and it is time to get creative. A few google queries later, and Agile is the next big thing. But now we have two problems: an impossible project and a change process! Listen in to learn how Michael turned the situation around for that client with the help of the team, of course.
About Michael Küsters
Michael helps companies and people become more agile by providing coaching, training and consulting in agile frameworks, principles and mindset.
Michael has consulted for a wide range of companies from small start-up to international corporation, transforming teams, divisions and entire organizations. He is a seasoned veteran with Scrum, Kanban, XP, LeSS and SAFe, Lean and Six Sigma and harnesses this vast experience for his clients’ success.
Michael is a Thought Provoker helping organizations become more agile.