<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Felipe Palomaro on Medium]]></title>
        <description><![CDATA[Stories by Felipe Palomaro on Medium]]></description>
        <link>https://medium.com/@fpalomaro?source=rss-573850b7129d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Wif0bBtsOxFb1vd_1HXIAw.jpeg</url>
            <title>Stories by Felipe Palomaro on Medium</title>
            <link>https://medium.com/@fpalomaro?source=rss-573850b7129d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:05:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fpalomaro/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Agile House Cleaning]]></title>
            <link>https://medium.com/@fpalomaro/agile-house-cleaning-5f21c405758c?source=rss-573850b7129d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f21c405758c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[experiment]]></category>
            <category><![CDATA[fun]]></category>
            <dc:creator><![CDATA[Felipe Palomaro]]></dc:creator>
            <pubDate>Sat, 15 May 2021 14:22:00 GMT</pubDate>
            <atom:updated>2021-05-15T14:22:00.045Z</atom:updated>
            <content:encoded><![CDATA[<p>I tend to drive my fiancée a little crazy — I do get over excited whenever I’m studying something new or reading any book. Whenever I stumble upon some brand new information my mind goes on overdrive trying to link it with other stuff I’ve learned so far.</p><p>For example, I was reading <em>Sapiens</em> from Yuval Noah Harari and at some point he mentions that studies lead us to believe that when mankind started walking just on our feet, our hips became narrower which might have increased number of mothers dying during labour whenever the baby was too big. So, according to evolutionary theories, mothers giving birth at earlier stages had more chances of having no complications as the babies were more flexible allowing easier pass through the birth canal.</p><p>This was just mind-blowing to me, as I usually mention how it is funny that baby animals are so capable when compared to baby humans. Then this new information came along setting quite a plausible reason to it. “Time to annoy the fiancée.”</p><p>I have been working in a very practical manner with project management since ever, but it took me a while to realize it. Ever since I was an intern, trainee or analyst it didn’t matter what was my exact role I was always looking out to find what could be improved and I made sure that at least my voice was being heard or I was leading the change itself.</p><p>I have being in the automobile and health industries so far, but I’ll have to admit that agile methods are quite new to me. I first learned about it while living a textbook example: I was appointed to join in the final stages of a project that had been ongoing for years, leading a big change for Latin America in the organisation I was in, investing most my hours (and long hours) to ensure smooth transition from one system to another, without any disruption to external and internal customers.</p><h3>One week before Go Live the project was cancelled.</h3><p>The project was managed with waterfall methods trying to comprise processes from 2 strategic and dynamic areas present worldwide and impacting thousands of customers. But, making a long story short, the project had a new kick-off and in a matter of 6 months, Latin America and parts of Europe were live and in another 6 months, USA, remaining Europe and Asia were not only live but the system had been greatly improved. And this was how I came to know about Agile, Product Owners, backlogs, sprints and lots of negotiating to reach what was really a priority.</p><p>Since then life has changed a lot: I got engaged, we bought our first apartment, changed jobs, roles and I have been studying more about project management finally starting to really learn agile and Scrum.</p><h3>Now what?</h3><p>Parts of agile thinking can be implemented to individual work: listing demands, prioritising some for specific time boxes, daily reviewing achievements and obstacles that should be removed to make it all easier among several others. But really implementing agile to drive results require certain people with certain profiles and skills to join you with a common mission, while management is aligned and on board with the plan.</p><p>These conditions might not be available to everyone, but that shouldn’t keep you from learning and applying all theories to practical life as this is a great way to really internalize any knowledge.</p><h3>Time to annoy the fiancée</h3><p>Now that I’m really diving into agile studying all the details, reading about Scrum, all the requirements, supporting techniques and all the smalls steps that might be needed, things start to pile up and tend to become one blurry list of “how to be agile”. The way to fight that is baby steps.</p><p>So, trying to lead my learning experience in an agile manner, I tried to identify the 20% most important structures that were required to simulate a sprint and decided to apply that to our cleaning day.</p><p>Basically we used the following structures:</p><ol><li>Sprint Zero: we created and prioritised the list of tasks that had to be executed, set everything visually using Trello on my iPad (simply with 3 columns: needs to be done, ongoing and done) and aligned on how we would be working.</li><li>Sprints: 1-hour long sprints where we should perform 1 task at a time, from start to end, while we could be working together or in parallel — multitasking was not allowed!</li><li>Sprint Review Meeting: there would be review ‘meetings’ after each sprint for use to share feedback, review what was completed (and what was not — helping us adjust how many tasks would fit following) and identify any obstacles that had to be removed (our vacuum cleaner broke during the experiment).</li></ol><p>Since the exercise was expected to take from 2–4 hours and we were not trying to be the fastest cleaners of all time, we didn’t use multiple other tools and rules as they would take longer the cleaning itself. Remember, the goal was simply to experiment some of the theories and knowledge from studying sessions.</p><h3>Sprints and Learning</h3><p>Sprint Zero was a 10 minutes talk, about how things were supposed to be done. Sprint 1 was badly planned: we added a lot of the backlog items to #1 and at the end of the hour we were only half way done with it. Sprint 2 was more cautious and dedicated to finish leftover from #1. And, final tasks and details were left to Sprint 3 which was finished faster than expected.</p><h3>Although partial and simplified there was a lot of learning.</h3><p>While reviewing Sprint 1, it became very clear that in a real business scenario this same situation could have happened if estimates were not done properly. At home, we simply added what our instincts told us would fit in 1 hour, but is this really far from what we see in companies?</p><p>Sure instinct and scenario fitting from experience are very comfortable places to start when problem solving, but caution is necessary not to jump to conclusions, before actually understanding where you stand. Gathering real data from your current situation and for each issue to be solved or value to be generated will lead you to insights and proper solutions.</p><p>Having this clear it should be taken into account that human beings simply don’t know how to estimate workload in measures of effort or time. We suck :)</p><p>We could spend weeks interviewing and gathering studies and feedback from specialists — using the Delphi technique, which is a very solid method, but overkill for our scenario — or we could use the shared knowledge of the involved team and set weights to each task when comparing one to another. Here there are several methods, such as Planning Poker using Fibonacci Sequence or T-shirt sizes (S/M/L), because as humans, we are good at comparing things! :)</p><p>For the cleaning, we should have simply set S/M/L sizes for the tasks to avoid such off estimate.</p><p>While reviewing sprint 2, we realised that we understood how much work would fit in the hour and we were able to finish all we needed, update our “agile board” and leave for lunch.</p><p>The break was interesting, because even though we didn’t have textually represented what meant to have any of the tasks done, we knew that we should execute from start to end, without multitasking and then put away any tools or products that would no longer be required. The results was that when coming back from lunch, we could start Sprint 3 know exactly what had to be done and carrying no left overs from #2.</p><p>Now, in the place you work, is it always clear the Definition of Done? This is a concept that should be extrapolated outside of agile methods as it gives clarity of what is expected to ensure that any deliverable has been really completed considering its execution, testing, feedback gathering, adjustments and release to an actual internal/external customer. Having it clear before any work starts should avoid re-work or incomplete deliveries.</p><p>After Sprint 3, which we finished earlier than expected, it felt like we were speeding up as we knew that whenever one ended their current task it was good to communicate with the other to see it any help was needed, avoiding multitasking but collaborating to finish faster.</p><h3>Avoid multitasking and ensure collaboration might sound simple, but actually this is when it gets tricky in actual companies.</h3><p>The challenge here goes directly to the structural level of the organisation. While agile teams are always multifunctional and structured around delivering a complete product or feature that adds value to its final customer, the most common traditional organisational structure divides people by specialisation, which leads to having departments like Finance, Marketing, Legal, Sales, etc. and blurring how it is that people’s daily work actually add value to the final delivery that reaches customers.</p><p>While this structure generates longer wait times for processes to flow as each area has its own goals and commitments, paradoxically it also makes it harder for individuals to avoid multitasking as urgencies might come from areas that they are unfamiliar with and it becomes difficult to understand its importance and to apply the Eisenhower matrix.</p><p>One possible start to this solution would be ensuring shared goals among several areas, to connect leaders and multifunctional projects to encourage collaboration between all the employees.</p><h3>Was it worth it?</h3><p>Finally, having powered up the regular house cleaning was great to experience and connect to several different theories and also good to reinforce knowledge. I plan on replicating this exercise with other activities and studies as part of my regular routine from now on.</p><p>How about you? Have you been studying something and wants to validate it? Find a minimal version that can be applied, start slow and repeat until insights start to become clear generating this feedback loop between theory and application.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f21c405758c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>