<?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 Adeline Hers on Medium]]></title>
        <description><![CDATA[Stories by Adeline Hers on Medium]]></description>
        <link>https://medium.com/@adelinehers?source=rss-e98ebb4fb2bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*NrKxITNaStTx2rK-jHmpeA.jpeg</url>
            <title>Stories by Adeline Hers on Medium</title>
            <link>https://medium.com/@adelinehers?source=rss-e98ebb4fb2bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:42:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adelinehers/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[Success, failure, Agile .. a few learnings from the 2019 Jam London Conference]]></title>
            <link>https://medium.com/@adelinehers/success-failure-agile-a-few-learnings-from-the-2019-jam-london-conference-cfe629bdcf55?source=rss-e98ebb4fb2bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfe629bdcf55</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[jam]]></category>
            <dc:creator><![CDATA[Adeline Hers]]></dc:creator>
            <pubDate>Mon, 02 Dec 2019 11:14:21 GMT</pubDate>
            <atom:updated>2019-12-02T11:14:21.985Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Success, failure, Agile .. a few learnings from the 2019 Jam London Conference</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZmSqVaR9oumJEkC-_GdqoA.png" /></figure><p>A few weeks ago, I attended the Jam conference on product management, hosting a variety of talks from product actors. It was quite a full day and I will share a few thoughts and learnings I took away.</p><p><strong>Make processes work for your team, and not the reverse</strong></p><p>One of the most entertaining yet inspiring session of the day was, to my own surprise, the talk on Agile given by Matt LeMay, who used to be a Product Manager. “ Why is Agile for everybody, and why everybody hates Agile”.</p><p>He addressed some of the <strong>existential</strong> questions we all have about Agile. <em>Is Agile a methodology? A philosophy? What is the right way to do Agile ? Does Agile means speed ?</em></p><p>It was extremely refreshing to hear him argue that (1) None of those questions matter since (2) Agile is a “completely made up things that seventeen people dreamed up on a ski week-end two decades ago”. We often hear people talking about “doing agile”, as if it was a science or a religion, but according to him, ceremonies, sprints, etc … should be used as guidance rather than strict rules. Every product team has a unique dynamic, and the idea is to really ask what is going to work for the team to build better products. Some of those will come for agile standard methodologies, and some be customised to the teams ( even if some could even be associated with the “W” word (waterfall) ). Matt gave a few simple examples of how he applied this mindset to help some of the product teams he worked with : starting a stand up asking team members how they feel today ; when a meeting seems to be an overkill, use a simple deprivation strategy and cancel it for a few weeks, to find out what was really missing without it.</p><p>In any case, I will never waste any more time debating on the “agility” of a certain team, project or company. We need to stop treating the Agile Manifesto as the Bible, and instead focus on smarter ways to make a team work to build the right product. To quote Matt one last time, “Agile is a made up thing. Either find a way to make it useful, or move on”</p><p><strong>Building your product career</strong></p><p>In the opening speech, Mathilde, one of the organisers, referred several times to the concept of serendipity. Serendipity is, according to the Cambridge English Dictionary, “the <a href="https://dictionary.cambridge.org/dictionary/english/fact">fact</a> of <a href="https://dictionary.cambridge.org/dictionary/english/finding">finding</a> <a href="https://dictionary.cambridge.org/dictionary/english/interesting">interesting</a> or <a href="https://dictionary.cambridge.org/dictionary/english/valuable">valuable</a> things by <a href="https://dictionary.cambridge.org/dictionary/english/chance">chance</a>”. That concept resonated particularly well for me, who have always felt I ended up working in product after a series of “accident”. I have often heard people say they realise they have been working in product for a long time, they just did not have the name in their job title. This is probably true for a lot of jobs / careers, but I feel it is very much the case for product, as there is a multitude of companies, roles and product (start up, software, apps , banks, …). In that context, it can sometimes feel overwhelming to decide what choices to make in order to develop the right skills. From a few of the conversations I had on the day, it made me realise that lots of people have little idea either. In one of the panels, Jane Honey, Product Director at Intercom mentioned that she had had more than 20 jobs in her life, from being a journalist, nurse and producer : she looked back at all those positions and was able to identify transferable skills that applied to her current product role in each one of them. There is no “right” product career paths, and it is reassuring to know that many roads can lead to many destinations.</p><p><strong>Success and failure, why it is not all black and white</strong></p><p>Later on the day, Susana Lopes explored with us the concept of what she called her <strong>shadow career</strong>. She explained that despite her long quest for building the perfect products, her products have failed multiple times. Each time she would fail, she was questioning herself, going in a completely different direction . She has, as you would imagine, learnt from her mistakes and improved, but most importantly, after years of doubting herself, capabilities, she has also managed to detach herself to the failure of her products : “ Your product failed, you did not fail”. Many factors can explain why a product does not deliver as expected, despite best efforts, and we are often unable to see it objectively during the build.</p><p>If on the other side of the Atlantic it seems usual to hear people talking about their failure and the lessons it gave them, this trend does not seem to have reached Europe yet, and often people hide their “shadow career”. Surfing on this wave, the founder of Autopsy introduced the data and research product they have created, collecting data from start-up who have collapsed, with the idea of being able to diagnostic the “causes of death” and prevent future debacles.</p><p>Both those talks were very liberating and encourage us to <strong>separate product-worth from self-worth</strong>.</p><p>This is just a snapshot of some of the ideas that were explored, there was many other interesting talks that day, with stakeholders from Instagram, Mail Chimp, Transferwise …. I would recommend anyone interested to attend to the one next year in London, or Barcelona.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfe629bdcf55" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>