<?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 Margot Le Rouzic on Medium]]></title>
        <description><![CDATA[Stories by Margot Le Rouzic on Medium]]></description>
        <link>https://medium.com/@margotlerouzic?source=rss-757c5d24b616------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*m-BbI3q_zq7pNpwtHA8xEw@2x.jpeg</url>
            <title>Stories by Margot Le Rouzic on Medium</title>
            <link>https://medium.com/@margotlerouzic?source=rss-757c5d24b616------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:58:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@margotlerouzic/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[Photo essay #1: Kep’s crab market, Cambodia]]></title>
            <link>https://medium.com/@margotlerouzic/photo-essay-1-keps-crab-market-cambodia-408d0cc154a6?source=rss-757c5d24b616------2</link>
            <guid isPermaLink="false">https://medium.com/p/408d0cc154a6</guid>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[newsletter]]></category>
            <category><![CDATA[documentary]]></category>
            <category><![CDATA[street-photography]]></category>
            <dc:creator><![CDATA[Margot Le Rouzic]]></dc:creator>
            <pubDate>Tue, 09 May 2023 05:02:43 GMT</pubDate>
            <atom:updated>2023-05-09T09:24:15.476Z</atom:updated>
            <content:encoded><![CDATA[<h3>Photo Essay #1: Capturing the essence of Kep’s Crab Market, Cambodia</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0jWKeOJqbfVGFTlv_iy5hw.jpeg" /></figure><p>The start of a new adventure has arrived, one in which I’ll communicate the <strong>world’s tales through the lens of my camera</strong>, specifically through <strong>street photography</strong>. Being a street photographer is a unique experience that involves attentiveness to one’s surroundings, discovering the perfect angle, locating bustling areas filled with locals, capturing the vivid colors, scents, and framing the perfect shot.</p><p>In this inaugural edition, I’ll transport you to <strong>Cambodia</strong>, and more precisely to the <strong>Crab Market</strong>, renowned worldwide for its Kampot green pepper. This particular delicacy is known for its exceptional freshness and must be consumed within days or weeks, making it impossible to export as is. Savoring a Kampot green pepper crab against the backdrop of the ocean is an experience not to be missed.</p><p>Rising at 4am to witness the fishermen arrive with an abundance of fresh crabs sporting pink and blue claws filled me with both delight and contentment. I was thrilled to have arrived promptly and overjoyed at the prospect of capturing vibrant shots of the colorful fishing boats.</p><p>After this awe-inspiring sight, I continued on to the next part of my journey, observing the sale of crabs in the market. The market was bustling with activity, with numerous stalls offering a variety of crabs for customers to purchase. Customers could choose to have their crabs prepared on-site or take them home to prepare themselves. It was fascinating to witness the hustle and bustle of the market and the interactions between customers and vendors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2tVOacc5wNlx__qmW49kkg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZRxABBXm4PS_smehPmgwGw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQ62aBEB4TCwIYJN-V48cQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ewBOczrQ7TPcfKTrujFvxA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZP8sacl99gVuhiBJUHtmQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bg7u78Jf6x8Q2QW8_a-wWw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z4c--b2UcrOJjo-NX5YUcw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yMzxdXvDKP1j2EpD8UIfIQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*45Wa_UtSh_8k83lLRwrNTA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4RhDO-JD2-rsSEIuuJzEfQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9CMaRSRJbH1S7UzPWuo4XQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O511qtBwAmuq91f7vawe7A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cRUI3oGgKuSqMT97fnhBFw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-mQo2P3LIPtE9o14R8isVg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ZML6Yoj8Ij_qVdiMwWGrw.jpeg" /></figure><p><em>Photos by Margot Le Rouzic</em></p><h3>Interested in street &amp; documentary photography ?</h3><p>Take a look at this inspiring newsletter offering a new perspective on the world through short photo stories of talented photographers.</p><p>👉 <a href="https://storydrops.xyz/">About the newsletter</a></p><p>Loved this post? Feel free to 👏! Follow my work on <a href="https://www.instagram.com/margot_lrz/">Instagram</a> for more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=408d0cc154a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life in the shoes of a new Full-time Scrum Master]]></title>
            <link>https://medium.com/manomano-tech/life-in-the-shoes-of-a-new-full-time-scrum-master-12dcf5ee6083?source=rss-757c5d24b616------2</link>
            <guid isPermaLink="false">https://medium.com/p/12dcf5ee6083</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[scaleup]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Margot Le Rouzic]]></dc:creator>
            <pubDate>Mon, 09 Sep 2019 11:29:03 GMT</pubDate>
            <atom:updated>2019-10-29T10:16:42.516Z</atom:updated>
            <content:encoded><![CDATA[<p>Becoming a full-time Scrum Master in a new team when you have always been a Javascript developer is kind of challenging. I discovered this role thanks to a marvelous Agile Coach who came to ManoMano one year ago in order to develop agility in the company. In the beginning we had a rotating Scrum Master in each team. Indeed, every 2 sprints (4 weeks), the role was occupied by another team member. Gradually over time, rotations stopped and I dedicated 40% of each sprint to my scrum master role. Eventually, it became my full-time job!</p><p>Here are 10 steps to illustrate <strong>how I managed to take this new role in hand in a few months</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-LGX5K7LbElc3lAcLgrO9g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@nate_dumlao?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nathan Dumlao</a> on <a href="https://unsplash.com/search/photos/job?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Being a watchful observer </strong>👀</h3><p>I’ve become full time Scrum Master of a one-year-old pre-existing team that already had its own habits and processes. It took me 2 sprints (4 weeks) to observe the team, its operations, its ceremonies and its way of working together.</p><p>During this phase of observation, <strong>I didn’t suggest anything to the team</strong>, I just wrote down all my remarks on my side and accustomed the team to my presence. This step is always touchy since I don’t know in advance how the team will react to this new presence, knowing that for some people the Scrum Master’s role is a little blurry.</p><p>After this observation step, I decided to write <strong>a discovery report</strong> <strong>to the team</strong>. It was divided in 3 parts: elements that sparked a positive surprise, elements that aroused a neutral discovery and finally areas of improvement.</p><h3><strong>Organize a coffee break with each team member </strong>☕</h3><p>Before putting anything in place, it is important to know better each team member. In order to do that, I organized an informal appointment with each of them to understand their needs, their expectations and their vision of the team. If, like me, you don’t like coffee, choose a tea time instead! It’s a bit hard at the beginning to organize it since you can be afraid to disturb a person for a quick chat but <strong>I learned that is so useful</strong>!</p><p>I took advantage of this meeting to see if the Scrum Master role was understood and what did they expect from me. In my opinion, the Scrum Master has to detect the temperament of the team members to act accordingly and be the team’s facilitator. The other advantage, and not the least, of this meeting is to come up with <strong>a first bond of trust</strong>.</p><h3><strong>Understand the big milestones and issues </strong>⛳</h3><p>As a Scrum Master you are supposed to focus your attention on issues of first importance that must be tackled. Initially, it’s difficult to recognize them but through retrospectives, daily meetings, or everyday team’s life some big issues stand out from others.</p><p>My best advice is to <strong>take one subject at a time</strong>. If you try to address all the issues at the same time, then too many changes will occur for the team at once. Then, it will be hard to solve them well. To choose a particular one you must order them by priority. The main point is not to consider something an issue because your team doesn’t have it but others do. <strong>If the team works great, no need to change something that is done well!</strong></p><p>The Scrum master must be vigilant to observe and detect the slightest impediment that will disturb or slow down the team. His main role is to be <strong>a servant leader</strong>, helping the team in priority is part of this role. Don’t hesitate during working days to see if everybody is going well without facing any particular bottleneck.</p><h3><strong>Organize and animate the daily meeting </strong>🌤️</h3><p><strong>The daily meeting is a crucial time for the Scrum Master</strong>. He must not radically change it but add new ways of doing it bit by bit through time. There is an exception for a non organized team that needs to establish a structure.</p><p>The daily meeting (also called stand up meeting) has a lot of benefits:</p><ul><li>allow the team to set up the day’s work</li><li>help the Scrum Master to raise impediments if any</li><li>have an overview on the progression sprint</li><li>remind the actions taken in the retrospective meeting</li><li>keep the focus on the sprint goal</li><li>contribute to the team synchronization</li></ul><p>To my mind there is no “traditional” way of doing a daily meeting. Each team in agreement with the Scrum Master can choose the format that they like and that leads to a group dynamic.</p><h3><strong>Review all the ceremonies and meetings </strong>🗓️</h3><p>Each feature team has its own ceremonies schedule. That is why it is very important for a new scrum master to take some time and understand the effectiveness of each meeting. If needed, he will, with the whole team’s approbation, be able to reorganize them. So that the team members don’t feel that they are wasting their time, they must precisely understand the purpose of every meeting.</p><h3><strong>Become a retrospective master </strong>🎖️</h3><p>The big part of the Scrum Master role is to organize the end sprint meeting: the retrospective. For me that’s <strong>the most important ceremony</strong> where the whole team gathers (Developers, Product Owner and Scrum Master) in the same room with the goal to inspect and improve ourselves as a team.</p><p>The scrum master has the possibility to be creative and innovative. The retrospective is supposed to be a moment where each member has the ability to express their feelings on the past sprint. I recommend to take more than one hour for this meeting and highly suggest to use various retrospective formats according to the team’s mood. Be careful to adjust to the team, don’t impose a game if your team prefers to have more traditional meetings.</p><p><strong>The output is a set of actions decided by the team as a whole</strong>. Each action is assigned to a specific member which will be small enough to be achievable in the next iteration.</p><p><em>My favorite inspiration for finding some good formats is the Internet!</em></p><h3><strong>Set up a visual management </strong>📌</h3><p>I’m personally a big fan of that tool ! From my perspective, it’s very important to visualize some information during the daily or easily during the day. That’s why <strong>I always set up a visual management using a whiteboard</strong>. I put on it: the sprint goal, the actions from the retrospective, the burndown, the north star metric, the DoD/DoR, the team members holidays and lots of other relevant things for the team !</p><p>The other benefit is to help having a dynamic stand up meeting since everyone is around the board. Some teams have all their JIRA tickets on it, I prefer to have a screen aside with the software opened to avoid wasting time and doubling actions every single time a ticket moves on the JIRA board.</p><h3><strong>Organize a workshop to define the DoD and DoR </strong>📋</h3><p>If the team doesn’t have a Definition of Ready and a Definition of Done, it’s the Scrum Master role to organize a workshop to define them. The team must know how to determine when a user story is ready and when it’s done.</p><h3><strong>Define metrics to keep your team on track </strong>📉</h3><p>As a Scrum master, you may want to measure the success of an agile team. My favorite metrics are: the team’s mood, the sprint completion, the achievement of the sprint goal, the velocity, the capacity, the bug rate and the technical debt rate.</p><p><strong>Be careful: the success of a team cannot be evaluated only with metrics, </strong>it also depends on their way of working, the overall good communication and harmony, their organization and their understanding of agility.</p><h3><strong>Keep time to think </strong>🧠</h3><p>It’s very important for a Scrum Master to take a step back to detect potential problems or find solutions to those already existing. We have a key position as a full-time Scrum Master since you’re not totally inside the team as a Developer or Product Owner but you’re enough inside to tackle the impediments and have an overview of the processes and global run of the team.</p><p>Keeping yourself up to date with the Agile methodologies is also very important. You can learn and be inspired by lot of things from the Agile community. I personally dedicate time every day to read news and blog articles on several websites (Medium, Xebia, Soat and so on).</p><p><em>The biggest pitfall for a Scrum Master is being too busy and not noticing what is really going on within the team.</em></p><h3><strong>BONUS: Having fun ! </strong>🚀</h3><p>It’s very crucial for the team that the Scrum Master brings happiness and joy in order to have a cohesive team which works more efficiently. He is supposed to come up with new ideas every time and put new things in place.</p><blockquote>A Scrum Master must be a Scrum Master by passion !</blockquote><p>For having tried to be a part-time and full-time Scrum Master, it’s totally different. From my perspective, this role must be taken at 100% and not by a developer neither a product owner nor whoever! The Scrum Master needs to have the time to think deeper on specific subjects and not to try having one or two hours per day or per sprint to help the team.</p><h4>Enjoy your time as a Scrum Master!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AW_NI67G5lhI8AILXRX5Gw.jpeg" /><figcaption>Part of the Scrum Team at ManoMano</figcaption></figure><p>Thanks for reading this article. I’m still learning this new job, any advice or feedback is more than welcome 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12dcf5ee6083" width="1" height="1" alt=""><hr><p><a href="https://medium.com/manomano-tech/life-in-the-shoes-of-a-new-full-time-scrum-master-12dcf5ee6083">Life in the shoes of a new Full-time Scrum Master</a> was originally published in <a href="https://medium.com/manomano-tech">ManoMano Tech team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>