<?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 Kevin Kane on Medium]]></title>
        <description><![CDATA[Stories by Kevin Kane on Medium]]></description>
        <link>https://medium.com/@kevinkane8?source=rss-31cf107aef6f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*U_dIC1kxWyw3zjzh.</url>
            <title>Stories by Kevin Kane on Medium</title>
            <link>https://medium.com/@kevinkane8?source=rss-31cf107aef6f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:59:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kevinkane8/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[Life as Tunaiku’s Product, Data and Engineering Team]]></title>
            <link>https://medium.com/tunaiku-tech/life-as-tunaikus-product-data-and-engineering-team-eeb247bad6b1?source=rss-31cf107aef6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeb247bad6b1</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kevin Kane]]></dc:creator>
            <pubDate>Wed, 18 Jul 2018 13:34:17 GMT</pubDate>
            <atom:updated>2018-07-20T02:29:10.944Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*A4nW1MjjddlzVTIxJVTtpQ.jpeg" /><figcaption>Source : <a href="https://en.prnasia.com/releases/apac/tunaiku-supports-the-largest-technology-community-at-tech-in-asia-product-development-conference-2018-216137.shtml">https://en.prnasia.com/releases/apac/tunaiku-supports-the-largest-technology-community-at-tech-in-asia-product-development-conference-2018-216137.shtml</a></figcaption></figure><p>It has been 4 years since Tunaiku’s first launch. It has been a crazy ride for all of us. It was only 8 people who started it which 2 of them are the Tech guys. There were a lot ups and downs since then, from being <strong>the only player in FinTech Online Lending platform</strong> into <strong>one of the leading FinTech Online Lending platforms in the very crowded red ocean market</strong>.</p><p>From technical challenges and point of view, there were a lot of experimentation, mistakes, refactoring and learning curves we have been through which leads to better platform, culture and solid team. Back then all tech guys were working on 1 single platform/product which was at some points became too big to manage and made us doing bug fixings instead of delivering new features.</p><p>Now after 4 years journey, the number has grown to ~300 people with ~40 people in Tech side. Instead of all people working on 1 single platform/product, we now have small teams who work independently on separate products. Not only that, we also have dedicated Product, Data and Engineering team now instead of 1 big Tech team.</p><blockquote>To always keep hungry and foolish is the most challenging task for us.</blockquote><p>However the journey has not ended yet. There are still long way to go for us to achieve our dream, <strong>200 million smiles in 2025. </strong>As team and as individual, every single of us needs to grow, learn and be better version of us. Quoting from Steve Jobs, “Stay hungry and stay foolish” might be one of the most challenging tasks for everyone of us in this stage.</p><p>If you are looking for an environment which always keep you challenging and provide you an opportunity to learn and implement new stuffs, such as new framework, language, cloud platform etc, <strong>you have to consider to join with us</strong>. To give you perspective how the working experiences in Tunaiku are and why any rockstar talents like you should join us, kindly check the video below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDOnnVa2_7C8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDOnnVa2_7C8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDOnnVa2_7C8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e6538d0016a1d363ae8e687ef747d66/href">https://medium.com/media/3e6538d0016a1d363ae8e687ef747d66/href</a></iframe><p><strong>PS : We are always hiring! Kindly check this for the opportunities </strong><a href="https://career.tunaiku.com/jobs">https://career.tunaiku.com/jobs</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeb247bad6b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tunaiku-tech/life-as-tunaikus-product-data-and-engineering-team-eeb247bad6b1">Life as Tunaiku’s Product, Data and Engineering Team</a> was originally published in <a href="https://medium.com/tunaiku-tech">Tunaiku Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tunaiku goes to Scrum Day Bandung 2018]]></title>
            <link>https://medium.com/tunaiku-tech/tunaiku-goes-to-scrum-day-bandung-2018-94192aaccf4b?source=rss-31cf107aef6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/94192aaccf4b</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Kevin Kane]]></dc:creator>
            <pubDate>Wed, 13 Jun 2018 03:11:34 GMT</pubDate>
            <atom:updated>2018-06-13T06:12:37.316Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UADq8it8P5PxfkwETi7hWw.jpeg" /><figcaption>The-must-to-have group picture post the conference</figcaption></figure><p>As we grow (not only in numbers, but also in responsibilities), we commit to always improve ourselves both in hard skills and also soft skills. There are many ways we have done in order to do so, such as learning from online courses, attending meetups, having a meeting and learning from other organization as well as joining workshops or seminars. This time, we decided to go to Scrum Day Bandung (<strong>#SDB</strong>) 2018 — <a href="http://scrumdaybandung.com/">http://scrumdaybandung.com/</a> to enhance our understanding about Scrum and to be the true servant leaders.</p><p>This is not our first time to attend #SDB, last year we did send 4 people to join and learn from the event. Based from last year experience there were plenty to learn and a lot takeaways to be adopted, therefore this year instead of 4 people, we sent 7 people to join. Each one of them is the representative from their own circle (terms that we use to call our group of talents based on their position, eg: Back-End, Front-End etc). The idea is to have them choosing their most appropriate session based on their circle needs, learning from the speakers, sharing the knowledge with the circle and implementing the takeaways.</p><p>For those who might not familiar with Scrum Day event or at least Scrum Day Bandung’s scheme. The organizer implemented path-based topics which were designed for CxO, Software Engineers, Product people, Scrum Masters or even HR (although in our organization we call them “<strong>People Function</strong>”). By using this scheme, it allows each participant to choose any relevant topics based on their scope of work or their interest. There were 4 paths, such as <strong>Business Development, Technical Excellence, Product Management and People &amp; Culture</strong>. In addition, between each session, participants were able to jump around from one path to another one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*kmmvwrQULHge-bySjs8kKQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*rt7PP1AlC6PWKd_K59EaDA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*H-wPiYQwyJxUvUyNobAqfw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*auHhp-pkB09hwUuUhAbwIg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*GZwe93mo8uwasaGd9T6Vzg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*lQB2t2Fop0idvpTHDRdK0g@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*kIIPGD5hR5DLK-ub9ov1Gw@2x.jpeg" /></figure><p>From all topics were available, our team chose several topics which are :</p><ol><li>STRATEGY PRODUCT OWNER TO MANAGE TECHNICAL DEBT</li><li>SCRUM + KANBAN + DEVOPS + CONTINUOUS DELIVERY</li><li>PRODUCT OWNER VS PRODUCT MANAGER</li><li>DATA DRIVEN PRODUCT MANAGEMENT</li><li>SCRUM FOR BIG DATA PROJECTS</li><li>METRICS FOR MEASURING SCRUM TEAM AND PRODUCT DELIVERY</li><li>AGILE TESTING</li><li>3 PILLARS OF SERVANT LEADERSHIP</li><li>BUSTING THE MYTHS: SCRUM HAS TOO MANY MEETINGS</li></ol><p>From the event itself, there are several takeaways from the conference are :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*3CDjxYGsHsO-QcDRJZ9Aug.png" /><figcaption><a href="http://roneringa.com/wp-content/uploads/2016/06/ExpectedBenefitsPO.png">http://roneringa.com/wp-content/uploads/2016/06/ExpectedBenefitsPO.png</a></figcaption></figure><ul><li>As Product Owner, there are several stages which is sometimes called as <strong>“Evolution of Product Owner”. </strong>5 stages of Product Owner are PO as <strong>Scribe, Proxy, Business Representative, Sponsor and Entrepreneur</strong>. More detailed explanation can be read at <a href="https://www.scrum.org/resources/blog/evolution-product-owner">https://www.scrum.org/resources/blog/evolution-product-owner</a>. In every organization, the terms of Product Owner and Product Manager are used interchangeably. Some organizations prefer to call their <em>Mini-CEO</em> of their Product as Product Manager, some call them Product Owner.</li></ul><blockquote>Hence instead of unifying how organization call this position, we agree to<strong> improve ourselves to be one stage/level ahead from current stage based on the PO Evolution chart regardless our position’s name</strong>.</blockquote><ul><li>To be a Servant Leader means to aspire others and have inspirational visions which others do not share or have. Most people misunderstood to correlate servant leadership with baby-sitting and even doing the team homework. However instead of baby-sitting the team, Servant Leader giving an example to their team (lead by example) and support them from behind. 3 pillars of Servant Leadership are <strong>Natural Feeling to Serve, Aspire to Lead, Grow as a Person.</strong></li></ul><blockquote>Because of the end of the day, <strong>a true leader, did not create followers, they create more leaders and voluntary followers.</strong></blockquote><ul><li>In Scrum, based on Scrum Guide, there are 4 events which are <strong>Sprint Planning, Daily Scrum, Sprint Review </strong>and<strong> Sprint Retrospective</strong>. Most of people are trapped in “<em>Scrum has to many meetings”-</em>mindset after knowing the total events in Scrum or running Sprint for first time. However a lot of people do not realize these events are designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. Furthermore these events are time-boxed events which cannot be executed more than given time box. More detailed read can be found at <strong>Scrum Guide</strong> (<a href="https://www.scrumguides.org/scrum-guide.html">https://www.scrumguides.org/scrum-guide.html</a>)</li></ul><blockquote>Not to mention, the events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94192aaccf4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tunaiku-tech/tunaiku-goes-to-scrum-day-bandung-2018-94192aaccf4b">Tunaiku goes to Scrum Day Bandung 2018</a> was originally published in <a href="https://medium.com/tunaiku-tech">Tunaiku Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>