<?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 Alberto González on Medium]]></title>
        <description><![CDATA[Stories by Alberto González on Medium]]></description>
        <link>https://medium.com/@a.gonzalezlizan?source=rss-c9a415876855------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*uYfFQ94OohdGScr4chtz8w.png</url>
            <title>Stories by Alberto González on Medium</title>
            <link>https://medium.com/@a.gonzalezlizan?source=rss-c9a415876855------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:06:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@a.gonzalezlizan/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[The importance of (well-designed) metrics at Software Engineering]]></title>
            <link>https://medium.com/coverwallet-engineering/the-importance-of-well-designed-metrics-at-software-engineering-1bc7ae63274b?source=rss-c9a415876855------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bc7ae63274b</guid>
            <category><![CDATA[circleci]]></category>
            <category><![CDATA[software-metrics]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Alberto González]]></dc:creator>
            <pubDate>Fri, 14 Jan 2022 08:47:49 GMT</pubDate>
            <atom:updated>2022-01-14T08:47:49.074Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5bYY5rzU6PhyXAD-" /></figure><p>If you have dealt before with engineering metrics, you understand it is not an easy task. Software development is a social activity and then it is not trivial to measure and understand. However, we try to measure everything, and hey, that is fantastic! But that is not enough when talking about software.</p><blockquote><em>“Metrics don’t tell the whole story”</em></blockquote><p>This is why it is so important to define <strong><em>well-designed</em></strong> metrics when measuring software. Sometimes, we lose sight of the truth when looking at specific metrics, as we only see a small part of the picture. I am a big fan of “You can’t manage what you can’t measure”, but this is something to be careful about when it is related to tasks like building software. It is pretty common in the industry to measure useless things. And, on the other hand, sometimes it is not possible to measure the useful things.</p><p>During my career, (and my personal life, to be honest), I’ve tried to measure every single thing for creating visibility (and then try to improve later), and I can guarantee that metrics are applicable to all the employees, from executives, managers, … to engineers. It is important to spread a culture of measurement and look back retrospectively. This is the only thing we can do to identify excellence or mastery. Managers should clearly identify the most important metrics to the team in its current phase.</p><blockquote><em>“Metrics are not only managers stuff”</em></blockquote><p>Nowadays, it is pretty common to talk about high-performance teams (<a href="https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339">Accelerate</a> book is an interesting reference on this topic). In my opinion, high-performance teams, apart from many other characteristics (autonomy, mastery, empowerment, …), have the ability to look back retrospectively and continuously improve. When we talk about looking back, it is pretty important to have some data explaining what really happened, and then understand ways to improve as a team.</p><p>CoverWallet is a data-driven company. We make decisions based on data, and that is present in all the departments, starting with sales, but including marketing, operations, product and engineering. We have a company daily standup when every department shows their numbers to the rest of the company.</p><h3>Engineering Metrics</h3><p>Most of the times, Software Development Life Cycle (SDLCs) involve more than 1 or 2 people: coder, reviewer, QA member, Product Manager, … Delivering software is a team activity, and we should foster that approach when setting metrics. Because of that, we must measure software based on teams, tribes, departments, …</p><p>Some metrics are unobtainable without standardizing some processes, and this could be seen as removing team autonomy. However, this aspect is critical in some metrics, for example, the ones obtained from the Project Management System (we use Jira, at CoverWallet). We have customized Jira in order to obtain better information about our teams, initiatives, and programs.</p><h3>Measurement VS target</h3><p>This is a critical aspect when starting to measure things. There is a big difference between measuring something and putting some target on that measurement. Those targets (and their incentives, if applicable) tend to erode intrinsic motivators, losing their empowerment and autonomy (if you are interested in this topic, I recommend you to read about Dan Pink). Intrinsic motivation is replaced by team motivation to only meet and pursue those targets (and earn those incentives).</p><p>This is a typical example:</p><p><em>Manager A sets (imposes) a velocity target to her squad team. As you all know, velocity is a good metric to measure when working with Scrum. However, in this case, that target limits the choice of action to the team, as they could feel unempowered to help address technical debt (for example) if it is constrained by velocity targets. Apart from that, it is pretty easy for the team to hack those metrics, as it is as easy as making bigger estimations.</em></p><p>Related to the previous example, however, this does not mean that velocity is a bad metric to measure, just that it is bad to use that metric as a target. This is the main difference between measurement versus target. We should try to measure as many things as possible (if they are feasible, automatic, …), but there is a high risk when selecting them as targets.</p><blockquote><em>“When a measure becomes a target, it ceases to be a good measure”</em> — Goodhart’s law</blockquote><p>Finally, and moving back to intrinsic motivation, teams motivated by targets tend to take less ownership against problems. Empower teams need a more meaningful purpose than targets, they need autonomy and mission.</p><h3>Well-designed metrics, good targets</h3><p>As we commented previously, it is critical to set well-designed targets for our teams, as this could have a negative impact when done wrong. But, even without targets, metrics can benefit a lot from better design.</p><p>A good practice I’ve been using along the time for setting well-designed metrics is to try to group a bunch of metrics together into an aggregate metric. This usually works better than reviewing them individually. This is achieved by defining an aggregate metric as the weighted sum of the other metrics. For example, here at CoverWallet, we have a very useful metric to review at a high-level how our scrum process works in a team. We consolidate 3 metrics in a 100-based formula result: sprint start commitment, sprint end commitment and sprint velocity. We call this metric, Scrum Health Score. We were iterating during weeks over this metric.</p><p>A well-designed metric is a learning journey, it is not possible from one day to another. Good metrics need to be easy to measure and obtain, and the benefits obtained from the metric should be bigger than the cost to obtain it. And, finally, good metrics should be reported (and reviewed) frequently.</p><h3>Types of Software Metrics</h3><p>We cover super quick some of the most common industry metrics (there are hundreds more). We’ve divided them into 5 big categories:</p><ol><li>SDLC</li></ol><ul><li>[GitHub] PR Lead Time (hours)</li><li>[GitHub]# of comments/PR (number)</li><li>[GitHub]Time from PR until first comment (hours)</li><li>[CircleCI] # of Deployments (number)</li><li>[CircleCI]Deployment success ratio (percentage)</li><li>[CircleCI]Time to Deploy (minutes)</li><li>…</li></ul><p>2. Quality</p><ul><li>[Jira] # of defects (number)</li><li>[SonarQube]Test/Code coverage (percentage)</li><li>[Jira]# of code smells (number)</li><li>[Jira] Defect Removal Efficiency (percentage)</li><li>[Jira] Mean Time To Recover (hours)</li><li>…</li></ul><p>3. Project Management</p><ul><li>[Jira] Velocity (number)</li><li>[Jira] Start commitment (number)</li><li>[Jira] End commitment (number)</li><li>[Jira] # of tasks (number)</li><li>[Jira] Time to market (hours)</li><li>…</li></ul><p>4. Release/Project/Program</p><ul><li>[Jira] Burndown/Burnup chart</li><li>[Jira] Status pie chart</li><li>…</li></ul><p>5. Monitoring</p><ul><li>[Datadog] Error and success rates</li><li>[Datadog]Service failures and restarts</li><li>[Datadog]Performance and latency of responses</li><li>[Datadog]Resource usage</li><li>…</li></ul><p>We could spend hours talking about all the different metrics. During this last year, we, at CoverWallet, have put extra focus on 4 main targets:</p><ul><li><strong>Number of defects</strong>. Teams were improving a lot, not just this number, but also the process to report and fix was improved heavily (Mean Time To Recover). This was our north star related to quality.</li><li><strong>Cycle Time</strong>. Teams improved this number by 40% in less than 2 months, and then it was maintained during the whole year. The main action was teams started to work and deal with their tasks better as a team (team-first mindset). :rocket:</li><li><strong>DRE (Defect Removal Efficiency)</strong>. Teams, mostly organized by our QA team, were paying extra attention to this metric, and how the changes in the process affect it.</li><li><strong>Scrum Health Score</strong>. Some teams were extremely engaged with this metric. We had an improvement by 25% during the year. Apart from this benefit, this metric also helps our teams to understand and negotiate better around their sprint commitments.</li></ul><p>Apart from those target, we were monitoring carefully some other metrics:</p><ul><li>Time to Deploy. Even without a target, we improved this metric by 30%.</li><li>Number of PRs merged.</li><li>Number of Deployments.</li><li>Niko-Niko mood.</li><li>PR size.</li><li>PR lead time.</li><li>And many more!</li></ul><h3>How to approach metrics to my team first time ever</h3><p>If you are dealing in a world without metrics/targets, my recommendations are:</p><ol><li>Understand your categories of metrics (SDLC, Project Management, …)</li><li>Select relevant metrics in each category. Remember it is critical that those metrics are feasible and easy to obtain.</li><li>Work on those metrics with the rest of your team.</li><li>Start to monitor and review those metrics</li><li>(If the metric is meaningful for you) Start thinking about having that metric as a target in the next cycle. When thinking, it is important to understand, as we commented, which other metrics are a good fit to group, bunch metrics are better that single fine-grained ones.</li></ol><p>We hope you enjoy and find this blog post useful.</p><p>We, at <a href="https://www.coverwallet.com/jobs/tech">CoverWallet</a>, will continue exploring which metrics are interesting and which ones are selected as targets for the next round :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bc7ae63274b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coverwallet-engineering/the-importance-of-well-designed-metrics-at-software-engineering-1bc7ae63274b">The importance of (well-designed) metrics at Software Engineering</a> was originally published in <a href="https://medium.com/coverwallet-engineering">Coverwallet Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Management advices I’d have appreciated to receive years ago]]></title>
            <link>https://medium.com/coverwallet-engineering/management-advices-id-have-appreciated-to-receive-years-ago-f094b4fd6d85?source=rss-c9a415876855------2</link>
            <guid isPermaLink="false">https://medium.com/p/f094b4fd6d85</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[negotiation-skills]]></category>
            <dc:creator><![CDATA[Alberto González]]></dc:creator>
            <pubDate>Fri, 02 Oct 2020 08:01:50 GMT</pubDate>
            <atom:updated>2020-10-02T08:01:50.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IEeeJ-Eg9lkSa0rK" /><figcaption>Photo by <a href="https://unsplash.com/@sctgrhm?utm_source=medium&amp;utm_medium=referral">Scott Graham</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A few years ago, I was a super happy software engineer, I had almost everything under control and I knew how to measure whether or not my day had gone well. As most of you know, it’s not easy to measure when a day has gone well for management roles, especially when previously you were an individual contributor, and you could evaluate with story points, tasks, lines of code or pull requests how your day had gone.</p><p>With the passage of time I started to work managing teams, complex at the beginning. The first weeks, and even months, are hard because we can be a little bit lost. Perhaps, this transition period could be extended to a year. I think the most important thing is to be sure that it’s what we really want to do.</p><p>Then we start working as awesome managers and find that we aren’t able to measure the success of our day. This is one of the trickiest situations. How can we evaluate our work if we don’t execute almost anything? With time, I’ve learnt to evaluate my work based on the work of my team, and that is the moment when you start to really enjoy your job 😎.</p><blockquote>“Talent wins games, but teamwork and intelligence wins championships”, Michael Jordan</blockquote><p>Once we have talked about the introduction of software engineers and managers, we are going to talk about some, at least for me 🙃, useful advice I have been collecting during my career.</p><p>The number one piece of advice: Improve your <strong>communication skills</strong>. This advice is super important. When we were studying at University, we learnt a lot of coding, architecture, operating systems, databases, … but not so much about how to communicate (with your team, your boss, …), delegate, give constructive feedback, … I have a quick summary of useful advice to improve your communication skills:</p><ol><li>Be friendly</li><li>Be available</li><li>Be a good listener</li><li>Be clear</li><li>Be aware of non verbal communication</li></ol><p>Regarding feedback, it’s important to take a look to <strong>SBI feedback</strong>. I’ll review so fast this kind of feedback:</p><ol><li>Situation</li><li>Behavior</li><li>Impact</li></ol><p>This is typical feedback SBI example:</p><blockquote>During yesterday morning’s team meeting, when you gave your presentation, you were uncertain about two of the slides and your sales calculations were incorrect. I felt embarrassed because the entire board was there. I’m worried that this has affected the reputation of our team.</blockquote><p>Situation = During yesterday morning’s team meeting, when you gave your presentation.</p><p>Behavior = you were uncertain about two of the slides and your sales calculations were incorrect.</p><p>Impact = I felt embarrassed because the entire board was there. I’m worried that this has affected the reputation of our team</p><p>Also, it’s very important to <strong>improve your negotiation skills</strong>. In a management role, we spend almost all our time negotiating. Here are some relevant negotiation skills you should be aware:</p><ol><li>Listen actively</li><li>Ask good questions</li><li>Build rapport</li><li>Search for smart tradeoffs</li><li>Develop A Plan Prior To Negotiating (for me, this last is the most important)</li></ol><p>These are some of them, but there are much more!</p><p>Finally, it’s important to<strong> identify what kind of feedback is good to give in public versus handle in private</strong>. Most constructive feedback is best given in a 1:1 meeting, because saying it in front of a group can make someone feel put on the spot. On the other hand, public feedback is important to congratulate your team or team members if they did a good job.</p><p>As managers, it’s common to have a busy agenda, but it’s important to <strong>make time for your team</strong>. Some common ways to do this:</p><ul><li>Regular 1:1s. I like to have biweekly sessions, or even, with some of them weekly. It also depends on the moment of the employee and her mood.</li><li>Be available via your messaging platform</li><li>Block some hours in your calendar to talk with your team</li><li>Go for lunch or coffee</li></ul><p>While I think the advice to spend more time with your team is important, if I had to choose one thing, it would be regular 1:1 meetings, for sure. I use these 1:1 meetings to give direct performance feedback every month, at least. to set goals during these meetings and check them monthly. In this performance feedback, you can analyse how close to achieving the goal the employee is and mentor them to go faster. If in the future, the employee doesn’t reach some of their goals, at least, you’ll be sure that you, the direct report and manager, worked hard to reach them, and there are no surprises for both parties. For this exercise, it’s very important to be honest, having a relationship based on solid trust.</p><p>As I mentioned before, your agenda as manager will be a busy one, so it’s necessary to organize your day and learn to prioritize. Every manager has their own tools like Trello, Notion, Jira, … to prioritize their tasks. I, personally, use Trello, trying to have a column for the important tasks of the day, other for important tasks of the week, and finally I have a column for deprioritized tasks. It’s super important to learn how to prioritize our work. We need to understand the difference between an important task and an urgent task. As managers, we spend almost all of our time prioritizing things.</p><p>To organize my day I use Google Calendar, and I share my calendar with all my teammates. In there I try to have regular events for 1:1s, weekly syncs or other kinds of events.</p><p>These are some of the indications that I would have appreciated receiving years ago. For each one, I could write a full post because they are so important. I hope this post helps you in the future, especially, if you are starting your career as a manager.</p><p><em>We, as managers at </em><a href="https://medium.com/u/a682303cb3e8"><em>Cover Wallet</em></a><em>, want to give our best. If you are interesting in joining our company, you can visit our </em><a href="https://www.coverwallet.com/jobs/tech"><em>open positions page</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f094b4fd6d85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coverwallet-engineering/management-advices-id-have-appreciated-to-receive-years-ago-f094b4fd6d85">Management advices I’d have appreciated to receive years ago</a> was originally published in <a href="https://medium.com/coverwallet-engineering">Coverwallet Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How is your team feeling during this WFH period?]]></title>
            <link>https://medium.com/coverwallet-engineering/how-is-your-team-feeling-during-this-wfh-period-c863cf5579c9?source=rss-c9a415876855------2</link>
            <guid isPermaLink="false">https://medium.com/p/c863cf5579c9</guid>
            <dc:creator><![CDATA[Alberto González]]></dc:creator>
            <pubDate>Tue, 12 May 2020 09:19:54 GMT</pubDate>
            <atom:updated>2020-05-12T10:19:41.707Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Gqb_DKOYFyYrQCY7eTncA.jpeg" /></figure><h4>What is Niko-Niko?</h4><p>Nowadays, it is very important to evaluate your team’s health, and Niko-Niko is a great tool to consider. This tool was invented by Akinori Sakata a few years ago, in 2006. This calendar is <strong>also known as the happiness index</strong> or the smiley calendar.</p><p>Niko-Niko is just a simple calendar where everybody shares their mood of the day. It can be reflected with smiley faces (from frowning to happy) or even with a number (from 1 “sad” to 5 “awesome”).</p><p>It is important to say that “happy people make happy people”, because <strong>happiness is contagious</strong> and <strong>an effective stress reliever</strong>. In addition, laughter is a great way to bond with others.</p><p>Niko-Niko is even more useful in the current situation, with a WFH period. This stressful situation could negatively affect the mood of our teams.</p><h4>Who is Niko-Niko useful for?</h4><p>Firstly, for the employees it is really useful. With Niko-Niko we enhance team building, and therefore help teams to grow. Also, this tool is for improving the happiness of the employees, so finally, <strong>it makes employees happier</strong> 😃 🎉!.</p><p>For management, they use a lot of KPIs to measure productivity, bugs, releases, … and it is also important to track the mood for helping the team to <strong>identify problems as soon as possible</strong>.</p><h4>Why is it useful?</h4><p>Happiness is really important because we could get some benefits like:</p><ul><li>Increase <strong>productivity</strong></li><li>Improve the <strong>quality of the job</strong> done</li><li>Improve <strong>engagement with the company</strong>, which is extremely important nowadays because of the difficulty in finding the right people for your team</li><li><strong>Stress reliever, </strong>as I commented before</li></ul><p>Who doesn’t want to feel productive? Or who doesn’t want to do a high quality job? Everybody wants this, and Niko-Niko helps us get it.</p><h4>When to implement it?</h4><p>Niko-Niko is always very useful, but <strong>we decided to start using the Niko-Niko calendar during the WFH period caused by COVID-19</strong>. As many you will be experiencing, WFH can be very stressful, with kids at home, small apartments, roommates, etc. All these elements could impact our mood, and the sooner we can detect them, the sooner we can act on them to avoid a negative impact.</p><h4>How to implement it?</h4><p>Traditionally Niko-Niko was used with a physical calendar at the office. Today, with so many teams working remotely,<strong> </strong>there are many cloud applications that are compatible with this calendar.<strong> The </strong><a href="https://www.coverwallet.com/jobs/tech"><strong>Coverwallet team</strong></a><strong> developed their own tool </strong>which is also maintained by them. Everyday, we receive a message reminding us to make a note of our mood on the calendar. This message is adapted to the time zone where our teams are working.</p><p>At Coverwallet, <strong>we use one online calendar per team</strong> and we try to analyze data retrospectively. <strong>Team members can access this team calendar whenever they want</strong>. Also, in this calendar, team members could reflect comments, or even events that happened that day. These details are really important to review at retrospective meetings. In addition to these meetings, it is important to have a high level view every quarter, for example.</p><p>If we detect some anomalies, we try to analyze them with our teammates and managers, and solve them as soon as possible.</p><h4>Which data are important?</h4><p>First of all, <strong>team involvement</strong> is key, because we need so much data to get a real mood. So, we need to encourage involvement from the team. Starting at 50–60% involvement the data starts to be useful.</p><p>Once we have good team involvement, teams can analyze the <strong>average mood</strong> trying to identify how is the team’s health and <strong>which actions have had a positive or negative impact</strong> (complex task, family issues, pay-slips, critical deadline, promotions, newcomers, team changes, …). Furthermore, comments are also really important.</p><p>These are the key elements:</p><ul><li>Team involvement</li><li>Average mood</li><li>Team comments</li><li>Actions</li></ul><h4>Some useful examples</h4><p>Related with agile methodologies, we have some useful and typical examples:</p><ul><li><em>All team members in a bad mood</em>. Uh, bad karma in the team. Why? What is happening with this team? Burnout?</li><li><em>One happy team mate and not the other ones</em>. Team is not correctly balanced? Lack of communication in the team?</li><li><em>Everybody is happy and the sprint is not going well</em>. What are they happy about? Are goals correctly communicated?</li><li><em>One sad team mate, the other are happy and the sprint is going well</em>. Any problem here? Problems outside of the office? Maybe, if the employee wants to, the manager can talk privately to help him/her.</li></ul><h4>Other companies using Niko-Niko</h4><p>Some of the biggest tech companies are also using Niko-Niko to keep track of the mood of their teams. Enterprises like <strong>Facebook, Google or Apple</strong> use this calendar daily.</p><h4>Other extra references</h4><p>University of Warwick.</p><blockquote>“Researchers prove that employees in a good mood are 12% more productive — and say perks could be the key”</blockquote><p>Alexander Kjerulf (founder of Woohoo inc).</p><blockquote>“…happy employees make better decisions, are better at time management, work better with others, and possess a number of other critical leadership skills…”</blockquote><p>William Craig (Forbes contributor).</p><blockquote>“…employees who aren’t happy with their work environments are likely to put in less effort at work…”</blockquote><p>Martin Zwilling (Forbes contributor).</p><blockquote>“… happy employees are more collaborative and more driven to work with their colleagues toward common goals…”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c863cf5579c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coverwallet-engineering/how-is-your-team-feeling-during-this-wfh-period-c863cf5579c9">How is your team feeling during this WFH period?</a> was originally published in <a href="https://medium.com/coverwallet-engineering">Coverwallet Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>