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.
When we visualise the work, how it flows in the organization we discover the real bottlenecks that prevent us from delivering. In this episode we study the case of an organisation that was divided into component teams instead of feature teams. That was discovered thanks to visualisation. But the hard work was about to start. How do we help an organisation transform from component teams to feature teams?
Listen in to hear Jeff’s journey through the change process, and what approaches he successfully used.
About Jeff Bubolz
Jeff is a speaker, trainer, and agile coach. He has been a Product Owner, Scrum Master and Development Team member. Jeff has worked with enterprise companies to small start-ups. His goal is to end human suffering in organizations, by nudging people to be the change they want to see in the world.
Petr has been working with a democratic school in Prague. At first blush it may seem hard to get a democratic school to find a common direction and productive collaboration. After all, isn’t it natural that kids want to skip class? Maybe. But there’s a lot you can do with teachers to help find a better way. In this episode we explore how mixing Management 3.0 practices, Scrum and continuous experimentation brought about a very positive change. Agile works outside IT!
About Petr Holodňák
Petr has a small consulting company where he helps businesses overcome obstacles of ever-faster changing environment, growth problems, stale processes, poor performance, lacking company culture etc. Petr helps companies be more adaptable through empowering their people. Petr also does some pro-bono consulting. Recently for example for a Liberal/democratic school in Prague. His passion is introducing modern management (we can call that “Agile”) to “old school” businesses like heavy industry, manufacturing and so on. Petr wants to help build a brighter future! You can find Petr’s business at: www.cerebra.cz. You can link with Petr Holodňák on LinkedIn.
We talk about change, and change becomes the goal. When we talk about other goals, then those other goals become the topic. In this episode we explore how we can make change happen faster by moving the focus away from change, and more into the business goals that justify the change.
Agile coach from Scrum Data since 2010. Daniel comes from a strong Business intelligence background. He is passionate about large scale product development , organisational structure and culture, being idealistic pragmatist, framework agnostic.
Many organizations are set up around the concept and idea of projects. Projects are the way we get work approved, funded, controlled, and ultimately released. Organizations set up their governance around projects with the customary PMO (Project Management Office) to help perpetuate the governance pattern. But how do we adopt Agile in this kind of environment. This story is about avoiding Death March projects, and what Chad and his colleagues tried to change. It’s a story about how sometimes we are the “insiders” in the change process, and how hard that role is.
Chad’s first experience with Scrum was in 2005 on a global team responsible for consolidating financial software. After some dark days of death march projects, he left his traditional business analyst and project manager roles behind. He is now consulting organizations as an external change agent and organizational agility advisor.