This is a great question👇. First, automated tests should be small and fast, so they don't appreciably increase development time. If you're doing TDD, you no longer need to use a debugger and the odds of creating correct code out of the gate are much higher. The code will also be the minimal code needed to get the job done, so you don't waste time writing code that's never executed. Mix in mobbing and you'll rarely have to rewrite or debug stuff and you can dump code review entirely. When fast automated tests are in place you can write code much faster because of the assurance that new code hasn't broken anything. As an added benefit, comprehensive tests remove almost all stress from programming, and that tiny thread of continuous worry is much more debilitating than ppl usually imagine. Tests also serve as runnable documentation and specification. They provide a rich set of examples of how you intend the code to be used, and those examples are guaranteed to be correct (provided that you run your tests 😄)
I hear lots of panicked questions about what to do if you're done with the work before the end of Sprint or if you have work still to do. Ppl say they have to estimate better. NO! Just dump the Sprints. Work on one _small_ thing at a time as a whole team. There. Problem solved.
Every PM should know these websites! 👇
1️⃣ learningloop .io: HUGE collection of product playbooks and case studies
2️⃣ stare.softr .app: hundreds of in-depth product teardowns
3️⃣ untools .com: collection of thinking tools and frameworks
Share it with your friends! Thanks 💙
Stop wasting time with random PM content.
I've spent >100 hrs curating:
🔹 60 all-time best resources
🔹 Sequencing them for impact
🔹 Writing q's for maximum learning
Soon, I'll make this a course for $149.
For the next 24h: FREE!
Follow + RT + comment "60" and I'll DM.
@esiuclm@inetum_es Os dejo por aquí el hilo donde respondo en profundidad a todas las preguntas que realizaron los alumnos. Un saludo y gracias por la difusión!
https://t.co/jO2ny7RHUp
When teams believe "the goal" is to finish all the stories in a Sprint, they start focusing on work, not impact on customers.
When we focus on work only, more work emerges and we have no way to manage/scope it out. Because the goal is, effectively "more work" #NoEstimates
Encantado de aportar mi granito de arena en la escuela donde me formé y con muchas ganas de compartir y hablar de agilidad, seguro que pasamos un buen rato!
🎙️Mañana nos visita Lucas González @lucasGlezM de
@inetum_es para impartir la conferencia "Gestión Ágil de Proyectos como catalizador de equipos de alto rendimiento". 🗓️A las 11.30h en el Salón de Actos Alan Turing
Disfrutando con Belén Olier y su charla sobre cómo los modelos mentales esconden las razones por las que un gran cambio puede fracasar. Aprender a reconocerlos es clave para trabajar el pensamiento sistémico tan necesario en grandes procesos de cambio. #cas2022#inetumcas2022
Arrancamos con Bas Vodde cocreador de @less_works que nos va a contar que las dependencias lejos de ser el mal son necesarias para que los equipos trabajen como un UNICO equipo creando un UNICO proyecto colaborando y aprendiendo unos de otros. #cas2022#inetumcas2022