Thomas was part of a team that had to replace a whole application. They decided to go with the StranglerFig pattern described by Martin Fowler. But, in this case, the pattern was being applied not only to the software, but also to the team, and interaction with the client. Thomas set-up a kick-off for the relationship, and based it on the key aspects we need to take into account as a Scrum Master: team agreement, expectations, vision for the product, and much more! Listen in to learn how Thomas used the first meeting with the client to set up the team’s agile ways of working, and get the customer involved in giving feedback and guidance to the team from day one!
About Thomas van Zuijlen
Thomas is an independent Scrum Master and workshop facilitator from the Netherlands. He believes self-organization, empiricism and facilitation will save the world (of work). A former developer and occasional quiz master with 15 years of experience, Thomas operates in the Netherlands and Lithuania. His weekly newsletter on practical agility can be found at TheBacklog.cc.
Sometimes, when we work with a team, we discover that the changes needed to help the team are needed outside the team. In this episode, we talk about such a situation where Erik was asked to explain Agile to a management team. He took the approach that he would use only what was needed or asked for by management. Listen in to learn about this example of how to introduce a complex topic (Agile) to management without overwhelming them.
Erik is what you get when you take a trained scientist, who mastered Agile as a programmer and is now a Scrum Master. A pragmatic, analytic, systemic and critical personality who is completely focused on understanding the problem. Because once you understand the problem, the solution is easy.
Working through an Agile adoption change in our organizations is always a difficult process, as not everyone will feel the same excitement about the adoption of Agile or Scrum. In this organization, the company had put up posters about Agile, but Wilson quickly realized that the Agile mindset was missing in the teams he worked with. This realization started a process of going through the change and Agile adoption process in a deliberate manner, and Wilson describes the process they adopted for that deliberate change management process.
Wilson is a pragmatic Scrum Master, he has over 15 years in Software development and has worked in different roles, from Support Analyst, Developer to tech lead. Wilson is from Portugal, with Indian origins and currently living and working in the UK with his wife and two daughters.
Jeremia and the team started to work with the c-level team to define a Vision and Mission that would clarify the purpose at his company. With that work, they were able to define a North Star, and start using OKR’s (Objectives and Key Results). He describes for us the process, and the lessons learned introducing OKR’s to focus the company on their purpose.
About Jeremia Riedel
Jeremia is an Agile Coach that describes himself as an Explorer, Enthusiast and Challenger.
There’s a big contrast between some of the Agile values and principles, and the approach that we see implemented when Project Management is the ruling approach to delivering software. Agile and Scrum require that leaders (including Scrum Masters) learn about servant leadership, instead of looking at teams as “school children” that must be managed, and controlled.
In this episode, we talk about the key differences we must be aware between the “old” approach to software development (based on project management ideas), and what Agile is all about.
Gurucharan Padki comes with 18 years of experience in the IT industry, of which he has spent more than a decade in the Agile world delivering products, programs and projects with focus on engineering and quality . He has played the role of product owner, scrum master and agile coach in multiple organizations across India and the world driving transformations.