Get Agile #30 | How do you get people to collaborate? | Jim Benson
"The longer you put off talking to your colleagues, the more likely it is, that you're going to have integration problems", says Jim Benson in his conversation with Tomasz Wykowski. They start their conversation with The Collaboration Equation, which is “Individuals x Teams = Value. Jim explains that teams are covered by the Agile movement, and Value is discussed in Lean, but the individuals are somehow forgotten - the way they interact, work with each other, help each other, monitor their work, and are self-aware of what they lend to the team and what they gain from it. Jim defines professionals as people wanting to do the right thing at the right time and wanting to do it better next time. He shows how Value Stream Mapping can help them improve by visualizing their work, pain points, emotions, and confusion. The moment they understand how they cause problems to others they can create their own reasons to collaborate and define the right environment to work as professionals. You can learn more about Jim and his services at: https://modusinstitute.com https://www.linkedin.com/in/jimbenson/ https://moduscooperandi.com/ Jim’s four books: The Collaborative Equation https://www.amazon.com/dp/B0BHXDBG25/ Why limit WIP https://www.amazon.com/dp/B00KRJFS2Y/ Why Plans Fail https://www.amazon.com//dp/B006S3UHGA/ Personal Kanban https://www.amazon.com/dp/B004R1Q642/ Two other books mentioned by Jim during the conversation: Flow by Mihaly Csikszentmihalyi https://www.amazon.com//dp/0061339202 Thinking Fast and Slow by Daniel Kahneman https://www.amazon.com/dp/0374533555 This interview was recorded during ACE! Conference (https://aceconf.com) in Krakow, Poland with support from Pragmatic Talks (https://www.pragmaticcoders.com/resources/pragmatic-talks) Tim’s talk from ACE! Conference 2024: https://www.youtube.com/watch?v=i3OfAzt4V-M.
--------
21:08
Get Agile #29 | Why Agile Teams Need Extreme Programming Practices? | Tim Ottinger
“CI is developers' behavior, it has nothing to do with running Jenkins,” says Tim Ottinger, XP coach from Industrial Logic. Join Tomasz Wykowski, from ProCognita as he interviews Tim Ottinger about the ongoing relevance of Extreme Programming in modern software development. They look at the state of different XP practices, including TDD, CI/CD, User Stories, Swarming, Pairing, and Teaming. Tim explains why these behaviors are necessary for teams to iteratively develop product, and how they differ from “solo ticket processing” commonly used in software development. Tim discusses how XP emphasizes working together, prioritization of the work, and the delivery of end-to-end features. He explains that developers know about 1-5% of the codebase and therefore their work must focus on continuous learning. This cannot be limited to the installation of new tools but requires changes in behaviors. Tim shares insights on fostering a culture of continuous improvement and provides valuable resources for teams looking to elevate their agile practices. You can learn more about Tim at https://www.linkedin.com/in/agileotter/, read his posts at https://agileotter.blogspot.com, and visit the Industrial Logic website at https://www.industriallogic.com/. The Swarm Programming article mentioned in the interview: https://www.industriallogic.com/blog/swarm-programming-with-the-swarm-board/ YouTube Channels mentioned by Tim: Dave Farley Continuous Delivery: https://www.youtube.com/@ContinuousDelivery Emily Bache on TDD: https://www.youtube.com/@EmilyBache-tech-coach This interview was recorded during ACE! Conference (https://aceconf.com) in Krakow, Poland with support from Pragmatic Talks (https://www.pragmaticcoders.com/resources/pragmatic-talks) Tim’s talk from ACE! Conference 2024: https://www.youtube.com/watch?v=P3SDiRMEWLE
--------
29:56
Get Agile #28 | Designing organization with Org Topologies | Alexey Krivitsky
Join Tomasz Wykowski from ProCognita as he sits down with Alexey Kryvitsky, Certified Scrum Trainer, Certified LeSS Trainer, and co-creator of Org Topologies. Together they discuss how to avoid making the implementation of the Agile framework as an organizational goal. Alexey introduces the concept of Org Topologies as a mapping technique to help companies discover where they are, where they want to be, and how to get there. He discusses two dimensions of the map, which are the scope of capabilities and the scope of work. Then he explains each of the four levels on both axis. They discuss the role of the managers in driving organizational development, how they can set their goals, and how their role and responsibility will change when moving to different parts of the Org Topologies map. Alexey also gives examples of how the tool can be used to discuss where the company is and where it wants to be, and how different Agile frameworks can support this development. Learn more about Alexey at https://www.linkedin.com/in/alexeykrivitsky/ and watch his talk from ACE! Conference at https://www.youtube.com/watch?v=-fiY53icUqE&list=PL-u-TkA0wpjdf0mlSNQmiLYw4_r3Yn-NQ About Org Topologies: Org Topologies™, a visual framework-agnostic approach designed to help organizations optimize their structure and processes by focusing on thoughtful organizational design. This helps organizations gain higher levels of adaptability. It provides guides such as Elevating Structures™ to help organizations progress on their transformation journeys with a clear direction toward the target state. Find out more at https://www.orgtopologies.com/ and https://www.linkedin.com/company/orgtopologies/. This interview was recorded during ACE! Conference (https://aceconf.com) in Krakow, Poland with support from Pragmatic Talks (https://www.pragmaticcoders.com/resources/pragmatic-talks).
--------
40:23
Get Agile #27 | Intent-Based Leadership | Jenni Jepsen
Intent-Based Leadership is a way of leading when we give control based on technical competencies and organizational clarity. Created by David Marquet, author of “Turn the Ship Around” it was popularized in the Agile community by Jenni Jepsen. Tomasz Wykowski from ProCognita interviews Jenni, on why Intent-Based Leadership works, and how to apply it. Jenni starts with David’s story on how he learned that one man cannot think for the whole submarine crew. She explains the main concept of Intent-Based Leadership, which is to give intent and take actions, rather than ask for permission and wait. To achieve this, she says, people need to obtain both technical competencies and clarity on the goal. They discuss how it can be used for both leaders who want more autonomy and responsibility on their teams, and team members who’d like to change the way they’re managed. Jenni describes The Ladder of Leadership which starts with “tell me what to do” and moves up through “I see…”, “I think…”, “I’d like to do…”, and “I intend to do…”. She shows that the last step is when employees don’t have to wait for permission. During the conversation, they look at how leaders can develop their skills and how they can understand their triggers to avoid returning to old behaviors under stress. They cover the development of competencies and how to ensure the right information is available when people are making decisions. Jenni company page: goAgile.dk Her book: TOGETHER – How leaders involve & engage people to get great things done https://www.amazon.com/TOGETHER-leaders-involve-engage-people/dp/B08NRP13R4 More on Ladder of Leadership: https://www.youtube.com/watch?v=9zOqFe1nTZc David Marquet's website: https://davidmarquet.com His book: Turn the Ship Around! https://www.amazon.com/Turn-Ship-Around-Turning-Followers/dp/B08V4TFFCK/ This interview was recorded during ACE! Conference (https://aceconf.com) in Krakow, Poland with support from Pragmatic Talks (https://www.pragmaticcoders.com/resources/pragmatic-talks) Jenni keynote from ACE! Conference 2024: https://www.youtube.com/watch?v=tyg6wuRAJTs
--------
37:23
Get Agile #26 | How to start LeSS adoption? | Viktor Grgic
“You need to make a distinction between which direction you’re going and what you’re going to do as a first step,” says Viktor Grgic, Certified LeSS Trainer. In this episode of the Get Agile podcast Tomasz Wykowski from ProCognita talks with Viktor about his approach to LeSS transformations. He shares his experience in finding people responsible for organizational structure, with whom he starts conversations on the identification of the problems to solve, not the symptoms to address. Victor explains how he educates decision-makers on the root causes of the current situation and helps companies identify the starting groups. He shows how the feature team adoption map helps define the first steps in the LeSS adoption, and how the team self-designing workshops are used to define new company structure. Companies finish the workshop with both clear goal in mind and the first steps to take, or where they want to be in one year. Viktor emphasizes why owning the change by the group is critical to the success of the transformation, and why the most difficult part of the adoption happens after the workshops. You can learn more about Viktor at: https://www.linkedin.com/in/vgrgic/ His talk from the AgileByExample 2023 conference in Warsaw, Poland: https://www.youtube.com/watch?v=wht5CbGFE9A