Thank you to Tech Lead Journal for inviting me back on again. As always, a great conversation. This time we focussed on remote work and how it’s changing the world.

Reminder for all #engineering #managers. 1 to 1 is team members' meeting, their time and free space to talk and be heard. Don't treat it as project status update. It's not your meeting. Please be mindful. #1to1 #meeting #engineering #em #team #management theengineeringmanager.com/management-101…

My article about running a simple and effective retrospective made it to the latest Tech Lead Digest🔥: techleaddigest.net/digests/111 I'm biased, but if you struggle with keeping your team engaged, you should check it out: notonlycode.org/effective-retr…

Writing code is an expensive way to solve problems. The less code the solution requires and the simpler that code is, the better. — Vladimir Khorikov in Unit Testing Principes, Practices and Patterns.

Time estimates: “Give me one sec” - Within the hour “I’ll be one minute” - An hour or two “I’m on it” - Maybe today "In a bit" - Sometime this week “It’s on my list” - Perhaps this month "Leave it with me" - Possibly never “If I have time” - Never

Programmers must never offer the option of bad code to managers who demand speed. Nobody goes faster when slogging through a mess. Messes slow everyone, and everything forever.

What a Healthy Team Looks Like via softwareleadweekly.com hpdailyrant.medium.com/what-a-healthy…

Turmoil at twitter: here's what's going on at the company, having talked with several software engineers and engineering managers. A free article: blog.pragmaticengineer.com/turmoil-at-twi…

Matthias Schmid Allen Holub. https://linkedIn.com/in/allenholub Kent Beck 🌻 Rule 3. Make regular, steady, and measurable progress against the backlog at all times.

Consent, not Agreement. A group rarely agrees on anything, but consent ("okay, I don't like it, but I can live with it—let's try it") works really well. To have consent, you must have an experimental mindset and a willingness to replace things that don't work—agility IOW.

Wouldn't it be great if we knew ways to make all stakeholders -- product experts, developers, and quality people -- collaborate to plan what goes into the sprint? #technical #agileCoaching #bdd #productManagement #sprintPlanning philippe.bourgau.net/5-whole-team-w…

Working incrementally is vital to doing a great job. Complex systems evolve through a series of many small steps.

Remote pair coaching influence trick#1: Teamwork and collaboration remain crucial for remote work #Agile #technicalCoach #xp #pairProgramming #remote philippe.bourgau.net/5-pair-program…

As we adapted to remote work, we replaced long workshops by successions of shorter and sustainable sessions. #technical #agileCoaching #growthMindset #resilience #sustainablePace #remote philippe.bourgau.net/how-the-pandem…

Retrospective Smells: Blaming benlinders.com/2018/retrospec… #agile #collaboration #english

We gotta learn from kids! Make Believe - sive.rs/mb

Being a servant leader is one of the most difficult path you go through as a manager of your team but I also believe will be the most rewarding thing once you get there #scrum #leadership #engineering #agile scrum.org/resources/blog…

#Remote workshops become a total waste of time when they last longer than 1h30! #technical #agileCoaching #sustainablePace philippe.bourgau.net/how-the-pandem…

NEW POST: Many software teams pack too much work into their iterations. Teams will usually run better when they have deliberate slack, as it allows their delivery to be more predictable and gives them time to improve their environment. martinfowler.com/bliki/Slack.ht…

Some teams don't want coaches to interfere but prefer to practice by themselves. That's when remote self-service and asynchronous workshops shine! #technical #agileCoaching #changeManagement #resilience #remote philippe.bourgau.net/how-the-pandem…