<?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 Huan Huan Huang on Medium]]></title>
        <description><![CDATA[Stories by Huan Huan Huang on Medium]]></description>
        <link>https://medium.com/@huanhuanhuang?source=rss-cc196794f16d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*L4K9D1Myw7bcZyrf.</url>
            <title>Stories by Huan Huan Huang on Medium</title>
            <link>https://medium.com/@huanhuanhuang?source=rss-cc196794f16d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:51:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@huanhuanhuang/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[Example of a social contract]]></title>
            <link>https://medium.com/@huanhuanhuang/example-of-a-social-contract-4ab047cca85e?source=rss-cc196794f16d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ab047cca85e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[social-contract]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Huan Huan Huang]]></dc:creator>
            <pubDate>Fri, 19 Oct 2018 10:35:41 GMT</pubDate>
            <atom:updated>2018-10-19T10:35:41.653Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/941/0*mi5U7Mlsp3tHX2xT" /></figure><h3>Why we need a social contract 📝</h3><p>Speaking of where is it from, the story began with one of our retrospectives.</p><p>Recently, we realized that our speed of moving story across the board has been slower. Lots of stories were waiting for being code reviewed. We brought up a few times before, came up with a solution, but never define a guideline to lead our behaviour. Here is where social contract comes in convenient.</p><p>A social contract is a guideline for the team to make sure we work well together ❤️. It’s like a ring in a marriage. it’s not a real constraint, but it’s more our own commitment to our happy relationship. 💍</p><h3>Meetings</h3><ul><li>🗓 All meetings created in the calendar should have an <strong>agenda</strong> with an expected outcome. We are allowed to decline a meeting without an agenda.</li><li>😎 Nominate a <strong>decision maker</strong>.</li><li>🕓 Be <strong>on time</strong> for attending a meeting. The facilitator should drive 🚙 to finish the meeting in time, stick to the agenda, be as succinct as possible.</li><li>💥 Be aware of a <strong>clash</strong> of the invites. Double check with the people that has a clash if unavoidable.</li><li><strong>📝 Document</strong> the decision, outcomes and actions in confluence if it’s a big one.</li><li><strong>🎯 Focus time</strong> for the team is 11:00 am — 3:00 pm. No meeting during this time for engineers.</li></ul><h3>Communication</h3><ul><li>❓We should <strong>feel safe</strong>. No bullying. It’s OK to ask any question (even if you think it’s stupid).</li><li>🗣 Give constructive/positive <strong>feedback</strong> timely.</li><li>👥 We prefer <strong>face to face</strong> conversation over <strong>slack; </strong>we prefer slack over<strong> email</strong>.</li><li>🎧 When we put on an earphone, <strong>slack</strong> will be preferable over face to face unless it’s a blocker or a fire 🔥 alarm.</li></ul><h3>Agile way of working</h3><ul><li>👩🏻‍💻 Code review has a higher priority. The first thing in the morning ☀️ should be code review or testing, focusing on moving stories across to Done column ASAP.</li><li>📈 Involve analytics in the early stage. All tickets need to have tracking events. Tracking events should be part of the AC or note that tracking is not required. otherwise, the story is not ready to be picked up.</li><li>✅ Any ticket added to the sprint after the planning meeting should go through PM and team lead.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*BYFiJoJ9h_sk7KAf.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ab047cca85e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do I change my mindset from “developer” to “product”]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@huanhuanhuang/how-do-i-change-my-mindset-from-developer-to-product-7f21537874e0?source=rss-cc196794f16d------2"><img src="https://cdn-images-1.medium.com/max/2600/1*bMKebYoDWKS8xlgqUqsCzw.jpeg" width="4256"></a></p><p class="medium-feed-snippet">&#x201C;Product&#x201D; was always in me. I have always wanted to build great products; I care about building a product that is easy to use and adds&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@huanhuanhuang/how-do-i-change-my-mindset-from-developer-to-product-7f21537874e0?source=rss-cc196794f16d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@huanhuanhuang/how-do-i-change-my-mindset-from-developer-to-product-7f21537874e0?source=rss-cc196794f16d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f21537874e0</guid>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Huan Huan Huang]]></dc:creator>
            <pubDate>Tue, 09 Jan 2018 12:12:03 GMT</pubDate>
            <atom:updated>2018-01-09T12:12:03.762Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I am joining SafetyCulture]]></title>
            <link>https://medium.com/@huanhuanhuang/i-am-joining-safetyculture-8d40332a8650?source=rss-cc196794f16d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d40332a8650</guid>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Huan Huan Huang]]></dc:creator>
            <pubDate>Mon, 25 Dec 2017 12:16:28 GMT</pubDate>
            <atom:updated>2017-12-25T12:17:38.735Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sy_4iRbsrg0GsekFKfAs_w.png" /></figure><p>I am very excited when I received the offer. I was on my train home after the 6th round interview. And the HR from SafetyCulture called and told me that the feedback of the interviews were so positive that they don’t think I need to go back for their final interview anymore. They decided to give me the offer. I was chilled to tear.</p><p>Cloe the HR asked me, do you want to accept the offer? I said YES! like a happy girl that accepting a proposal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d40332a8650" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The process vs the right process]]></title>
            <link>https://medium.com/@huanhuanhuang/the-process-vs-the-right-process-3db6aa698c2b?source=rss-cc196794f16d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3db6aa698c2b</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Huan Huan Huang]]></dc:creator>
            <pubDate>Thu, 07 Dec 2017 12:35:33 GMT</pubDate>
            <atom:updated>2017-12-11T12:47:51.024Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The process vs the right process</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/249/1*rK-f010blhEgYooXaSft5Q@2x.jpeg" /></figure><p>It’s not the first time I heard people complain that standup was boring, retrospective has been useless, and pair programming was not easy. Yeah, none of those feel right if we are not doing it right. In fact, it’s so often that we are repeating the same routine periodically that we end up forgetting why we are doing it in the first place.</p><p>Why is “why” important? Because we can reflect the process we are executing has reach our expectation or not. It’s like writing code for your test cases using TDD. Now that your tests failed, does your implementation makes the tests passed?</p><p>If not, we must have done it wrong. Either we need to find a new process or try the process in a new way. Keep exploring and improving. Until one day, all our test cases are passed!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3db6aa698c2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>