<?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 Adarsh Muraleedharan on Medium]]></title>
        <description><![CDATA[Stories by Adarsh Muraleedharan on Medium]]></description>
        <link>https://medium.com/@adarsh.muraleedharan?source=rss-913634c28fda------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Adarsh Muraleedharan on Medium</title>
            <link>https://medium.com/@adarsh.muraleedharan?source=rss-913634c28fda------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:08:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adarsh.muraleedharan/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[2020 Reflections]]></title>
            <link>https://medium.com/momenton/2020-reflections-52f02d00f583?source=rss-913634c28fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/52f02d00f583</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Adarsh Muraleedharan]]></dc:creator>
            <pubDate>Mon, 15 Feb 2021 00:38:27 GMT</pubDate>
            <atom:updated>2021-02-15T00:38:27.542Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we outperformed in a crisis</h3><figure><img alt="Mountain reflection on a lake" src="https://cdn-images-1.medium.com/max/1024/1*Do9CZwR135PblEL70QMLOQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@paulgilmore_?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Paul Gilmore</a> on <a href="https://unsplash.com/s/photos/reflections?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>2020 was a hard year for the world. We were faced with challenges like never before; this blog will talk about my experience joining a new organisation and how we as a team overcame the challenges and even surpassed our performance in the pre-covid world.</p><p>In early March 2020, I joined Momenton. I was excited, a new role and a new chapter in my career. However, I had absolutely no idea of what was in store for me or the rest of the world in 2020. When Covid-19 was announced as a global pandemic, there were rumours of a pending lockdown in Melbourne. So we decided to trial the whole team working from home for two days in preparation. Almost immediately after this trial, a state of emergency was declared. The client I was consulting with invoked its Business Continuity Plan, it’s premises were locked down, and we all had to work from home. So here I am, having just joined a new company and haven’t even been in the office for 2 weeks.</p><p>My role at this client is helping two different squads in delivery and ways of working; one was following scrum where the squad had a specific customer segment, a mission and a clear road map. The other squad was in the final stages of a large initiative and had been following the Kanban methodology and were yet to define a roadmap beyond that. I found it hard to do a lot of context switching as the two squads were entirely different from each other. However, both the squads were operating in a co-located model, used a physical board to visualise the work and had a certain rhythm which was disrupted by remote working.</p><p>During the initial stages of remote working, we had acknowledged that there would be a dip in productivity and we started monitoring the throughput, and cycle time more closely. Lack of face-to-face conversation also meant that the team initially found it hard to stay in sync and facilitate a certain discussion that involved brainstorming or drawing board. Overall it was almost as if we were starting as a new team. Unlike in an office environment, we did not have the opportunity to just stand up or walk up to a team mate and clarify something; hence things took a little longer than before. Both the teams were also working on features that were considered ‘covid-appropriate’ as they were expected to enable self-service for customers and reduce calls to the call centre or visits to the branch. This applied additional pressure to deliver these features.</p><p>We moved all our ceremonies, including stand-ups, planning sessions, refinement, retrospective into a major online meeting platform and used Jira to visualise the work and stay in sync. We would then refer to the digital boards via screen share to facilitate the ceremonies and stay focused on the goals. Digital solutions that can be used to scribble and share ideas were identified and socialised.</p><p>We also organised a brown bag for the teams on Remote Working as by then we knew it was to stay for a while. The session covered 3 aspects of remote working, mental, physical and technical wellbeing and the challenges and opportunity this entails. It was important to discuss this as the sudden lifestyle changes, and being isolated could harm your professional and personal life.</p><p>Under mental wellbeing, we discussed how we could protect ourselves from loneliness, stress and anxiety, the importance of allowing time for things you really enjoy doing, making personal connections and staying informed. Physical wellbeing was more about ergonomics, monitoring screen time, getting out and staying physically active. Lastly, we spoke about technical well being and maintaining productivity, the importance of setting up work life boundaries, staying relevant and securing sensitive information from potential threats. We also discussed the opportunities that this brings and how the team can benefit from this.</p><p>We started an informal session every week to come together and use the time for team bonding. We would either play online games, have a trivia or just chat about a topic that the team really enjoys. There are plenty of resources online. Something that we really enjoyed was the Aliens game. In this game, we assume that Aliens have landed, and we have to explain to them what we do in our teams using pictures. This game was very interactive, and it was really fascinating to see how creative some of our team members were, and also the fact that a lot of them had similar ideas or concepts.</p><figure><img alt="series of pictures explaining banking system in layman terms" src="https://cdn-images-1.medium.com/max/480/1*v7hYGVspIbEV5_PX90xTkw.jpeg" /></figure><figure><img alt="series of pictures explaining banking systems in layman terms" src="https://cdn-images-1.medium.com/max/480/1*JuYk8Moc6HLQP_7QW_WE1w.jpeg" /><figcaption>Our superstar engineers explaining what we do with pictures</figcaption></figure><p>During our sprint planning, we also set up a stretch goal for the team to do physical activity everyday. There was no individual goals but only team goals just like our sprints. As long as we achieve that as a team, the goal is met. The idea was to encourage each other and work as a team. This also involved a lot of banter which was important to build a social aspect to the team. The challenge was to avoid inertia and be able to do things differently. Once we did a retro where everyone had to reflect on the last sprint using GIFs, and we thoroughly enjoyed it. These initiatives also helped me personally get to know the teams, and it’s dynamics and fit in quickly and be a crucial part of the team.</p><figure><img alt="simpson holding a magnifying glass" src="https://cdn-images-1.medium.com/max/480/1*JcqCFuZXn0810M7IvW-1_Q.gif" /><figcaption>D’uh</figcaption></figure><p>During the early days of remote working, we also observed a lot of questions and clarifications while the story is In Progress or In Test, which started to impact our cycle time. We also observed that we were not having story kick- offs, resulting in gaps in understanding a story. So we re-emphasised the importance of story kick-off, ensured that it was happening for every user story and was attended by a Developer, Analyst and/or QA. We encouraged the teams to do some background work before meetings/workshops to facilitate decision-making and outcomes. The team was encouraged to demonstrate more autonomy and make quick decisions as opposed to beating a dead horse. In the middle of the sprint, if someone has finished all their stories, we would consider how they can help others in the squad finish their stories rather than adding more stories.</p><figure><img alt="Cycle time report showing average, standard deviation and median" src="https://cdn-images-1.medium.com/max/795/1*yMoCj1usoU1qQba2EaYZnQ.png" /><figcaption>Cycle time report</figcaption></figure><p>When the team reported challenges with the distribution of code reviews, we started using Github metrics that provide the team with more insights into their delivery process. This provides more insights on the feedback process, number of commits, size of the pull requests and time taken to approve and merge.</p><figure><img alt="Graphs explaining code review turnaround time and size of the pull request" src="https://cdn-images-1.medium.com/max/632/1*RR0ToSn5P2FtIPAE7mqnmA.png" /><figcaption>Github Insights</figcaption></figure><p>We also revised our working agreement to make it appropriate for remote working. All this culminated in our team understanding each others strength and started leveraging the same to the team’s benefit. We also organised feature workshops with the delivery partners from other areas of the organisation to make sure everyone is onboard, committed to the feature, understand the expectations from each of them and agree how we work to deliver the features to our customers. This was really critical as cross tribe delivery and alignment had been a bottleneck in the past. We also created powerful metrics and dashboards to measure the progress of the work. As a result, we were able to run Scrum of Scrums more effectively and had complete transparency of the work happening across the different squads helping us identify and address any issues right away.</p><figure><img alt="an example of a working agreement that explains what is encouraged and what is not" src="https://cdn-images-1.medium.com/max/1008/1*squ89DgFvPXH0wJ0pDCyuA.png" /><figcaption>Working agreement</figcaption></figure><p>The team’s throughput started to rise again as we addressed the initial hiccups, embraced the new working model and finally found the rhythm again. We delivered some really great features while working remotely and one of them was delivered in less than 6 weeks from discovery to customer launch. Most importantly we had fun doing this, so much so that as soon as we deliver one feature, we can’t wait to start the next feature at full throttle. And today our throughput is more than what it was before we started working remotely.</p><p>What stands out the most is the people I had the chance to work with. We have some really capable individuals who demonstrate high morale and work ethics. Now that we are working out plans to open offices and what the future working model will look like, I can’t wait to sit down and have a coffee with the people that I have been working remotely with for the past 10 months and meet some of them for the first time.</p><h3>Summary</h3><p>This whole experience has challenged us but has also made us stronger and ready for the future working model. We have also learned to appreciate the positives of both remote working as well as working from the office. As we move forward there will be other challenges but we will face into them as team and come out stronger on the other side.</p><p>Reach out to hello@momenton.com.au to understand how Momenton can help your organisation with new remote ways of working and how we can help you deliver your product faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52f02d00f583" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/2020-reflections-52f02d00f583">2020 Reflections</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>