In the regular Retrospectives we find the symptoms of the systemic problems we have to face. We can use Retrospectives as the engine to find and create possible improvements to solve those systemic problems. Balazs shares his approach to Retrospectives and some examples of how he applied this approach in his work. We also discuss a critical technique to make the “intangible” problems more concrete and actionable. This technique can take your team from complaining to taking action.
About Balazs Tatár
Balazs is a technical project manager, working for the European Commission in Brussels, Belgium. Currently he plays the Scrum Master role in a support team of one of the biggest web project at the European Commission. He is a former technical lead and fan of open source technologies.
When we start our role of Scrum Master in a new team or organization, Samantha suggests, listen first. Pay attention to the interaction, the way people relate to each other, the language they use. When you know where the pain is, be an agile paramedic. Go where the pain is, help the teams reflect and find their real pains, and possible solutions.
Samantha is a Scrum Master based in London where she works with clients in a number of different industries. In her spare time she is a game writer and designer and uses Scrum to work on game projects.
When we work with organizations and teams that adopt Scrum, we need to have an understanding of what might be the inherent organizational and personal barriers to adoption. There are a number of tools we can use to learn about which barriers are active, and from that generate ideas about what might be the next step.
A Scrum Master who specialises in Mobile and User Centred Design based approaches, Adrian comes from a testing background and he still finds that he champions making testing easier for the teams he works with. Due to that Adrian is also a strong advocate of XP practices (and, from that, BDD)
Systems affect the teams we work with. Systems develop certain patterns – the system conditions – that we must be aware of, and the people in the system also must be aware of. To find and understand those system conditions we need tools, practical tools that help us understand and describe the system conditions. In this episode we review 3 specific tools that help us understand the system conditions we deal with in our role as Scrum Masters.
During this episode we discuss the concept of the Lindy Effect, a useful heuristic that can help us understand the systems we are part of.
About Jacopo Romei
Agile practitioner since 2003, entrepreneur more than once, he has been agile coach in eBay Italia, co-founder of the ALE Network and a former member in Cocoon Projects, an open governance based company. His main focus now are contracts and lean-thinking-compatible agreements.
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.
What are the right questions? In this episode we review some of the critical questions that we must ask to begin to understand the system. The questions may seem easy to understand and even simple to ask, but how do we enable the organization and the people in the team to reflect on those questions?
About Ruben Sadoyan
Ruben has played many different roles in his career. Agile Coach, Team Engineer, Scrum Master with IT Project Management and Software Development background are just some of those. He’s also been an Account executive with software/web development roots and business development, experienced in team and client relationship management.
He’s also launched a startup named Internet Company and has more than 15 years experience in IT. He describes himself as Focused on constant improvement and self-education. Result driven, able to lead in a Lean way, identify root causes and gradually improve teams to make results happen.
There are many techniques that we can use to understand the system we are working with. Oana shares how she uses Open Space Technology to create an environment where the system can reveal itself to us as Scrum Masters and change agents.
About Oana Juncu
Oana likes to present herself as a Business DJ, mixing whatever practices, from Agile and Lean(Startup) to storytelling , User Experience and neuroscience. In her day to day Oana helps teams and organisations unfold creativity, become proud of their achievements, and delight their customers.
You can connect with Oana Juncu on LinkedIn, or follow Oana Juncu on Twitter.
Oana’s website can be seen at coemerge.com.
When we start with our focus totally dedicated to the teams we sometimes completely forget to look beyond. Jason Little shares his journey from team-focus to system-focus and the tools he uses to identify and understand the system.
Woody Zuill discusses systems, and tools to help us understand the system. We also discuss how important retrospectives are, and how to go about increasing the amount, and value of your retrospectives: Just-In-Time retrospectives.
About Woody Zuill
Woody Zuill, an independent Agile Consultant, Trainer, Coach, and Guide and has been programming computers for 30+ years. As a pioneer of the Mob Programming approach of teamwork for software development he has been sharing presentations and workshops on Mob Programming for conferences, user groups, and companies all over the world. He is considered one of the founders of the “#NoEstimates” discussion on Twitter.
You can connect with Woody Zuill on LinkedIn or contact Woody Zuill on Twitter.
If you are interested, check the MobProgramming conference.
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.