<?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 Alessio Romito on Medium]]></title>
        <description><![CDATA[Stories by Alessio Romito on Medium]]></description>
        <link>https://medium.com/@alessioromito?source=rss-aa3c4d2b842------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uw9M4E3ING7IWawZdEQwhA.jpeg</url>
            <title>Stories by Alessio Romito on Medium</title>
            <link>https://medium.com/@alessioromito?source=rss-aa3c4d2b842------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:49:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alessioromito/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[How do Story Points help you measure your development speed?]]></title>
            <link>https://alessioromito.medium.com/how-do-story-points-help-you-measure-your-development-speed-2985fd95dbea?source=rss-aa3c4d2b842------2</link>
            <guid isPermaLink="false">https://medium.com/p/2985fd95dbea</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alessio Romito]]></dc:creator>
            <pubDate>Wed, 24 May 2017 14:00:08 GMT</pubDate>
            <atom:updated>2017-05-24T14:03:14.482Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Estimation is a crucial part of software development. By looking at how a team estimate their work, you can already recognise many good (or bad) patterns.</p><p>In a <a href="https://medium.com/@alessioromito/why-doesnt-agile-make-us-go-faster-f12557cf3bc">recent article</a>, I explained why you should measure, and not “expect”, development speed. Today I will dig deeper into how we can actually measure it<em>.</em></p><p>From that article I defined:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HkfK9LMea-XmGUsmnP-4ng.png" /><figcaption>Brackets are used to define the measurement units for a specific quantity.</figcaption></figure><p>In physics, you do dimensional analysis to make sure that you are not mixing apples with oranges. For instance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ms2YyUdSceI3ksYt1-UqQw.png" /><figcaption>You cannot directly compare acceleration and velocity, as they have different measurement units.</figcaption></figure><p>Your equation will be invalid, if you don’t have the same physical quantity on both sides.</p><p>Velocity is not a pure, non-dimensional, number. As a matter of fact, it relates two different quantities, space and time, to each other.</p><p>That’s why we must define <em>Development speed</em> (or <em>velocity</em>) in a similar way.</p><p>Many teams estimate their tasks with time. This estimation is the answer to the (usually million-dollar) question: “How long will it take you?”.</p><p>There are two problems with that: first, development is a non-linear process that can have different result for the same kind of task; second, different people will take different time to complete the same work.</p><p>Furthermore, if you estimate your <em>Scope</em> with time, for example by using “Man days” or “Man hours”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u8Pr6-MBOUyz2aDxdUpbig.png" /><figcaption>You can simplify measurement units when needed.</figcaption></figure><p>You end up with a non-dimensional Development Speed.</p><p>What does that mean? By estimating <em>scope</em> with time, you are not measuring how fast is your development team, but only how good they are at estimating.</p><p>To measure true development speed, you need a different quantity: Story Points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zPVLw8SKMS0ycU4WFFICzg.png" /><figcaption>Story Points, like “Space” (in classical physics), do not change according to the person who has to complete them.</figcaption></figure><p>I recommend <a href="https://www.mountaingoatsoftware.com/blog/what-are-story-points">this article</a> by Mike Cohn if you are not familiar with what Story Points are. His explanation is one of the best I found on the internet.</p><p>Complexity is an intrinsic property of the work you want to complete. It does not change depending on who does it. This means that, over time, your team will develop a common understanding of what does “a Story Point” mean.</p><p>They will build together a way of estimating chunks of work that do not depend on who completes them. Story Points are an intrinsic property of the <em>scope</em> you have ahead of yourself. They do not depend on who delivers the work.</p><p>But where does it all go wrong? Story Points can cause more than a headache when they are not used correctly. They are the result of a team estimation, therefore you should use them for pieces of <em>scope</em> that everybody will contribute to.</p><p>It won’t fly if you try to estimate a back-end task with a UI designer. It will work, however, if you start estimating true user stories that need a bit of effort from every team member.</p><p>As a PO, this is one of the main challenges you will face: to slice the correct amount of <em>scope </em>that can be easily grasped, and estimated, by every team member.</p><p>As you start doing that, you will be able to measure how many Story Points your team can “burn” every sprint.</p><p>Scope over time: development speed. This measure will fluctuate at first, but also become more stable as time goes by.</p><p>You must have two goals in mind: first, to find a sustainable pace of development, and second, to become reliable in your commitments.</p><p>As a developer, this will make you more professional and less stressed. As a PO, you will have an easier time managing the expectations of your stakeholders.</p><p>The only people who will “lose” from adopting this practice are the ones who have a tendency for yelling at the team to blindly <em>go faster</em> and cut corners.</p><p>It’s up to you and your team to counter this tendency, while delivering great value to your customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2985fd95dbea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why doesn’t Agile make us go faster?]]></title>
            <link>https://alessioromito.medium.com/why-doesnt-agile-make-us-go-faster-f12557cf3bc?source=rss-aa3c4d2b842------2</link>
            <guid isPermaLink="false">https://medium.com/p/f12557cf3bc</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Alessio Romito]]></dc:creator>
            <pubDate>Wed, 03 May 2017 13:22:45 GMT</pubDate>
            <atom:updated>2017-05-24T14:06:39.423Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>There’s one sentence that any person who has ever worked in IT has heard at least once: “Development is too slow”.</p><p>Why isn’t “Agile” an obvious remedy to that? Many companies apply Agile frameworks and development practices, and yet, the complaints remain.</p><p>As a former physicist, I like to make comparisons between the problems I encounter at work, and the laws of nature.</p><p>Like any kind of velocity, the <em>speed </em>of development must be the ratio of a <em>space </em>quantity, over a <em>time </em>quantity. Furthermore, two different observers can, and will, perceive <em>speed</em> in two opposite ways.</p><p>If I’m travelling on a high-speed train at 300 Km/h, a car on the highway next to me will look slow, in comparison<em>.</em></p><p>On the other hand, if I were to stand still in the middle of the same highway (please don’t try this), I would feel every car moving at a crazy fast speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*jQSUKERfVSuQrNkV529kIQ.jpeg" /><figcaption>The Shinkansen “bullet train” — by tansaisuketti (CC-BY-SA)</figcaption></figure><p>To make everything more objective, let’s define the <em>speed </em>of software development as <em>scope</em> (space) over <em>deadline </em>(time). By <em>scope</em> I mean “what needs to be done”, while by <em>deadline</em> I mean “time to get the <em>scope</em> done”.</p><p>I mention the word “deadline” because, wether we like it or not, there will always be one. It will either be said out loud, or stay unspoken in somebody’s mind. But it will be there.</p><p>Even an implicit deadline will generate expectations. People will use it to evaluate the <em>speed</em> of development, from their own frame of reference.</p><p>It’s a notion you must accept: without a measure of time there is no “speed”, by definition.</p><p>Our true mistake is to let people outside of the development team get continously biased by their own frame of reference.</p><p>As a matter of fact, to be on the “business side” is like riding a high-speed train.</p><p>Software development, on the other hand, can feel like being stuck in the middle of a highway, where all vehicles threaten to run over you every second.</p><p>Mutual understanding of each other’s frame of reference is of paramount importance.</p><p>Business stakeholders tend to expect a certain speed of development, instead of measuring it. This should not surprise you: once <em>scope</em> and <em>deadline </em>are set, you already have a <em>speed</em> to be compared against.</p><p>It’s as easy as saying “if I want to cover 200 Km in one hour, I will need to travel at an average speed of 200 Km/h”.</p><p>However, forcing a car to travel at a certain high speed is a recipe for disaster. Especially if your car is guaranteed to be reliable only at a lower speed than the one you set. You can either have an accident, or, on the long run, a series of mechanical failures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*gqKty3QEtynFmYeH_0D9Qw.png" /><figcaption>Understanding this simple equation can yield substantial benefits to your organisation.</figcaption></figure><p>How does an Agile framework help you in this situation?</p><p>Let’s use Scrum as an example. Once you adopt it, you let the team find the fastest speed that optimizes their reliability (a.k.a. “sustainable pace”), and then see in how much time you will be able to complete your <em>scope</em>.</p><p>This comparison is very easy to understand, and goes straight to the point. You need to let the team find their own pace, measure it, and only then use this data for your planning sessions.</p><p>Your business people will understand. You will not simply tell them that they are wrong. You will show them how to look at a single problem with different eyes.</p><p>Once they understand that <em>speed</em> is something you measure, most of the work is done. As any kind of measure, the more often it’s updated, the better. That’s why, in Scrum, you have frequent “checkpoints”.</p><p>Every day, at the stand-up, and every sprint, during the Sprint Review, the team passes a checkpoint. You can both measure how many tasks get delivered, and get an educated idea about the team’s pace.</p><p>As soon as you have that, it will be easy to compare their pace to the theoretical one you (or anybody else) had in mind.</p><p>To sum up: let the developers find their own pace, <a href="https://medium.com/@alessioromito/how-do-story-points-help-you-measure-your-development-speed-2985fd95dbea">measure their speed</a>, and use it as a health check for your original plan. Rinse and repeat this, every day and every sprint.</p><p>You want to increase transparency as much as possible. In this way, the team and their stakeholders can, over time, build mutual trust. Everyone will benefit from it. The old days of frustrating conversations and unlikely explanations will be over.</p><p>Collaboration will always yield better results than confrontation. A mindset that follows the Agile principles will get you there.</p><p>Start today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f12557cf3bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Road to Agile — Part 3: Skip the tutorial]]></title>
            <link>https://engineering.hellofresh.com/road-to-agile-part-3-skip-the-tutorial-b266c1fb5dc5?source=rss-aa3c4d2b842------2</link>
            <guid isPermaLink="false">https://medium.com/p/b266c1fb5dc5</guid>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[Alessio Romito]]></dc:creator>
            <pubDate>Thu, 06 Apr 2017 14:55:36 GMT</pubDate>
            <atom:updated>2017-04-06T14:55:36.623Z</atom:updated>
            <content:encoded><![CDATA[<h3>Road to Agile — Part 3: Skip the tutorial</h3><p>After a brief introduction to HelloTech and its status quo, today we will take a look at the first concrete changes in the way our teams work.</p><p>My first idea was to avoid long workshop sessions about “how to do Agile”. Instead, I used a <em>“skip the tutorial”</em> approach: we gather feedback, implement changes, and iterate. This seemed appropriate as the business pressure on the teams is very high, and it doesn’t cause any significant dip in productivity.</p><p>With all this in mind, it was important for me to have an initial “observational” phase. This way, I could quickly gather useful proposals for the teams, and gradually introduce them to Agile best practices.</p><p>I decided to focus on the Product Owners first. Why? If you compare software development to the flow of water through a pipe, the Product Owners will be responsible of ensuring a reliable and predictable water intake.</p><blockquote>You cannot expect the output of a certain workflow to be good, if the input is not good as well.</blockquote><p>Or, put more concisely:</p><blockquote>Garbage in, garbage out.</blockquote><p>Depending on their actions, Product Owners have largest impact on the efficiency of their teams.</p><p>The tasks they create can either enhance the “agility” and “ownership” of their teams, or drastically hinder it.</p><p>Furthermore, they can accidentally convey external pressure on to their teams, or allow tech debt to build up over time. They are often asked to compromise a lower <em>creation cost</em> for a higher <em>maintenance cost </em>of their product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VfEOi6nl7tLZzlxCTutv-g.jpeg" /><figcaption>By personal experience, the “skip the tutorial” approach should not be used in the kitchen.</figcaption></figure><p>Over my first few weeks here, I had several talks with our Product Owners and looked at the way they were creating either tasks or user stories. We looked at the characteristics and advantages of a good user story, and tried to apply these principles to their daily work.</p><p>It often wasn’t easy to do this exercise on projects that were already born as “back-end only”. Especially in some squads, this created a rift between the front-end and back-end developers that was almost impossible to close, unless we started a new project from scratch.</p><p>It was important, however, for the Product Owners to slice their product in releasable increments, regardless of the status quo of their teams. Establishing this principle is a very important preparation step for the introduction of Agile methodologies.</p><p>The results were good. Especially for new projects, the Product Owners showed great potential. Words like “Proof of Concept” and “MVP” acquired a different meaning.</p><p>I applied the following strategy:</p><ol><li>Train the Product Owners on user story writing</li><li>Establish a standard visual format for user stories across all teams in JIRA</li><li>Dig deeper into the topics of user story splitting and MVP</li><li>Hold user story refinement sessions with the teams.</li><li>Follow up as often as possible</li></ol><p>As the teams often complained about unclear tasks, establishing a common (visual) format for all user stories was a quick win. In this way, we were able to have much more focused conversations than before.</p><p>This helped us a great deal when we brought our stories to the team. It was nice to witness how they accepted the change, and trailed behind the Product Owners.</p><p>However, I also saw how the initial thrust died quickly, and how the teams naturally “fell back” to old practices. Mindsets don’t change over time, and that’s why constant coaching is crucial during this phase.</p><p>I realised that there is one limit to this <em>“skip the tutorial”</em> approach: you cannot be 100% sure of how many notions are actually needed by the team, in order to root out most of their inefficiencies. I tried to pick the smallest possible pieces of “Agile knowledge” and hand them out to the teams gradually. It wasn’t perfect, but it gave us a starting point.</p><p>With hindsight, it’s easy to acknowledge what had been missing. The advantage, however, is that the teams themselves will now be able to also realise and accept it. This way, you are not imposing a new process from Day One, but make sure you gradually build up both processes and mindset at the same time.</p><blockquote>A mindset without processes can become inefficient, and does not scale. Processes without mindset can kill both commitment and morale.</blockquote><p>It’s an exciting challenge, though sometimes it can be an emotional rollercoaster. Things feel great, and then bad, and then great again.</p><p>It’s almost as if every day we were trading our “Agility” on the stock market: the index goes up and down, appreciated or depreciated, bought or sold.</p><p>You must expect some sort of fluctuation, and have a strategy that accounts for it. A shared strategy, that is. In HelloTech, the Product Owners are a crucial part of it. Without them, it will be very hard to take this vision to the next level.</p><p><em>Agile 1, over and out.</em></p><p><em>Looking for a new job opportunity? </em><a href="https://www.hellofresh.com/jobs/"><em>Become a part of our team! We are constantly on the lookout for great talent</em></a><em>. Help us in our mission of delivering fresh ingredients to your door and make home cooking accessible to </em><strong><em>everyone</em></strong><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b266c1fb5dc5" width="1" height="1" alt=""><hr><p><a href="https://engineering.hellofresh.com/road-to-agile-part-3-skip-the-tutorial-b266c1fb5dc5">Road to Agile — Part 3: Skip the tutorial</a> was originally published in <a href="https://engineering.hellofresh.com/">HelloTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Road to Agile — Part 2: The right ingredients]]></title>
            <link>https://engineering.hellofresh.com/road-to-agile-part-2-e10b4a721cde?source=rss-aa3c4d2b842------2</link>
            <guid isPermaLink="false">https://medium.com/p/e10b4a721cde</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alessio Romito]]></dc:creator>
            <pubDate>Wed, 01 Mar 2017 16:23:12 GMT</pubDate>
            <atom:updated>2017-03-01T16:44:52.662Z</atom:updated>
            <content:encoded><![CDATA[<h3>Road to Agile — Part 2: The right ingredients</h3><p>In <a href="https://engineering.hellofresh.com/road-to-agile-pt1-d842a9937307#.fgay5h5ea">Part 1</a> we discussed the main motives and circumstances that led HelloFresh to seek a transition to an environment that adheres closer to Agile development practices.</p><p>Today we will have a look at what is the <em>status quo</em> within HelloTech. It took me a few days to get a clear picture of what is actually going on, given the size of the department. I took the necessary time to speak with people on all levels of the organisation, from newly-hired juniors to C-level managers. As a matter of fact, this broad scope is, if you ask me, one of the most interesting aspects of working as an Agile Coach.</p><p>There are many good cultural aspects to our IT team: people share a collaborative mindset, first of all, and on top of that there is a clear focus on <em>getting shit done</em>,<em> </em>from all sides. Each team member is valued and recognized for his contribution and has the chance of becoming a <em>de-facto leader</em> of his squad, regardless of job titles.</p><blockquote>Everybody plays a crucial role in the success of the company. Each team is able to pull together when a tough situation arises, and get the job done.</blockquote><p>Furthermore, the IT leadership team is very open to changes and giving the teams enough freedom to experiment with new ways of working together. The leadership team itself is mainly made up of people who got promoted internally to positions of responsibility, which makes career progression something “real” and appealing to every member of the development teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*Ip1OlcNLhtvbXWwAKD0aNA.jpeg" /><figcaption>Something&#39;s always cooking, here at HelloTech. We need to make sure we never lack the right ingredients for our recipes.</figcaption></figure><p>I consider this good <em>fertile soil </em>for a successful implementation of Agile development practices. If you have it, you will be able to focus more on coaching people and less on debating about why certain things are more useful than others.</p><p>On the other hand, there are aspects in which HelloTech needs to get better at, if they want to reach a more “stable” status.</p><p>First of all, we can only improve things that we can measure. We need objectivity if we want to show people that we are on the right path. Follow up on the good initiatives, don’t give up on finding tangible solutions.</p><blockquote>“I think we are improving” will never be as strong as “Here you can see how much we have improved”.</blockquote><p>At this early stage, I’m not even thinking about actual numbers or KPIs. I started on a more simple level by writing down retrospective notes and action items, and then regularly analyzing with the teams if problems were being solved once and for all.</p><p>If you have the team complaining about something for two months, and then that “something” disappears because of a change we introduced, it conveys a very strong message and encourages everybody to experiment more, to improve more.</p><p>While it sounds obvious, this is something often overlooked or simply ignored. We have a culture focused on “delivering”, while I believe it would be beneficial to start shifting towards “delivering in a better and better way” in terms of product quality, personal satisfaction, and development sustainability.</p><p>Setting an upward trend for these three items is my goal at HelloFresh. This is the vision I shared with my colleagues over the past few weeks. In the next articles we will take a look at how this trend can be initiated, and what kind of “accidents” might happen along the way.</p><p>Cheers,<br>Alessio</p><p><em>Looking for a new job opportunity? </em><a href="https://www.hellofresh.com/jobs/"><em>Become a part of our team! We are constantly on the lookout for great talent</em></a><em>. Help us in our mission of delivering fresh ingredients to your door and make home cooking accessible to </em><strong><em>everyone</em></strong><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e10b4a721cde" width="1" height="1" alt=""><hr><p><a href="https://engineering.hellofresh.com/road-to-agile-part-2-e10b4a721cde">Road to Agile — Part 2: The right ingredients</a> was originally published in <a href="https://engineering.hellofresh.com/">HelloTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Road to Agile — Part 1: Setting the stage]]></title>
            <link>https://engineering.hellofresh.com/road-to-agile-pt1-d842a9937307?source=rss-aa3c4d2b842------2</link>
            <guid isPermaLink="false">https://medium.com/p/d842a9937307</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Alessio Romito]]></dc:creator>
            <pubDate>Thu, 02 Feb 2017 11:12:01 GMT</pubDate>
            <atom:updated>2017-02-02T12:02:50.022Z</atom:updated>
            <content:encoded><![CDATA[<h3>Road to Agile — Part 1: Setting the stage</h3><p>To introduce Agile development practices into a team is not an easy task. Some people will like the proposed changes, and will help the transition. Others will not be impressed and will just be neutral. A minority (well, hopefully) might even openly oppose the transition, claiming that it won’t ever be worth the effort.</p><p>As a coach, you never know the hand you’re dealt with until you start the game.</p><p>You need to funnel the enthusiasm of the people who are willing to change, fight the inertia of the “neutral faction”, and take care to address every single issue reported by those who are resisting the transition.</p><p>It’s a hard road to walk on, with many opportunities for false steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*8R8ZNU5PS9cuu2BreP-ubQ.jpeg" /><figcaption>On the road, your goal is in front of you even when you can’t directly see it.</figcaption></figure><p>This kind of transition can take several weeks, if not months, for a single development team of five to nine people. My job at HelloFresh is to make sure that this transition is put in motion for the whole IT organization, which is more than 100-people strong.</p><p>Before joining HelloFresh, on January 2nd, 2017, I couldn’t see what sort of “hand” I was about to be dealt, though I already knew it was going to be a tough game.</p><p>The company has grown exponentially over the past two years and the IT team (a.k.a. HelloTech) has unrelentingly delivered whatever was necessary to fuel that growth.</p><p>This continuous support did not come without pain, however. Many trade-offs were made when it came to prioritizing quality over speed. “Deliver it now” has usually been the standard over “Let’s do it right”.</p><p>These short-term gains, chosen over long-term sustainability, are now starting to cause trouble among both the developers and the product owners.</p><p>As a consequence of that, HelloTech is facing the risk of falling into a state where the cost of maintaining their codebase is higher than creating new parts of it.</p><p>The word “legacy” is already haunting many developers. “Documentation” causes a wave of either laughter or dismay whenever spoken in a meeting room. “Tech Debt” often rhymes with “cold sweat”.</p><p>Faced with this challenge, HelloTech took two major decisions:</p><ol><li>Re-organize the team structure, as described <a href="https://engineering.hellofresh.com/hellotech-growing-a-tech-team-ba5c6cc96011#.w57s2c5yr">here</a>;</li><li>Hire an Agile coach, for the first time.</li></ol><p>Traditionally, HelloFresh has never employed a full-time coach (or even Scrum master) for their teams. Tech Leads and Product Owners have been “running the show” since the dawn of days, juggling both priorities and stakeholders without any consistent help or guidance.</p><p>In the next post, I am going to describe what kind of “Agile vision” and strategy I have in mind for HelloTech as an IT organisation, and for HelloFresh as a whole.</p><p>Stay tuned for more,<br>Alessio</p><p><em>Looking for a new job opportunity? </em><a href="https://www.hellofresh.com/jobs/"><em>Become a part of our team! We are constantly on the lookout for great talent</em></a><em>. Help us in our mission of delivering fresh ingredients to your door and make home cooking accessible to </em><strong><em>everyone</em></strong><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d842a9937307" width="1" height="1" alt=""><hr><p><a href="https://engineering.hellofresh.com/road-to-agile-pt1-d842a9937307">Road to Agile — Part 1: Setting the stage</a> was originally published in <a href="https://engineering.hellofresh.com/">HelloTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>