<?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 Gergely Nemeth on Medium]]></title>
        <description><![CDATA[Stories by Gergely Nemeth on Medium]]></description>
        <link>https://medium.com/@nthgergo?source=rss-732ca3d84cb7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DdXtUW5JAIGimxc_djoECQ.jpeg</url>
            <title>Stories by Gergely Nemeth on Medium</title>
            <link>https://medium.com/@nthgergo?source=rss-732ca3d84cb7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:28:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nthgergo/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 to Provide Feedback]]></title>
            <link>https://nthgergo.medium.com/how-to-provide-feedback-a4d61a2d8170?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4d61a2d8170</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Wed, 13 Jul 2022 21:49:03 GMT</pubDate>
            <atom:updated>2022-07-13T21:49:03.361Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IDxPSgGabo0mgQtG.png" /></figure><p>Providing both critical feedback and praise are two acts we can all agree are important. For most of us, however, it takes time and practice to get comfortable with either. This blog post summarises what worked well for me in the past; hopefully, you can adopt some of it for your own purposes.</p><ul><li>When you start working with new team members, ask them how they prefer to get praise and critical feedback. I use these two questions in my very first 1:1s with direct reports:<br><em> –“How do you like to receive recognition? Are you okay with the occasional public praise?”<br> –“How do you prefer to receive critical feedback?”</em></li><li>My preference is to provide real-time feedback whenever possible, and to have longer conversations as follow-ups during 1:1s. As I pointed out above, however, I let team members pick the method they are most comfortable with. Either way, make sure your feedback is timely: either real-time, or discussed in the very next 1:1.</li><li>To provide critical feedback, I usually choose a framework like SBI (Situation, Behaviour, Impact) or STAR (Situation/Task, Action, Result)<br><em> –Example: “(Situation) During the outage yesterday, (Action) John jumped in to help with org-wide comms by sending regular updates to eng@, (Result) that helped with the number of tasks the incident commander had to take care of, leading to faster resolution of the incident. Thank you John!”</em></li><li>These frameworks allow me to provide context on what I’ve observed and how that impacted the team or the broader community.</li><li>For the recipient of the feedback, this gives an external point of view, so we can start a conversation and come to an understanding about what happened and how we can improve in the future.</li><li>Using frameworks like these also helps to eliminate bias, forcing you to provide feedback on the action you observed and not on the person.</li><li>Critical feedback should occur in a private setting with very few exceptions.</li><li>Avoid sugar coating feedback, or using techniques like the <a href="https://hbr.org/2013/04/the-sandwich-approach-undermin">“feedback sandwich”</a>. If you have critical feedback that needs to be heard and actioned, make sure that’s your primary and only message. Don’t confuse folks by also highlighting things they are doing well!</li><li>It might also be a good idea to document feedback items, both critical and positive, in a 1:1 document shared among both parties. This document will ensure you have a shared understanding of the feedback’s purpose, and which actions should be taken to improve.</li><li>While the annual performance review might serve as a good opportunity to summarize the feedback discussed over the year, it doesn’t serve anyone to save up feedback for it: it won’t be timely, and because of that, it does not allow the recipient to address it and improve on it. In short, never save feedback for the performance review!</li><li>Follow up. Have a plan to improve on the feedback you provided, and check back later. Once you’ve seen improvement, be sure to provide positive feedback.</li></ul><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/how-to-provide-feedback"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4d61a2d8170" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Tips For Your Performance Reviews]]></title>
            <link>https://nthgergo.medium.com/6-tips-for-your-performance-reviews-3ddd04aeed55?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ddd04aeed55</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[performance-reviews]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Sun, 21 Nov 2021 15:25:45 GMT</pubDate>
            <atom:updated>2021-11-21T15:25:45.081Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zv8x50uQFlZSW1jq.png" /></figure><p>With just a few months left from the year, performance review season is quickly approaching for many tech companies. This is often a stressful process for many working in tech, though it doesn’t have to be. By following the tips in this article, you should get more out of the annual or semi-annual reviews, that will help your professional growth.</p><h3>Performance Evaluations in a Nutshell</h3><p>Before getting into the weeds of it, let’s start with a quick overview of how performance evaluations look at most tech companies.</p><p>Most companies have two performance cycles per year, usually one for each half. Once the period under review wraps, employees are asked to write a few types of evaluation documents:</p><ol><li>An assessment of the work you’ve completed, which is usually referred to as a self-evaluation.</li><li>Several peer evaluations that provide feedback about the people you’ve worked beside most frequently.</li><li>A review of your direct manager.</li></ol><p>These review documents are then shared with your manager, who will write their assessments about your work, called manager evaluations. Once the manager evaluations are complete, the managers either finalize the reviews and use their budget to reward people, or undergo a calibration process, where engineering managers from the broader organization attempt to apply the same expectations for everyone in the org. This is done to improve the fairness of the review process. After these steps are finalized, your manager should share the results of their review with you. The results might take a bit longer if they include compensation changes, since larger companies require engineering leadership and/or the finance department to approve before granting raises.</p><p>Now that we’ve covered the basics, let’s get into how you can get the most out of these reviews!</p><h3>1. Identify your goals with the performance review</h3><p>While it may be a cliche, it’s a helpful exercise to identify what you’d like to get out of your reviews. Most of us will fall into one of these categories:</p><ul><li>To continue one’s professional growth, either by learning new skills, earning a promotion, or both.</li><li>Continue your current role, assuming you’re content in the position.</li><li>Earn a substantial pay raise.</li></ul><blockquote>Check out the article <a href="https://randsinrepose.com/archives/your-professional-growth-questionnaire/">Your Professional Growth Questionnaire</a> by Michael Lopp for help reflecting on goals and motivations.</blockquote><p>Your company culture, compensation, and long-term career goals all influence which part you’d like to improve. Once you identify your goals, consider sharing them with your manager to help you achieve your goals.</p><blockquote>At most tech companies, raises cap out at around 10%, even after promotions. So if you are looking for a raise higher than that, probably you’ll need to start looking for a new job.</blockquote><h3>2. Understand the review process at your company</h3><p>Work with your manager to gain an understanding of how the review process works at your company. Ask questions like:</p><ul><li>What are the expectations for my job level?</li><li>When are the formal reviews?</li><li>How does my performance influence compensation changes?</li><li>How do promotions work?</li><li>What are the expectations for the next level?</li></ul><p>There are no right or wrong answers to these questions, but they will help you set timelines, and understand how performance is evaluated for your job.</p><h3>3. Treat performance reviews as a continuous process</h3><p>I have often seen co-workers rushing to get their self-reviews done in a few days before the deadline. The problem with that is they tend to leave out a lot of achievements from the period under review. Depending on the size of a team, their managers might be unaware of how substantial their contributions were.</p><p>Making this mistake means you might miss out on recognition for a job well done. Even if your company does organization-wide calibration sessions or your manager is directly responsible for your reviews, you might not be represented fairly without all the facts from your self-evaluation.</p><p>Instead, it’s better to treat performance reviews as a continuous process. As <a href="https://randsinrepose.com/about/">Michael Lopp</a> puts it, <strong>it’s always performance season</strong>.</p><h3>4. Start documenting your achievements</h3><p>One of the best ways to address the point above is to document your achievements. It won’t just serve as a great starting point for your self-assessment document, but it will also help you identify skills you didn’t have the opportunity to improve.</p><p>In more practical terms, this is my usual process for documenting achievements:</p><ul><li>If your company has expectations for your current role, make a copy of that document, and use it to categorize your achievements.</li><li>If your company doesn’t have a well-documented list of expectations, work with your manager to create one for yourself.</li><li>Alternatively, you can keep a document for yourself about the tasks you’ve worked on, and how you helped solve the challenges presented by those projects.</li></ul><h3>5. Reflect on your achievements</h3><p>Once you have a list of achievements, there are a few ways you can use this document. First, create a list of skills you need to achieve your long-term career goals. Then, once you have this list, try identifying areas where you didn’t have an opportunity to succeed.</p><p>Alternatively, if your company has a career ladder or expectation for your current role or the next one up, use that list to identify areas you didn’t work on.</p><p>Once you have a list of skills or areas you’d like to work on, team up with your manager to find projects aligned with your growth goals.</p><h3>6. Repeat</h3><p>As we’ve already covered, performance reviews and self-improvement is a continuous process. I prefer to have a set cadence to reflect on where I am with my career and which areas need improvement. I recommend you spend around 30 minutes every two weeks making notes on what you’ve accomplished and reflect on how that helps you progress in your career.</p><p><em>I hope the tips above help you grow, get the promotion you want, or at least provide some insight about performance reviews and the best ways to prepare for them. If you have other tips and practices you like to follow; I’d love to hear from you, so drop me a message anytime on </em><a href="https://twitter.com/nthgergo"><em>Twitter</em></a><em>!</em></p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/tips-for-performance-reviews"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ddd04aeed55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On-calls and Incident Response]]></title>
            <link>https://nthgergo.medium.com/on-calls-and-incident-response-4b1f8cca700e?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b1f8cca700e</guid>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Wed, 01 Sep 2021 15:48:55 GMT</pubDate>
            <atom:updated>2021-09-01T15:48:55.733Z</atom:updated>
            <content:encoded><![CDATA[<p>Before starting in my current role, I worked on <a href="https://baseweb.design/">design systems for years</a>. One of the perks of that job was that we didn’t have to staff a 24/7 on-call rotation. If we released a version that had issues, the product team would simply roll back these changes so we could patch it the next day.</p><p>Today, I am still leading platform teams, except with one significant change in scope: we have Tier 0 production systems that need a 24/7 on-call rotation. The transition back to operating mission-critical systems led me to summarize my thoughts on what makes or breaks engineering on-calls, for anyone finding themselves facing these same challenges.</p><p>One of the main goals of staffing your on-call rotation is to ensure customer satisfaction. It’s not just a means to make sure services work, but to make sure customers can use your product effectively.</p><p>This is where Service Level Objectives (SLOs) come in. SLOs are built from Service Level Indicators (SLIs) and their associated goals. SLIs measure the level of service provided by any given operation that deals with customers. For most services, the following SLIs might serve as inspiration:</p><ul><li><strong>Latency SLI</strong>: the percentage(%) of requests that are handled faster than a given threshold.</li><li><strong>Availability SLI</strong>: the percentage(%) of requests that returned a successful response.</li></ul><p>You can turn the SLIs listed above into SLOs by assigning a goal for each of them:</p><ul><li><strong>Latency SLO</strong>: 95% of the requests are completed in less than 200ms.</li><li><strong>Availability SLO</strong>: 99.99% of the requests return a successful response.</li></ul><p>Defining SLOs is a collaborative process between your product counterparts and your engineering team. This is an exercise to complete early, so your services have an error budget-based approach rather than the unspoken goal of 100% availability. This allows the engineering team to make design decisions based on their error targets.</p><p><a href="https://sre.google/workbook/implementing-slos/"><em>You can read more about implementing SLOs here.</em></a></p><p>Once you’ve defined the goals of your on-call rotation, it’s time to staff it. Most articles and books on the topic will recommend at least eight engineers to staff a two-tiered, 24/7 on-call rotation, since it assures that no engineer remains on-call for more than two weeks in any given two-month period.</p><blockquote><strong><em>A two-tiered, 24/7 on-call rotation</em></strong><em> is when an on-call shift has a primary and a secondary responder. If the primary doesn’t acknowledge the pager after a certain amount of time, the secondary responder is paged automatically. Most on-call rotations implement a two-tiered system for redundancy.</em></blockquote><p>I prefer to have thirteen engineers on any given on-call rotation, so each individual becomes primary and secondary responders once a quarter. I avoid adding more to the rotation so the engineers can keep their services in context.</p><p><strong>Shared on-call rotations</strong> are when engineers are pooled from multiple teams to staff an on-call rotation for a single service. While this can bridge staffing gaps and create a safety net for services in the short-term, it is not a feasible strategy for long-term success. Engineers who don’t work on the service daily might miss out on changes required to deliver quality service, which can lead to an escalation of engineers with a better understanding of the services, or at worst, longer service restoration times.</p><p>Before an employee is fit to be an on-call responder, they should complete an on-call training and familiarize themselves with your service’s <strong>playbook</strong>. This is a critical step, since you don’t want on-call engineers handling their first mitigation steps during a live incident.</p><h3>On-call Playbooks</h3><p>Playbooks contain essential information for on-call scenarios, such as:</p><ul><li>Links to monitoring systems with crucial information about service health.</li><li>A short explanation of common error scenarios and how to mitigate them. This includes information like adding extra capacity, blocking and rate-limiting traffic, or rolling back a bad deployment.</li><li>Service architecture and dependencies on other services, with contact information to reach people from those teams, if necessary.</li><li>Protocols to follow during an incident. I’ve added more about this subject in the <a href="https://nemethgergely.com/blog/on-calls-and-incident-response#incident-response">incident response</a> section below.</li></ul><p>As playbooks can become obsolete with each new deployment, the on-call engineer is responsible for keeping them updated.</p><h3>On-call Trainings</h3><p>I recommend practicing on-call training with a cadence, even if no new on-call engineer joins the rotation. This ensures that everyone’s understanding of the systems they are responsible for is up-to-date.</p><p>Along with your responders’ understanding of the playbook, on-call trainings also help with:</p><ul><li><strong>Incident dry runs</strong>: Turn off certain parts of the system in a sandbox environment, observe which alerts are triggered, and see if your mitigation steps from the playbook help. Update the playbook as needed.</li><li><strong>Ensure correct setup of your pager</strong>: Try changing your phone’s clock to a different time and sending a test page to make sure it’s not blocked. I’ve seen a few pagers disappear this way, so it’s important to check.</li></ul><p>An incident is an event that can lead to a negative impact for customers <em>(or one already hurts customer relations)</em>. To gather an incident’s scope, you should define its severity level, which will influence how you prioritize mitigating incidents.</p><p>To measure severity levels, I recommend starting with 0 as the most impactful of incidents, and counting upward from there. Priorities will follow your definitions of severity levels. Using the example below, S0 translates into a priority where impacted teams need to stop everything and start working on the incident’s resolution immediately. S1 will be similar, though depending the size of the impacted population, you might have more time to address it. S2 may still require attention, but it becomes a “let’s take a look tomorrow morning” situation instead of preparation for an all-nighter. The following list might serve as inspiration:</p><ul><li><strong>S0</strong>: An outage that impacts every customer. These are the problems that could have a negative impact on your entire consumer base, so it’s all hands on deck.</li><li><strong>S1</strong>: An outage that impacts a subset of customers. Your business might partition customers based on where they live, or which applications they use to access your products and/or services.</li><li><strong>S2</strong>: Any incident that needs attention, but doesn’t impact customers. These may be scenarios which could potentially become worse, but allow for a little time to correct before events affect your bottom line.</li></ul><h3>Commanding Incidents</h3><p>The term <a href="https://en.wikipedia.org/wiki/Incident_commander">incident commander</a> is borrowed from <a href="https://en.wikipedia.org/wiki/Incident_Command_System">Incident Command System</a>, a standardized approach to the command, control, and coordination of emergency response.</p><p>During an incident, it’s crucial to have a single person overseeing mitigation steps. This ensures a focused effort to restore site health and clear communication about what to do next.</p><p>The technical details of mitigating incidents are outside the scope of this article, but I do want to cover some best practices for communicating during an incident.</p><p>First, you must enforce a company-wide standard regarding how to communicate during an incident. Consider creating a public Slack room (or equivalent) for sharing links, images, and additional context, such as the steps you’ve already tried to mitigate an incident. This will create an incident timeline, which serves as a source of truth for the <a href="https://nemethgergely.com/blog/on-calls-and-incident-response#post-mortems">post-mortem</a>. In most situations, it is more effective to use a real-time video app to resolve the incident with direct conversation. The incident commander takes the lead in both scenarios — asking the right questions, and gathering information that will inform the next step.</p><p>Secondly, partner with your marketing/PR team to devise a plan to communicate the problem with the customers without incurring liability or speaking off-brand.</p><h3>Post-mortems</h3><p>After each incident, it is important to use the understanding you’ve gained to prevent the same issues from happening again. One of the best ways to accomplish that is through <strong>post-mortems</strong>. In business, post-mortem documents and meetings define the incident’s root cause and seek to create action items that address identifiable gaps in service.</p><p>A post-mortem document should contain the following sections:</p><ul><li><strong>Timeline of events</strong>: This allows everyone reading the post mortem to follow the original team’s logic.</li><li><strong>Root cause</strong>: This defines the root cause of the incident, which can be anything from employee mistake to a systemic malfunction.</li><li><strong>Action items</strong>: These are the action items the team uses to address the incident’s root cause. Each item should have a clear owner and timeline, so future participants know who to contact with any questions.</li></ul><p>Once you have a draft of the post-mortem, it’s time to call for a post-mortem meeting <em>(or present it during your company incident reviews, if any)</em>. During this meeting, your team should present the post-mortem and answer any additional questions. Focus on identifying any action items that you may have missed.</p><p>Once the post-mortem meeting concludes, you can share any findings with the rest of the engineering organization. Sharing this information allows other teams to figure out their own gaps and prioritize accordingly.</p><p>The processes outlined above may or may not work for your organization. The only way to assess improvements to your on-call rotation is by capturing metrics with clear definitions. These metrics should focus on two different aspects of on-calls: service health and employee satisfaction.</p><p>For the service health, start with ‘mean time to detect’ (MTTD) and ‘mean time to restore’ (MTTR). MTTD is the time it took to discover an incident in your system from when it’s first reported; MTTR is the time it takes to resolve the incident once it’s discovered.</p><p>Regarding employee satisfaction, you should enact retros for the on-call participants at least once a quarter. These are how you find the necessary changes to the rotation or its protocols. Ideally, retros grant a consistent feedback loop through regular one-on-ones and reporting, so you can start to prevent problems instead of reacting to them.</p><p>On-call procedures are critical for engineering teams, and they can have a significant impact on the company’s bottom line. A poor on-call operation can quickly become a source of frustration and tension that poisons customers’ impression of your company. The practices outlined above should help you create healthier on-call rotations.</p><p><em>Thank you go to Michael Sitter for upleveling my expertise in incident response!</em></p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/on-calls-and-incident-response"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b1f8cca700e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Better Quarterly Plannings]]></title>
            <link>https://nthgergo.medium.com/better-quarterly-plannings-531ab628cdb4?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/531ab628cdb4</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 14:55:01 GMT</pubDate>
            <atom:updated>2020-11-25T14:55:01.191Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s face it: most engineering organizations struggle with quarterly and annual planning. As engineers and engineering leaders, we dread the weeks when it’s time to go through it again. Some companies struggle because of how long the planning process takes, or how counterproductive may seem compared to larger goals; others find it challenging to wade through the internal politics.</p><p>We can do better than this. This article provides a framework for engineering and product teams to reduce the inherent friction involved with planning, as well as the time required to complete planning cycles.</p><h3>Common Pain Points</h3><p>First, let’s examine some of the pain points your organization might experience during planning. The following are mentioned frequently :</p><ul><li>The process takes too much time. Depending on the organization and its competing priorities, it can take several weeks.</li><li>Even if planning takes several weeks, it can still feel rushed because numerous sync meetings are involved. This is especially true when there are internal or external dependencies, like a front-end team depending on a back-end service.</li><li>Projects can rarely fit into a single quarter, and most of them span several.</li><li>Too many projects may run parallel because a product has multiple priorities. This can leave teams without a sense of ownership as they jump between projects.</li></ul><h3>The Proposal</h3><p>In the article <a href="https://nemethgergely.com/blog/playbook-for-running-sprints">Playbook for Running Sprints</a>, I characterized sprints as efficient, but only if:</p><ul><li>The team always works on the most important stories.</li><li>There is a healthy feedback culture among team members.</li><li>There is at least a rough idea when things might be completed.</li></ul><p>Regarding prioritization: “The backlog is a semi-prioritized list of things that the team eventually wants to work on. Stories in the backlog may never get picked up, depending on priorities.”</p><p><strong>Wouldn’t it be great if we used a similar approach to quarterly plannings?</strong></p><p>The idea is to replace quarterly plannings with an organization-wide Kanban board and on-demand meetings as needed.</p><p>To illustrate the idea, consider the Kanban board below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CPSFpD29V7xO7SoV.png" /></figure><p>The <strong>backlog</strong> column represents ideas that the product or engineering leadership want the team to complete. Ideally, this list of epics is semi-prioritized, meaning that the top items are already in order of importance.</p><p>Epics are moved to the <strong>planning</strong> column when teams commit to delivering them. This is the phase when the internal and external dependencies that exist between teams are resolved. Ideally, you create epics in a way that invites collaboration between the least amount of dependencies.</p><p>The <strong>in progress</strong> column represents the epics that teams are actively working on.</p><p><strong>Done</strong> are the epics that you shipped to production.</p><p>Before putting this planning proposal into practice, be sure to state the rules and responsibilities clearly, as in:</p><ul><li><strong>Who can add ideas to the backlog?</strong> Starting with PMs and EMs might be a good start to expand on later.</li><li><strong>What are the requirements for epics to be added to the backlog?</strong> Consider requiring at least a one-page design document or a rule about minimum lengths. Also try to limit the epics’ size for a shorter feedback loop on proposal planning and the business impact of delivered epics.</li><li><strong>Who can expedite epics and stop in-progress ones?</strong> Business priorities can shift suddenly when something unforeseen happens, like COVID-19 or a new regulatory requirement. As stopping in-progress work results in quite some churn, this decision shouldn’t be made lightly.</li><li><strong>Who and how frequently should we meet to review backlog items?</strong> Depending on the size of your organization, these meetings could include engineering leaders and product stakeholders.</li></ul><p>This is not an exhaustive list of things to consider when changing how quarterly planning is done in your organization, but examples of typical considerations.</p><p><strong>The idea is to adopt a Kanban-like planning methodology for long-term planning, so teams can pull in epics whenever they are ready, without a fixed quarterly planning cadence.</strong> By following this proposal, you can reduce the number and length of planning meetings, not to mention the year’s worth of epics in the backlog that will give your teams a better sense of what’s coming next.</p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/better-quarterly-plannings"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=531ab628cdb4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Releasing Major Software Versions]]></title>
            <link>https://nthgergo.medium.com/on-releasing-major-software-versions-a9201313b15b?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9201313b15b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Thu, 19 Nov 2020 22:10:43 GMT</pubDate>
            <atom:updated>2020-11-19T22:10:43.601Z</atom:updated>
            <content:encoded><![CDATA[<p>As software engineers, the goal is always to improve the quality of the software we help develop, especially if other engineers are depending on this quality to complete their own projects. We want to be proud of the engineering solutions we devise. These improvements come with a price, however; especially if we change the API, the contract between ourselves and developers that use our libraries or frameworks.</p><p>To illustrate this point, I present the story of how the versioning policy for <a href="https://baseweb.design/">Base Web</a> evolved.</p><h3>The Inception of a Library</h3><p>When we started working on the library, we wanted to get it into other developers’ hands and collect feedback through usage. Creating the perfect first release was never our intention. <strong>Our goal was to learn and iterate quickly, until we had created a library engineers found useful.</strong></p><p>It also meant that we released multiple major versions in a short period, to comply with <a href="https://semver.org/">SemVer</a>. In five months, we’ve released five major versions. Here are a few examples:</p><p>This approach worked initially, and we learned a lot about our users, but it wasn’t sustainable as more developers at Uber and beyond started using Base Web.</p><p>Even the smallest major version release creates work for product teams that depend on your platform, which increases the likelihood you’ll introduce regressions.</p><h3>Rise to Fame</h3><p>After the rapid prototyping phase — and once Base Web became popular — it was time to stabilize the library, and create expectations among users anticipating major software releases. For this, we published a public <a href="https://baseweb.design/discover-more/roadmap/">roadmap for Base Web</a>.</p><p>In this document are a few key pieces of information:</p><ul><li>Major version release cadence, set for a year.</li><li>Changes users should expect in the next major version.</li></ul><p>The new approach came with its own set of challenges. Major updates usually contained small API changes, localized to a handful of components. In the new approach, API changes are accumulated until the next major upgrade, so updating host applications takes more effort. To help product development teams upgrade Base Web, we released codemods for each major update, which allowed automated upgrades to the latest version of the library. You can find an example of a codemod in the <a href="https://baseweb.design/blog/base-web-v9/#codemod">Base Web v9 changelog</a>.</p><p>We also noticed, that different people had different ideas on what breaking changes meant for them. Would visual updates to components count as a breaking change? Questions like these got addressed in Base Web’s <a href="https://baseweb.design/discover-more/versioning-policy/">Versioning Policy</a>.</p><p>To take it further, we updated Base Web for all projects depending on the library for internal users whenever a new release was avilable. In your own projects, be sure you can complete the upgrades without breaking any functionality in the host applications. As Base Web is a React component library, we developed a visual regression test suite for all applications that depend on Base Web.</p><p>With this approach, the platform team becomes responsible for maintaining technical debt instead of shifting it to the product teams right away. In fact, this is one of the main reasons we have platform teams.</p><h3>Key Takeaways</h3><p><strong>When you start a new project, it’s perfectly acceptable to experiment and learn quickly.</strong> No one gets it right the first time. Be upfront about this with your stakeholders, however, so they can plan accordingly.</p><p><strong>Balance who needs to address tech debt and when it needs to be addressed.</strong> If you serve many product development teams, consider how to reduce the effort necessary to supply them with major versions of your library or platform.</p><p><strong>Publish a roadmap.</strong> A roadmap is more than just a set of goals for your team. It informs your users about the cadence of your major version releases, and what to expect in them.</p><p><em>Thank you go to Chase Starr, Graham Murdoch, Nadiia Dmytrenko and Vojtech Miksu for contributing to Base Web’s release cadence.</em></p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/on-releasing-major-software-versions"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9201313b15b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mentoring First-Time Managers]]></title>
            <link>https://nthgergo.medium.com/mentoring-first-time-managers-da2a30a9047?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/da2a30a9047</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[mentoring]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 14:51:41 GMT</pubDate>
            <atom:updated>2020-11-02T14:51:41.088Z</atom:updated>
            <content:encoded><![CDATA[<p>Transitioning from a software engineering position to a managerial one can be quite a leap. The roles are drastically different from one another, and without mentors, it can be a daunting task. It’s our job as engineering leaders help new managers navigate the change. This article offers a few practical tips you can follow to help new engineering managers succeed.</p><p>Whenever I start coaching new managers, the first thing I do is set up a recurring time to meet, talk about progress, and provide feedback. Similar to the <a href="https://nemethgergely.com/blog/meaningful-1-1#keep-record-of-your-1-1s">1:1s I do with team members</a>, I keep track of these conversations in a shared document. This gives us a place where we can record our progress and assign action items to each other. During these 1:1s, I tend to focus on the areas detailed below.</p><h3>Preparing for 1:1s</h3><p><strong>One of the first tasks a new manager will undertake is to hold regular 1:1s with their team members.</strong> For most people it will be the first time they sat on the other side of the table. I believe 1:1s are the most important meetings I have during the week, as they allow me to build connections with team members. I find it essential that we prepare first-time managers for their first 1:1s.</p><p>As part of this exercise, we examine what the first few 1:1s might include, and how they can best prepare. I ask them to think about their questions their team members are most likely to ask:</p><ul><li>What are your expectations for me?</li><li>What’s your vision for the team?</li></ul><p>New managers should also prepare a few questions for their team members, on topics like their preferred way to receive praise, or their preferred way to communicate:</p><ul><li>How do you like to receive recognition? Are you okay with occasional public praise?</li><li>How do you prefer to receive critical feedback?</li><li>Do you have any clear career goals I can help you achieve?</li><li>What’s one thing you really liked and disliked about your work relationship with your previous manager?</li></ul><p>It helps build an honest relationship between first-time managers and their team members if the manager acknowledges in their first 1:1s that she is new to management, and may need some help growing into the position. This small act contributes to healthy feedback culture within the team.</p><h3>Start a reading club</h3><p>“Learn from the mistakes of others. You can’t live long enough to make them all yourself,” as the saying goes. I believe reading about management can accelerate one’s journey into becoming comfortable at it, especially for understanding how things can go wrong.</p><p>I recommend picking a book on management and studying it with your mentee. You can meet when you’ve both had the time to read the next chapter and discuss it in depth. Ask your mentee to summarize the takeaways from that chapter, and bring questions they want to discuss. Also, prepare a few questions about what was most important for you in that chapter.</p><p>I usually go with <strong>The Manager’s Path</strong> by <a href="https://www.camilletalk.com/">Camille Fournier</a>.</p><h3>Start slowly</h3><p>If possible, let new managers start with a handful of people.</p><p>First, this gives them the opportunity to transition slowly from their role as an individual contributor to a manager, and give them a chance to continue writing <a href="https://nemethgergely.com/blog/coding-as-an-engineering-manager">code as an engineering manager</a>. However, it’s important to emphasize it’s no longer their primary role, so it can’t take precedence over their managing responsibilities.</p><p>Starting slowly also gives new engineering managers time to learn their duties. They’ll have a better sense of how to prioritize their time once they’ve seen a few product planning cycles and performance and promotion seasons.</p><h3>Be patient</h3><p>Remember all the mistakes you made as a new manager? I can certainly remember mine. For more seasoned engineering managers, some tasks may appear straightforward. You should always try to put yourself in the first-time manager’s shoes, though. They’ll probably need guidance on how to handle performance reviews or engage in hard conversations.</p><p>We all make mistakes, especially when we start a new position. It’s okay to cut them some slack in the beginning, provide timely feedback and guidance, and help them grow.</p><h3>Give them an out</h3><p>Not everyone finds joy in management, so it’s important to give new managers an out if they want to transition back to software engineering. Be clear about this upfront, so first-time managers don’t feel pressured to continue in a role that’s not a good fit, which would only hurt the team in the long-term or cause them to leave your company altogether.</p><p>Instead, let them transition back to an individual contributor role if that’s where they are most effective.</p><h3>Further reading</h3><p>This article only scratches the surface of how we can help first-time managers succeed. For more on the topic, check out the books <strong>The Manager’s Path</strong> by Camille Fournier and <strong>The Making of a Manager</strong> by Julie Zhuo.</p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/mentoring-first-time-managers"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da2a30a9047" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Truth Behind Employee Pulse Surveys | Gergely Nemeth]]></title>
            <link>https://nthgergo.medium.com/the-truth-behind-employee-pulse-surveys-gergely-nemeth-a74cc266a0d4?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a74cc266a0d4</guid>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[surveys]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Thu, 29 Oct 2020 03:29:12 GMT</pubDate>
            <atom:updated>2020-10-29T03:29:42.147Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Truth Behind Employee Pulse Surveys</h3><p>Every once in a while, you might receive an email in your company inbox asking for feedback on a survey called the Employee Pulse, the Employee Satisfaction survey, or something similar. If you’re a manager, you’ll likely receive the results of these surveys, comparing your department to the rest of the organization.</p><p>The common thread in these surveys is that they gauge employee satisfaction in a few different areas. They cover things like how people’s direct supervisor is performing, whether or not they agree with the company’s vision, or if they plan to remain with the company in the future.</p><p>Statements are rated on a scale from 1 to 6, with 1 to 2 being unfavorable, 3 to 4 neutral, and 5 to 6 favorable. For example:</p><ul><li>My manager proactively solicits feedback.</li><li>My manager creates a safe environment built on trust and respect.</li><li>My manager communicates how our team contributes to the company’s overall mission.</li><li>Our company is committed to doing the right thing.</li></ul><p>These statements will have a favorability score, which is the percentage of the respondents who rated the questions favorably.</p><h3>The Problem with Pulse Surveys</h3><p><strong>As with all surveys, Employee Pulse surveys are subject to </strong><a href="https://en.wikipedia.org/wiki/Recency_bias#:~:text=Recency%20bias%20is%20a%20cognitive,before%20being%20dismissed%20to%20deliberate."><strong>recency bias</strong></a><strong>.</strong> Whether good or bad, everyone generally places more importance on recent events than those happened weeks or months ago. A good way to fix this is to conduct these surveys more frequently, though we must also be aware of survey fatigue and avoid overdoing them. Once every quarter is a good cadence to start.</p><p><strong>People with negative feedback are more likely to fill out a survey to see improvements.</strong> If your response rates for surveys are low, it might be that employees with critical feedback are overrepresented in the respondents. For a more accurate picture, make sure your response rates are close to 90%.</p><p><strong>Employees’ interpretation of statements does not necessarily align with yours.</strong> Employees will have different perspectives about employee pulse survey questions, so you might not be measuring what you intended.</p><p><strong>Finally, metrics collected by employee surveys are suspect to gaming.</strong> If managers are measured and compensated based on employee survey results, their motivation could change from making teamwork improvements to simply putting up better numbers.</p><h3>Understanding and Improving Team and Company Health</h3><p><strong>The goal is not to improve the metrics, but to make meaningful changes that improve everyone’s work-life balance, productivity, and morale.</strong> Once you are successful in that, the employee survey ratings will improve, too. I usually try to follow a process like this to get to the truth behind employee pulse surveys:</p><p><strong>First, understand and identify five questions you want to improve in the next cycle.</strong> I’d caution you against picking more than five questions, as any more risks spreading your efforts too thin instead of focusing them.</p><p><strong>Once you have the areas on which to focus, use your one-on-ones to discuss them.</strong> I find it important to discuss problem areas because numbers don’t always reveal the nature of issues, just that there may be problems.</p><p>Ask team members to think about specific examples that the manager, team, or the company didn’t do well, and how these processes can be improved. Identify action items the manager, team, or company should complete to move forward. Follow this process with everyone on your direct team. It’s important to emphasize to team members that you’re not asking for specifics about the ratings they provided, nor specific examples involving them, but general observations.</p><p><strong>After you’ve spoken with everyone, identify common pain points and action items for each area.</strong> Discuss your findings openly with the team, but keep confidentiality in mind. Communicate the action items you take personally, as well as those for the team and those for escalation to upper management.</p><p><strong>Finally, make sure you deliver on promises made to team members.</strong> Every once in a while, consider giving your team an update on the goals you set out for yourselves, and ask for their help when needed.</p><p>If the team’s health improved through meaningful changes you’ve made, this should be reflected in the next employee pulse survey. Perhaps new issues will come up for that survey, except now you can follow the above framework and understand the truth about the survey’s results.</p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/the-truth-behind-employee-pulse-surveys"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a74cc266a0d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Tyranny of Metrics]]></title>
            <link>https://nthgergo.medium.com/the-tyranny-of-metrics-a3b5bfde29d?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3b5bfde29d</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Tue, 27 Oct 2020 15:14:03 GMT</pubDate>
            <atom:updated>2020-10-27T15:14:03.913Z</atom:updated>
            <content:encoded><![CDATA[<p>There seems to be a growing trend in technology — and in all aspects of our lives, really — to measure everything: business outcomes, organizational success, and individual performance. I wrote about <a href="https://nemethgergely.com/blog/engineering-productivity">engineering productivity</a> and how I disagree with measuring individual performance based on metrics before, so I was excited to start reading <a href="https://press.princeton.edu/books/hardcover/9780691174952/the-tyranny-of-metrics">The Tyranny of Metrics</a> by Jerry Z. Muller.</p><p>In 1975, two social scientists named <a href="https://en.wikipedia.org/wiki/Donald_T._Campbell">Donald T. Campbell</a> and <a href="https://en.wikipedia.org/wiki/Charles_Goodhart">Charles Goodhart</a> independently identified patterns as they researched the idea of pay for measured performance. Campbell claimed “the more any quantitative social indicator is used for social decision-making, the more subject it will be to corruption pressures, and the more apt it will be to distort and corrupt the social processes it is intended to monitor.” In other words, when a given metric becomes the target, some participants will start gaming for their gains, so the metric stops being a good indicator of what it was initially intended to measure. Goodhart as paraphrased by Marilyn Strathern, says nearly the same thing, “when a measure becomes a target, it ceases to be a good measure.”</p><p>In the book, Muller draws on both Campbell and Goodhart’s expertise, then provides more insights on metrics fixation and the detrimental effects they have on our everyday life.</p><h3>Key Takeaways</h3><p><em>As we introduce more and more metrics, we fall prey to the distortion of information.</em></p><p><strong>We tend to measure what’s the easiest to measure and because of that, we tend to measure inputs rather than outcomes.</strong> It’s a natural human tendency to simplify problems; in most cases, measuring what’s important is a challenge.</p><p>One example of this fallacy is charitable organizations. It’s difficult to measure their outcomes, so foundations and governments measure the percentage of each charity’s budget on fund-raising and administrative costs as a proxy for efficiency. This metric’s collection and publication led to underspending on staffing and degraded capabilities, interfering with their operations. As with any organization, charities require competent staff, suitable office space, and efficient information systems. To help, their leaders often try to game the system by reporting that most of the staff works on projects, which leads to a loop in the system since organizations are valued according to ever-improving numbers.</p><p><strong>We tend to degrade information quality through standardization.</strong> Numerical data allows us to compare things more easily, whether it’s humans or entire organizations. When we compare these things, however, we often miss out on important context. As numerical data washes away uncertainty, we stop looking for those nuances.</p><p><strong>We tend to replace judgment with metrics.</strong> “The demand for measured accountability and transparency waxes as trust wanes,” as Muller puts it. The author reasons that lack of trust leads to creating new metrics, contributing to the decline of reliance on our judgment. It usually happens because of our belief that numbers convey objectivity, so they become a safer bet than judgment.</p><p>One academic institution in Great Britain measured faculty members by the number of publications they published in a Research Assessment Exercise, so they were incentivized toward quantity over quality. This led to a bias towards short-term publication instead of long-term research. Worse, they began to add metrics on top of metrics once they realized researchers were catching on, like counting how often an article was cited to measure its “impact”. The problem is that this approach doesn’t distinguish between positive and negative references. One person might tweet that the article was useful; another might say it was worst article ever written on the topic. Both would count as a reference to this article. Academia has encountered the same problem.</p><p>Wouldn’t it be better if we’d trust each other’s professional judgment? Using academia as an example, the assessment could come from a small committee or a department chair.</p><p><em>We don’t just suffer from distortion of data, but there will be inevitable attempts to game the metrics.</em></p><p><strong>We tend to improve the metrics by distortion of data.</strong> This happens when participants omit or re-classify data points that reflect on them unfavorably. This type of gaming the metrics is more frequent in policing, since politicians demand decreased crime rates to show their constituents.</p><p>Police departments collect crime numbers through <a href="https://en.wikipedia.org/wiki/CompStat">CompStat</a>. Originally a software solution, CompStat has become a broad program that combines management, philosophy, and organizational management tools for police departments. Its purpose was to provide insight into crime hot spots, so the police could deploy resources accordingly, but this was lost when politicians began demanding better numbers. Some police department heads started to believe their careers depended on improving these statistics. As a result, break-ins became “trespassing” and theft became “loss of property”. Essentially, major crimes became minor offenses so police department heads could produce favorable data for their superiors.</p><p><strong>We tend to improve the metrics by lowering the standards.</strong> In software engineering, lowered standards usually occur when a group repeatedly violates their SLAs, and instead of fixing the root causes, they just keep increasing the error budget.</p><p><strong>We tend to game the metrics by creaming.</strong> This happens when we pick simpler targets with less challenging circumstances, making it easier to reach goals, which invites complacency and stagnation.</p><p>Consider a medical practice where compensation is tied to the success rate of surgeries. Some surgeons will pick up cases that are less complicated so their performance indicators look better. This can leave patients with more serious issues on the sidelines with qualified doctors avoiding their cases.</p><p>There are also inspiring examples of using metrics in hospitals, however. Peter J. Pronovost and company created a checklist of five simple ways to reduce a type infection that was troubling hospitals. They collected metrics on infection rates, and made them public, which led to pressure for other hospitals to make improvements. The project was a success, because the metrics weren’t used to penalize or compete, but show their peers the infection rates were manageable.</p><p>We also <strong>tend to underestimate the cost of collecting metrics.</strong> Data collection often means adding more people to an organization, some whose sole responsibility is to make sense of all the numbers.</p><h3>Conclusion</h3><p>We can run into a lot of pitfalls when creating new metrics. If you are about to create a new metric, ask yourself these questions:</p><ul><li>What is the information you are trying to measure? Metrics on human activities tend to become unreliable, since it’s human nature to react to being measured.</li><li>Is the metric you picked a good proxy for the information you are trying to measure ? If not, you probably do not want to measure it.</li><li>Do you really need one more metric? Think about the additional costs it would take to analyze the new metric. Information is never free.</li><li>Will you publish the data for internal use or for external consumption? Think about the policing example above.</li><li>Who should be involved in creating a new metric? Getting the buy-in from participants is easier when they drive the metric’s creation.</li></ul><p>Sometimes, the best metric is no metric.</p><p><em>To learn more, check out </em><a href="https://press.princeton.edu/books/hardcover/9780691174952/the-tyranny-of-metrics"><em>The Tyranny of Metrics</em></a><em> by Jerry Z. Muller.</em></p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/the-tyranny-of-metrics"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3b5bfde29d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coach! Football is life. | Gergely Nemeth]]></title>
            <link>https://nthgergo.medium.com/coach-football-is-life-gergely-nemeth-74032348f641?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/74032348f641</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Fri, 09 Oct 2020 15:42:37 GMT</pubDate>
            <atom:updated>2020-10-09T15:43:36.250Z</atom:updated>
            <content:encoded><![CDATA[<h3>Coach! Football is life.</h3><p>When we began watching a new TV series called <a href="https://www.rottentomatoes.com/tv/ted_lasso">Ted Lasso</a>, I wasn’t sure what to expect. The show is about an American football coach named Ted Lasso, who takes over a premier Premier League soccer team despite having dubious qualifications at best. I don’t regret a single minute I’ve spent watching this show. Quite the opposite, in fact: I’d say that Ted Lasso is one series we all need in 2020. Underneath the comedy and sports metaphors is a reminder that being kind to one another can make a difference.</p><p><strong>Ted Lasso is also a reminder of what good leadership looks like.</strong></p><blockquote><em>The rest of the article contains spoilers.</em></blockquote><p><strong>Ted understands that leadership comes from everywhere.</strong> He asks for everyone’s input, which is how he discovers Nathan, the club’s equipment manager. Ted quickly realizes Nathan has valuable insight into which strategies worked in the past and which ones didn’t, and Nathan’s strategic mind allows him to become one of Ted’s most trusted advisers.</p><p>Not only does Ted use everyone’s input in his decisions, but he is <strong>quick to course-correct</strong> if a decision needs to be changed. He doesn’t blame anyone else when things go wrong, but takes full responsibility for his choices.</p><p>There are numerous examples when Ted shows <strong>he is an excellent listener</strong>. He takes pauses to consider what was said, and he asks lots of questions. The show’s screenwriters created a powerful scene to show what could happen if someone doesn’t listen well. The club’s previous owner thinks he tricked Ted into a losing bet in a darts game, only to find out the hard way Ted is an exceptional dart player. “Be curious, not judgemental,” as Ted put it.</p><p>Ted shows he is vulnerable throughout the series. <strong>He leads with empathy.</strong> Empathy is one of Ted’s greatest assets as a leader. Even when they lose the last game of the season to Manchester City, he congratulates Jamie, a <a href="https://en.wikipedia.org/wiki/Forward_(association_football)">forward</a> who left Ted’s club on bad terms earlier in the season.</p><p>Ted is passionate about creating teams that have each other’s backs. He is always first to offer support to each team member in struggles and triumphs. As a result, his team members begin to replicate his behavior; that is, <strong>he leads by example</strong>.</p><p>Ted also surrounds himself with smart and passionate people, like Dani Rojas: Coach! Football is life.</p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/coach-football-is-life"><em>https://nemethgergely.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74032348f641" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playbook for Running Sprints]]></title>
            <link>https://nthgergo.medium.com/playbook-for-running-sprints-d43050e929ca?source=rss-732ca3d84cb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d43050e929ca</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Gergely Nemeth]]></dc:creator>
            <pubDate>Sat, 19 Sep 2020 20:42:36 GMT</pubDate>
            <atom:updated>2020-09-19T20:43:29.731Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are reading this piece in 2020 as a member of an engineering/cross-functional team, chances are that the team you are on uses some mix of waterfall, scrum and kanban principles for planning. But what does that mix look like? Is it working well for the team, or is it getting in the way of product development?</p><p>This article attempts to describe the “Ideal Sprint” or well, to put my thoughts down on what I’ve seen working well during my years as a software engineer and engineering manager.</p><h3>Characteristics of Efficient Sprints</h3><p>When I think about what makes sprints efficient, my thoughts are usually around these goals:</p><ul><li><strong>The team always works on the most important stories.</strong> The most important work item can be defined broadly, but it can be the features that provide the most value for the customer or eliminating the tech debt that slows the team down.</li><li><strong>We have a healthy feedback culture on the team.</strong> Retrospectives are about discussing real problems and solutions for them.</li><li>The team has estimations to ensure that we have a rough idea of when given projects are shipping.</li><li>We have to ensure that there are no single points of failure on the team: multiple engineers should work on the same problems. This enables the team to work together: stories are not created for individuals, but for the group as a whole.</li></ul><h3>The framework</h3><p>Let’s start with a few rough definitions:</p><ul><li>The <strong>backlog</strong> is a semi-prioritized list of things that the team eventually wants to work on. Stories in the backlog may never get picked up, depending on priorities.</li><li><strong>Stories</strong> are work items that never take more than a week to accomplish. The time limit on them is critical. It helps teams with story sizing.</li><li>During <strong>backlog refinement</strong> (or grooming), the whole team gets together to estimate stories using story points and prioritize the backlog taking the new stories and potentially shifting priorities into account.</li><li><strong>Story points</strong> are abstract units for measuring complexity. During backlog refinement, story points are assigned to new stories.</li><li>The <strong>scrum master</strong> is the team member responsible for running the scrum meetings and helping unblock engineers on the team. The team can decide to rotate the scrum master every few sprints.</li><li><strong>Velocity</strong> is the sum of the story points the team takes on and finishes in any given sprint.</li></ul><p>Now that we got most of the definitions out of the way, let’s take a look at what processes the team follows and the lifecycle of stories.</p><h3>Meetings and their purpose</h3><h4>Backlog refinement</h4><p>Every other week, the team has a backlog refinement session. <strong>The goal of this meeting is to estimate any new stories and change their order (priority) in the backlog.</strong> To get the most out of this session, the scrum master has to prepare: they need to know what stories will be estimated, and if the stories have enough context so the team can estimate them. If not, the scrum master has to ask for clarification before the meeting takes place. If by the time of the backlog refinement meeting there is not enough information to estimate a story, the team skips the story.</p><p>The estimation of a story may go something like this:</p><ol><li>The scrum master summarizes the story on hand in less than a minute and asks if anyone on the team has questions or can proceed to estimation.</li><li>If the team has questions, we first discuss them and ensure that everyone has the same understanding of the work item.</li><li>The group estimates the story by anonymously voting using tools like <a href="https://hatjitsu.toolforge.org/">Hatjitsu</a> or <a href="https://scrumpoker.online/">Scrum Poker</a>.</li><li>If there was a close to a unanimous vote, the scrum master picks the estimation and assigns it to the story.</li><li>In case of a big spread, the scrum master asks the team who wants to speak up and reason why they thought the given story should be estimated the way they estimated it. After some discussion, the team re-estimates the story.</li></ol><blockquote><em>When a team adopts estimation that never did it before, it may be helpful to think about story points as time estimations: one story point for one day of work should do. After a few sprints, the team can slowly move away from the time estimation and start trying to assign story points based on each story’s complexity.</em></blockquote><h4>Retrospective &amp; Sprint planning</h4><p>This meeting consists of two parts. The first part is a retrospective for the sprint the team is about to close and <strong>the goal of this part is to give kudos and discuss problems</strong>. The group spends the first few minutes highlighting what went well and what needs to be improved by collaborating on a shared document. After five minutes, or when folks stop typing, the scrum master starts going through the items, and the team briefly discusses them. One of the most important parts of this meeting is to discuss what needs to be improved and assigning clear owners of the action items.</p><p><strong>The second part of this session is sprint planning, with the goal to understand the team’s velocity, and what will be the main focus for the next sprint.</strong></p><p>You could follow an agenda similar to this:</p><ol><li>Go through the current sprint’s open stories, and make sure they are up-to-date. Move the in progress and unstarted stories to the next sprint.</li><li>Take a look at holidays and planned vacations for the next two weeks. This both helps with capacity planning and ensures team members know when their peers will be out.</li><li>Agree on the targeted velocity for the next sprint by looking at past sprints and considering planned vacations.</li><li>If there are new stories that will need to be included in the next sprint, do a quick estimation session.</li><li>Discuss what the next sprint priorities should be and start pulling in stories. Decide if the stories spilled over from the previous sprint are still a high priority, or if they should be moved out. A key input for priorities should come from the prioritized backlog: a big chunk of the capacity should be filled in with stories from the top of the backlog.</li></ol><blockquote><em>You can use this </em><a href="https://docs.google.com/document/d/1myAewuUZLuJvcYyqr1R19QZEt3HPqsqVBY-RTHuRFIw/edit?usp=sharing"><em>template to keep track of retros and sprint plannings</em></a><em>. The planning section is filled out during sprint planning, and the retro section is filled out during the Retrospective meeting in two weeks. So in practice, you’ll edit two of these documents during this meeting, one for the past sprint, and one for the next one.</em></blockquote><h4>Standups</h4><p>As most of us have a slightly (or vastly) different schedule, daily standups can be challenging, especially if you are part of a globally distributed team. Instead of doing daily standups, I prefer doing standups twice a week, using Slack.</p><p>It has the following benefits:</p><ul><li>Standups provided through Slack are easier to consume and follow up on: using threads, we can have longer conversations without taking up time from the entire team.</li><li>In my experience, standups are more structured if provided through Slack. Every Tuesday and Thursday, a Slack bot can remind people to provide their standup using a template, reminding folks what should be included in their update.</li></ul><h4>Putting it all together</h4><p>I found it best to start sprints on Mondays and close them the next Friday. This way, calendar weeks directly maps to sprints, without any cognitive overhead (like starting sprints on Wednesday).</p><p>With this in mind, a calendar for a sprint for a scrum team may look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/0*23NiyvmT7fjc8Xd8.png" /></figure><h3>The lifecycle of a story</h3><p>Now that we covered the definitions and the meetings involved in efficient sprints let’s also recap the lifecycle of stories.</p><p>Every story is created equal — we do not differentiate between bugs, feature work, or discovery (spike). They go through the same estimation and prioritization sessions. This way, the team can better plan each sprint the amount of work they can take on.</p><ol><li>The story/bug/spike is created and placed at the bottom of the backlog</li><li>The team meets for backlog refinement and sprint planning to look at new items, estimate and prioritize them.</li><li>The story gets pulled into one of the next sprint (or will sit in the backlog for eternity).</li></ol><h3>Sprints &amp; planning cycles</h3><p><strong>Okay, okay, but how does this process fit into quarterly/semi-annual planning cycles?</strong></p><p>Ideally, in your planning cycles, you set goals using <a href="https://www.whatmatters.com/get-started/">OKRs</a>. These goals will be the primary inputs for your prioritization discussions during sprint planning and backlog refinement.</p><p><strong>Another question that can also come up when following this framework is how the team will meet deadlines?</strong></p><p>Taking a look at the team’s average velocity and summing up the estimations for stories required for a feature or release gives a relatively accurate picture of when a team can ship a feature. Estimations also empower the engineering team to help decide what parts could be cut to make a deadline.</p><p><em>I realize that these answers barely scratch the surface, but they deserve an article of their own. Be on the lookout, I am planning to work on them next!</em></p><h3>Conclusion</h3><p>By following this framework, you can create a streamlined sprint planning process that only adds less than an hour of meeting overhead to the team’s weekly schedule: the backlog refinement takes only half an hour. The joint retrospective and sprint planning meeting an hour.</p><p>I am thrilled that we created this sprint planning framework — it saves the teams following it countless hours spent in meetings, and helps them keep focused. It also reduces the friction caused by annual, semi-annual, or quarterly plannings.</p><p><em>Special thanks go to </em><a href="https://www.linkedin.com/in/chasestarr/"><em>Chase Starr</em></a><em>, who contributed a lot to the framework I described above!</em></p><p><em>Originally published at </em><a href="https://nemethgergely.com/blog/playbook-for-running-sprints"><em>https://nemethgergely.com/blog/playbook-for-running-sprints</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d43050e929ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>