Konstantin Ribel: Rebuilding Scrum Team Dynamics To Overcome Remote Work Anti-Patterns

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

Konstantin recounts a team's struggle rooted in prioritizing individual tasks over collective effort. Daily meetings centered on status updates fostered a fragmented and siloed work environment. The team working remote made the issue even worse, making it hard to have face-to-face interaction and pair-working. All of these patterns resulted in underperformance. Konstantin advises regular team gatherings, emphasizing the importance of on-site collaboration. He underscores the human element, urging teams to function cohesively as people.

Featured Book Of The Week: The Miracle Morning by Hal Erold

In this segment, Konstantin delves into how his morning routine, inspired by "The Miracle Morning," by Hal Erold has profoundly influenced his role as a Scrum Master. He emphasizes the critical link between personal and professional development, crediting the book "Extreme Programming Explained" for its condensed wisdom. Konstantin highlights Kent Beck's mantra of "do more of what works" and expresses a preference for pair working, acknowledging its occasional impracticality. He consistently applies the insights gained from this book, advocating against the anti-pattern of delayed feedback in his work with teams.

[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!  

About Konstantin Ribel

Konstantin drives organizational success through innovative thinking, simplifying processes, and building high-performing teams. With a strong track record in change management and process optimization, he leads agile transformations and applies systems thinking for adaptable, thriving businesses in dynamic industries.

You can link with Konstantin Ribel on LinkedIn. 

Dragan will share with us his study on optimizing PR and philosophy on async vs sync development. 

Timestamp: 

• 02:20 - Dragan's path to extreme programming
• 04:00 - Dragan's study on the best way to code review
• 11:40 - "how do we keep the cost of code review per line of code constant, as we decrease the size of the PR"
• 12:00 - Synchronous code creation
• 13:40 - Accelerate: Building and Scaling High Performing Technology https://www.amazon.com/Accelerate-Building-Performing-Technology-Organizations/dp/B07BMBYHXL
• 14:30 - Mobbing and pairing for more productive and effective developers
• 16:00 - Deep dive into Dragan's study metrics and insights
• 18:50 - Enable teams to evaluate their current process in a data-informed way
• 20:00 - The results your team can expect from Dragan's study
• 22:30 - Latency in remote vs. co-located teams
• 24:00 - Remote vs. co-located and the tools to enable both
• 28:00 - Psychological safety and positive reinforcing feedback loop in synchronous workflows
• 35:00 - The tools to help you get into a collaboration mode faster
• 38:20 - Asynchronous versus synchronous work
• 39:00 - Fewer delays in communication leads to shorter feedback loops

https://www.slideshare.net/kobac/async-code-reviews-are-killing-your-companys-throughput-248758692

Tester son code est un sujet qui divise et rassemble tout à la fois la communauté des développeurs. Si chacun s'accorde à reconnaître qu'il est indispensable de s'assurer que son application fonctionne comme attendu, les méthodes pour arriver à cette fin diffèrent largement d'une équipe à une autre, quand elles ne s'opposent pas totalement.

Alors que certains sont adeptes du l'extrême programming et du test driven development, d'autres testent directement leur code en production. Il y a ceux qui considèrent que les tests sont une perte de vélocité, tandis que d'autres trouvent que c'est une réduction drastique de temps dans la boucle de feedback.

S'il y a une approche meilleure qu'une autre, comment le savoir ? C'est pour répondre à cette question épineuse que je reçois Fabrice Nourisson. Fabrice est lead developer chez Servebox, et un partisan modéré de l'extreme programming. Nous parlons ensemble des différentes situations qui amènent à réfléchir sur la meilleure manière de tester son code.