<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Meeting on Ivan Luminaria</title><link>https://ivanluminaria.com/en/tags/meeting/</link><description>Recent content in Meeting on Ivan Luminaria</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 27 Jan 2026 08:03:00 +0100</lastBuildDate><atom:link href="https://ivanluminaria.com/en/tags/meeting/index.xml" rel="self" type="application/rss+xml"/><item><title>Standup meetings: why they only work if they last 15 minutes</title><link>https://ivanluminaria.com/en/posts/project-management/standup-meeting-15-minuti/</link><pubDate>Tue, 27 Jan 2026 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/project-management/standup-meeting-15-minuti/</guid><description>&lt;p&gt;First Monday of the project. New team, new methodology, new hopes. The PM proposes a daily standup. Everyone nods. &amp;ldquo;Fifteen minutes, standing up, three questions. Simple.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The first week works. At 9:15 it starts, by 9:28 everyone is back at their desk. Each person speaks for two minutes, blockers are flagged, people move on. Pure efficiency.&lt;/p&gt;
&lt;p&gt;The second week someone raises a hand mid-round: &amp;ldquo;Can I quickly explain the problem I&amp;rsquo;m having with the integration?&amp;rdquo; Five minutes of technical discussion between two people. The other six stand there listening to something that doesn&amp;rsquo;t concern them.&lt;/p&gt;</description></item><item><title>The Yes-And technique: how I defused a meeting that was about to blow up</title><link>https://ivanluminaria.com/en/posts/project-management/tecnica-si-e-yes-and/</link><pubDate>Tue, 13 Jan 2026 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/project-management/tecnica-si-e-yes-and/</guid><description>&lt;p&gt;It was a Thursday afternoon, one of those meetings that was supposed to last an hour on paper. Seven of us, connected on a call. The agenda was straightforward: decide the migration strategy for an Oracle database from on-premise to cloud.&lt;/p&gt;
&lt;p&gt;Straightforward, sure. On paper.&lt;/p&gt;
&lt;p&gt;Twenty minutes in, the meeting had turned into a duel.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="-the-spark" class="relative group"&gt;🔥 The spark &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#-the-spark" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h2&gt;&lt;p&gt;On one side was the infrastructure manager. Experienced, twenty years of datacenters behind him. His position was rock-solid: &lt;strong&gt;lift-and-shift migration, zero changes to the architecture, we move everything as-is&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>