Tim Bourguignon's guest appearances

Tim Bourguignon

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Software Developer's Journey

Untold Developer Stories

Jason Lengstorf

Cassidy Williams

Chris Coyier

Ines Montani

Linda Liukas

Jerome Hardaway

Wes Bos

Katrina Owen

Carl Franklin

Taylor Otwell

Matt Biilmann

Guillermo Rauch

Woody Zuill

Greg Koberger

Laurie Barth

OwlTail

BONUS: From Scrum Master to Engineering Lead, how to prepare the transition with Tim Bourguignon   We start this episode, reflecting on Tim’s journey of realizing the importance of working collaboratively and embracing agile methodologies. Tim noticed early on that he drifted to teaching and providing assistance to others rather than actively developing software. After a while, he moved to consulting in Agile, and in that role, he noticed recurring patterns and struggled with unclogging processes that seemed to be missing something crucial. Over time, frustration set in. He felt like he was fighting an uphill battle and highlighted the disruptive nature of Agile, which aimed to uncover and solve problems but often revealed bigger and deeper underlying issues.   The big problem with Agile adoption, and what we can do to prepare for it   With time and experience, Tim realized that leadership was a crucial factor in the team's success. He observed a recurring pattern where leadership was either blocking progress or not fulfilling their role effectively. This realization led him to recognize the significance of leadership's involvement and the impact it had on the overall performance of the team.    From developer, to coach, and finally to leader: learning to help teams at all levels of the organization   Tim shares his journey at WeMaintain and discusses the challenges of scaling while maintaining agility. Before joining, and during the interview process, Tim already sought to identify the problems he could help solve but couldn't pinpoint a specific issue. His boss expressed concerns about managing fast growth while staying agile. Initially, WeMaintain had two teams working efficiently from a backlog, releasing frequently, and measuring their progress. But, they wanted to grow the company without resorting to a traditional approach of multiple teams working on the same problem, which often led to communication issues. Instead, they advocated for compartmentalized teams with strong ownership and defined success metrics for each team based on specific business streams. Each team had the necessary skills and accountability to achieve their success metrics, ensuring a shared responsibility for success.   From coach to leader, and the critical lessons learned on the way   Tim reflects on the differences between his current approach and what he observed in the past, when he was the coach trying to help teams and organizations. He emphasizes the importance of taking personal responsibility as a leader when facing problems within a team. Previously, their clients would assume that the leaders were right and focused only on changing the teams, and he wanted to avoid that anti-pattern at all costs. Tim shares the tip of starting with leadership and establishing a clear vision, emphasizing the impact of lacking a clear vision and passionate individuals on the organization. When it comes to reflecting on our performance, Tim recommends evaluating oneself against the 12 principles of the Agile Manifesto and highlights the necessity of enabling developers to communicate directly with customers to foster agility.   Scaling with Agility: Building Compartmentalized Teams and other strategies for growing companies, and staying Agile   Tim’s current focus is on  stream-aligned teams and metrics. Tim recommends   the book "Team Topologies", whose authors have been guests on the podcast. Tim also shares the tip of asking teams to create a portfolio of metrics that demonstrate they are working on the right things. Various teams have found interesting metrics to track their progress. The  PDCA cycle  and  DORA (DevOps Readiness Assessment) metrics  are mentioned. The guest highlights a positive sign of organizational health, with a rate of 1.5 deployments per day across the entire product group. They suggest having frequent discussions with people throughout the organization and implementing practices like showcasing Monday morning deliveries and sharing post-release messages on Slack as early documentation for stakeholders.  The book "Accelerate"  is also recommended for further insights into metrics.  In this final segment, we also refer to  Extreme Programming.

BONUS: From Scrum Master to Engineering Lead, how to prepare the transition with Tim Bourguignon We start this episode, reflecting on Tim’s journey of realizing the importance of working collaboratively and embracing agile methodologies. Tim noticed early on that he drifted to teaching and providing assistance to others rather than actively developing software. After a while, he moved to consulting in Agile, and in that role, he noticed recurring patterns and struggled with unclogging processes that seemed to be missing something crucial. Over time, frustration set in. He felt like he was fighting an uphill battle and highlighted the disruptive nature of Agile, which aimed to uncover and solve problems but often revealed bigger and deeper underlying issues. The big problem with Agile adoption, and what we can do to prepare for it With time and experience, Tim realized that leadership was a crucial factor in the team's success. He observed a recurring pattern where leadership was either blocking progress or not fulfilling their role effectively. This realization led him to recognize the significance of leadership's involvement and the impact it had on the overall performance of the team.  From developer, to coach, and finally to leader: learning to help teams at all levels of the organization Tim shares his journey at WeMaintain and discusses the challenges of scaling while maintaining agility. Before joining, and during the interview process, Tim already sought to identify the problems he could help solve but couldn't pinpoint a specific issue. His boss expressed concerns about managing fast growth while staying agile. Initially, WeMaintain had two teams working efficiently from a backlog, releasing frequently, and measuring their progress. But, they wanted to grow the company without resorting to a traditional approach of multiple teams working on the same problem, which often led to communication issues. Instead, they advocated for compartmentalized teams with strong ownership and defined success metrics for each team based on specific business streams. Each team had the necessary skills and accountability to achieve their success metrics, ensuring a shared responsibility for success. From coach to leader, and the critical lessons learned on the way Tim reflects on the differences between his current approach and what he observed in the past, when he was the coach trying to help teams and organizations. He emphasizes the importance of taking personal responsibility as a leader when facing problems within a team. Previously, their clients would assume that the leaders were right and focused only on changing the teams, and he wanted to avoid that anti-pattern at all costs. Tim shares the tip of starting with leadership and establishing a clear vision, emphasizing the impact of lacking a clear vision and passionate individuals on the organization. When it comes to reflecting on our performance, Tim recommends evaluating oneself against the 12 principles of the Agile Manifesto and highlights the necessity of enabling developers to communicate directly with customers to foster agility. Scaling with Agility: Building Compartmentalized Teams and other strategies for growing companies, and staying Agile Tim’s current focus is on <a href="https://itrevolution.com/articles/four-team-types/" rel="nofollow" target="_blank"> stream-aligned teams and metrics</a>. Tim recommends <a href="https://scrum-master-toolbox.org/2020/03/podcast/bonus-how-to-setup-agile-and-devops-teams-team-topologies-interview-with-matthew-skelton-and-manuel-pais/" rel="nofollow" target="_blank"> the book "Team Topologies", whose authors have been guests on the podcast</a>. Tim also shares the tip of asking teams to create a portfolio of metrics that demonstrate they are working on the right things. Various teams have found interesting metrics to track their progress. The <a href="https://scrum-master-toolbox.org/?s=PDCA+cycle" rel="nofollow" target="_blank"> PDCA cycle</a> and <a href="https://dora.dev/" rel="nofollow" target="_blank"> DORA (DevOps Readiness Assessment) metrics</a> are mentioned. The guest highlights a positive sign of organizational health, with a rate of 1.5 deployments per day across the entire product group. They suggest having frequent discussions with people throughout the organization and implementing practices like showcasing Monday morning deliveries and sharing post-release messages on Slack as early documentation for stakeholders. <a href="https://amzn.to/45jm4LZ" rel="nofollow" target="_blank"> The book "Accelerate"</a> is also recommended for further insights into metrics. In this final segment, we also refer to <a href="https://scrum-master-toolbox.org/tag/xp/" rel="nofollow" target="_blank"> Extreme Programming</a>.

BONUS: From Scrum Master to Engineering Lead, how to prepare the transition with Tim Bourguignon | Tim Bourguignon

Tim Bourguignon is a Chief Learning Officer as well as a podcast host, which means he not only has plenty to say... he also says it in a radio voice.Join us as we talk about what it means to be a mentor as well as some of the many tips and insights Tim has come across during his time as a mentor and podcast host. Also, brief mentions of D&amp;D.Learn more about Tim here: https://twitter.com/timothephttps://devjourney.info/

Tim Bourguignon is a Chief Learning Officer as well as a podcast host, which means he not only has plenty to say... he also says it in a radio voice. Join us as we talk about what it means to be a mentor as well as some of the many tips and insights Tim has come across during his time as a mentor and podcast host. Also, brief mentions of D&amp;D. Learn more about Tim here:  <a href="https://twitter.com/timothep" rel="nofollow" target="_blank">https://twitter.com/timothep</a> <a href="https://devjourney.info/" rel="nofollow" target="_blank">https://devjourney.info/</a>

Tim Bourguignon: Insights from a Serial Mentor and Chief Learning Officer

We first started talking about how I dabbled into the world of computers, mostly through gaming and tinkering. We then talked about my studdies and my wish to go into (buildings) architecture and keen interest into leadership. We discussed the origin of the show and what I learned from it. We discussed my superpower(s) and what use I make of them. We went over the effects of hosting the podcast in everyday life and how I am able to convince.Here are the links of the show:https://www.twitter.com/timothephttps://timbourguignon.frhttps://mentoring.rockshttps://seecfp.comTalk to me 1-1: https://bit.ly/one_on_one_with_timThe host of this show is Amitai Schleier https://www.twitter.com/schmonzhttps://schmonz.com/CreditsMusic Aye by Yung Kartz is licensed CC BY-NC-ND 4.0.Your(regular) hostSoftware Developer‘s Journey is hosted and produced by Timothée (Tim) Bourguignon, a crazy frenchman living in Germany, who dedicated his life to helping others learn &amp; grow. More about him at timbourguignon.fr.The gest-host of this episode is Amitai Schleier, a dear friend and fellow coach, who describes himself as an independent software development coach and speaker, an itinerant programmer, a legacy code wrestler, the host of the "Agile in 3 Minutes" podcast, a musician and finally an (award-winning) bad poet.Gift the podcast a ratingPlease do me and your fellow listeners a favor by spreading the word about this podcast. And please leave a rating on the podcasting platforms. This is the best way to increase the visibility of the podcast. Find all the links here: https://devjourney.info/subscribe.htmlPatreonFinally, if you want to help produce the podcast, support us on Patreon. Every cent you pledge will help pay the hosting billsSupport the show

We first started talking about how I dabbled into the world of computers, mostly through gaming and tinkering. We then talked about my studdies and my wish to go into (buildings) architecture and keen interest into leadership. We discussed the origin of the show and what I learned from it. We discussed my superpower(s) and what use I make of them. We went over the effects of hosting the podcast in everyday life and how I am able to convince. Here are the links of the show:<ul><li><a href="https://www.twitter.com/timothep" rel="nofollow" target="_blank">https://www.twitter.com/timothep</a></li><li><a href="https://timbourguignon.fr" rel="nofollow" target="_blank">https://timbourguignon.fr</a></li><li><a href="https://mentoring.rocks" rel="nofollow" target="_blank">https://mentoring.rocks</a></li><li><a href="https://seecfp.com" rel="nofollow" target="_blank">https://seecfp.com</a></li><li>Talk to me 1-1: <a href="https://bit.ly/one_on_one_with_tim" rel="nofollow" target="_blank">https://bit.ly/one_on_one_with_tim</a></li></ul>The host of this show is Amitai Schleier <ul><li><a href="https://www.twitter.com/schmonz" rel="nofollow" target="_blank">https://www.twitter.com/schmonz</a></li><li><a href="https://schmonz.com/" rel="nofollow" target="_blank">https://schmonz.com/</a></li></ul>Credits<ul><li>Music <a href="http://freemusicarchive.org/music/Yung_Kartz/August_2018/Aye" rel="nofollow" target="_blank">Aye</a> by <a href="http://freemusicarchive.org/music/Yung_Kartz/" rel="nofollow" target="_blank">Yung Kartz</a> is licensed <a href="http://creativecommons.org/licenses/by-nc-nd/4.0/" rel="nofollow" target="_blank">CC BY-NC-ND 4.0</a>.</li></ul>Your(regular) host Software Developer‘s Journey is hosted and produced by Timothée (Tim) Bourguignon, a crazy frenchman living in Germany, who dedicated his life to helping others learn &amp; grow. More about him at <a href="http://timbourguignon.fr" rel="nofollow" target="_blank">timbourguignon.fr</a>. The gest-host of this episode is Amitai Schleier, a dear friend and fellow coach, who describes himself as an independent software development <a href="https://schmonz.com/coach/" rel="nofollow" target="_blank">coach</a> and <a href="https://schmonz.com/speaker/" rel="nofollow" target="_blank">speaker</a>, an itinerant <a href="https://schmonz.com/tag/coding-tour/" rel="nofollow" target="_blank">programmer</a>, a legacy code <a href="https://schmonz.com/2015/02/25/the-when-to-stop-kata/" rel="nofollow" target="_blank">wrestler</a>, the host of the "Agile in 3 Minutes" <a href="https://agilein3minut.es/" rel="nofollow" target="_blank">podcast</a>, a <a href="https://schmonz.com/tag/music/" rel="nofollow" target="_blank">musician</a> and finally an (award-winning) <a href="https://schmonz.com/2007/11/16/explosion-at-the-poem-factory/" rel="nofollow" target="_blank">bad poet</a>.Gift the podcast a rating Please do me and your fellow listeners a favor by spreading the word about this podcast. And please leave a rating on the podcasting platforms. This is the best way to increase the visibility of the podcast. Find all the links here: <a href="https://devjourney.info/subscribe.html" rel="nofollow" target="_blank">https://devjourney.info/subscribe.html</a>Patreon Finally, if you want to help produce the podcast, support us on <a href="http://bit.ly/2yBfySB" rel="nofollow" target="_blank">Patreon</a>. Every cent you pledge will help pay the hosting bills<a href="https://www.buzzsprout.com/190346/support" rel="payment nofollow" target="_blank">Support the show</a>

#100 Tim Bourguignon is a guest on his own show