<?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 Michal Ličko on Medium]]></title>
        <description><![CDATA[Stories by Michal Ličko on Medium]]></description>
        <link>https://medium.com/@licko61?source=rss-77b3a5dd189e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Fzc5BbMZJuMCFW6gZVp18w.jpeg</url>
            <title>Stories by Michal Ličko on Medium</title>
            <link>https://medium.com/@licko61?source=rss-77b3a5dd189e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:00:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@licko61/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[Run for fun or chase the medal?]]></title>
            <link>https://medium.com/productboard-engineering/run-for-fun-or-chase-the-medal-20e068375b23?source=rss-77b3a5dd189e------2</link>
            <guid isPermaLink="false">https://medium.com/p/20e068375b23</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Michal Ličko]]></dc:creator>
            <pubDate>Thu, 19 Nov 2020 09:27:33 GMT</pubDate>
            <atom:updated>2020-11-19T09:28:21.001Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The personal growth of an individual is indeed very individual — and that’s how managers should approach it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BwwAajuvR8bJeiyC" /></figure><p>Let’s imagine two hypothetical characters, John and Paul. John wakes up every morning, takes his running shoes from the rack, and runs into the forest next to his house. He usually runs for around an hour. If he feels great, he runs faster or longer, but he doesn’t care how fast or how far he runs.</p><p>Paul wakes up every morning and goes running the same way John does. However, unlike John, he has a plan. He desperately wants to run 10k in under 40 mins and chase the medal in the local competition, which is in three months. He also has a precisely designed plan for every day. Today he should run 8k at a steady pace between 4:15 and 4:25 min/km.</p><p>In the end, John decides to go to the competition as well because his friends will be there and it might be fun. Both guys finished the track in under 40 mins.</p><h3>Identify motivation</h3><p>The conclusion is that there were at least two different “career” paths leading to the same result. If you have read Kim Scott’s amazing book <a href="https://www.amazon.com/Radical-Candor-Kim-Scott/dp/B01KTIEFEE"><em>Radical Candor</em></a>[1], you will recall her division of people into Rockstars (John) and Superstars (Paul), with neither of the two being better or worse than the other.</p><p>While Paul is most probably motivated by future results, status, money, or recognition, John is living in the moment and is motivated by the joy it brings him. But how to help these people get what they want and increase their value for the company at the same time?</p><p><strong>Practical tip:</strong> Try a tip from <em>Radical Candor</em>: Identify motivators. One great way to do this is through an interview. Ask the person to walk you through his or her past experience and pay attention to all the decisions they made, especially regarding career changes.</p><p>This interview is very similar to a normal interview where you are evaluating a candidate. The big difference is that you might have already built trust with the person you are interviewing, so the conversation will be much more honest.</p><p>I talked to one of my team members once, realizing that this manager always wanted to open his own cafe. His motivation is to gain the management experience and money he needs to one day run his own business. After we’d identified that, we were able to have much more honest conversations about his goals and the types of challenges that interest him.</p><h3>Have your ambition set right</h3><p>With people like Paul, their ambition should be fairly obvious, but it might not be entirely easy to achieve. Paul wants to be promoted a level up. But the more intangible and unreal this ambition is, the more frustrated he can be. He might be asking what he should do to be ‘good’ enough.</p><p>Career ladders typically describe the responsibilities and expectations of an individual in each position, but they rarely say anything about how to get there. Rather, they might be based on the “I’ll know it when I see it” principle. The existence of such a list of steps might cause people to make only minimal effort to tick the box, proceed to the next item, and expect promotion once the list is completed.</p><p>The point is, such a list cannot be finite, and being motivated only by sitting on a better chair might be considered dangerous and the “wrong” kind of ambition. Ben Horowitz said: ”The wrong kind of ambition is an ambition for the executive’s personal success regardless of the company’s outcome.”[2] Although he is mainly talking about how to run the company at an executive-level, I think this might be at least partially applied to any level.</p><blockquote><strong>“Talent wins games, but teamwork and intelligence win championships” </strong>— Michael Jordan</blockquote><p>So a person’s primary goal should be to increase his or her impact on the company’s revenue, with a possible promotion being the secondary goal that reflects their hard work and impact on the company. This is easy to say but hard to implement.</p><p>I’ll return back to Paul. Besides being a runner, he is also a developer and wants to become a senior-level engineer, be recognized, and get more money. To help him grow, any goal should provide guidance around how he can increase and demonstrate his impact. Such a goal might be making him accountable for solving a very complex problem that others hesitate to take on. It could also be something softer, like making team meetings more effective, or writing some tech articles for the company blog.</p><p>If done well, all of these activities might potentially increase the person’s impact. But how would you know whether it’s good enough for promotion? As I mentioned previously, promotion shouldn’t be the only target, but for people like Paul, recognition is fairly important. A great way to approach this might be through department-wide calibration.</p><p>The main purpose of calibration is to preserve the level of standard for each position where people should have a similar impact. In Paul’s case, we might compare him to other colleagues in senior positions and see whether or not there is still a gap. The topic of calibration would fill up the pages of a whole new article, but to cut a long story short, the main advantage is that the person might compare themself to other colleagues and therefore see areas for improvement more clearly.</p><h3>Opportunity to shine</h3><p>To quote Lara Hogan, “To sponsor someone is to feel on the hook to help get someone promoted.” [3] Increasing one’s impact within the company might be extremely hard if there are no challenges to demonstrate your higher impact, new skills, or experience.</p><p>I have seen some people stepping up on their own, finding the right challenge, and nailing it down. But this is very rare and sometimes even impossible. People are usually tied up with their current working agreements and the expectations of their peers, managers, etc. That means they have very little time to focus on something outside of the day-to-day business — and if they do, it’s usually in their free time.</p><p>It is crucial for people’s growth to give them space to grow. For you as a manager, it might be giving them some extra time to find and tackle their challenges. You might spread the word, saying: “Hey, did you know Paul already tackled this issue? Have you considered consulting him?” Or: “I believe John is the right person to do the job for us.” The main difference between coaching and sponsoring is that you also help the person find the right challenges.</p><p><strong>Practical tip:</strong> Always make sure you have clearly defined WHY it is important to solve this particular problem, and HOW it will impact company business. It is much easier to measure and recognize success if you can support it with quantitative or qualitative data.</p><h3>Recognize results</h3><p>Recognition is often much more powerful than just getting more money. It is important that you identify the best method of recognition for each person. Some people need public recognition, so giving a short thank-you speech during a team, tribe, or company meeting might make them feel proud. Other people just need to hear from you during a 1:1 meeting, read a note in the company communicator, or receive a gift card for food delivery. It doesn’t matter what it is, but it must be there.</p><p>You gave the person five minutes of fame and made them feel proud, but you also gave them much more than that. Everybody just heard, saw, or read that they did something outstanding, which will help raise their reputation. Remember the calibration meeting? That’s exactly where it might help that person be promoted.</p><h3>Conclusion</h3><p>Let’s return to the running analogy. You might think this article was solely about high-achievers — the people with strong goal-orientation who are desperate for promotion. The truth is, you can apply a similar principle to both categories.</p><p>Paul will be more likely to get promoted if their ambition is set right. That’s mainly because their primary motivation is to be the best and achieve great things. You might spend more time with them because setting the right goals is time-consuming, they need to see progress faster, and it might be frustrating for them if things are moving slower than expected.</p><p>However, that doesn’t mean that the others won’t achieve promotion as well, and it would be a pity not to reveal the gem hidden in your team. For that, you need to set the right work environment and support them in what they love to do. Chances are, you wouldn’t need to spend that much time with them.</p><p>So be a sponsor for your people, set them up for success in their specific challenges, and recognize their contributions.</p><h3>Bibliography</h3><ol><li>Radical candor: How to Get What You Want by Saying What You MeanKim Scott, 2017, ISBN: 9781250103505, <a href="https://www.amazon.com/Radical-Candor-Kim-Scott/dp/B01KTIEFEE">https://www.amazon.com/Radical-Candor-Kim-Scott/dp/B01KTIEFEE</a></li><li>The Hard Thing About Hard Things, Ben Horowitz, 2014, ISBN: 9780062273208</li><li><a href="https://larahogan.me/blog/what-sponsorship-looks-like/">https://larahogan.me/blog/what-sponsorship-looks-like/</a>, Lara Hogan, quoted: 11/17/2020</li></ol><p><em>Interested in joining our growing team? Well, we’re hiring across the board! Check out our </em><a href="http://bit.ly/CareersArticlePavlina"><em>careers page</em></a><em> for the latest vacancies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20e068375b23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productboard-engineering/run-for-fun-or-chase-the-medal-20e068375b23">Run for fun or chase the medal?</a> was originally published in <a href="https://medium.com/productboard-engineering">Productboard engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Establishing project management in an agile environment — one step back and two steps forward]]></title>
            <link>https://medium.com/@licko61/establishing-project-management-in-an-agile-environment-one-step-back-and-two-steps-forward-9aa6c3548868?source=rss-77b3a5dd189e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9aa6c3548868</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[transformation]]></category>
            <dc:creator><![CDATA[Michal Ličko]]></dc:creator>
            <pubDate>Wed, 27 Mar 2019 20:01:52 GMT</pubDate>
            <atom:updated>2019-03-27T20:01:52.685Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Establishing project management in an agile environment — one step back and two steps forward</strong></h3><p><strong>Do you work in an agile company? Have you ever thought what would happen if you implemented traditional project management instead? Is agile development the best way to hit your OKRs? Read more about why we are now implementing project management principles and why agile is ending … or it isn’t???</strong></p><p><strong>A little bit of context …</strong></p><p>Before I launch into an exhaustive description of the specific steps we’ve already taken (or will in the future), I want to share a basic outline of the baseline. Our department has been running on agile (such as Scrum, Kanban, etc.) since it was established in 2006. We started with one development team, which was later extended with a product owner and scrum master so that it was able to deliver everything within the team. They actually wrote the whole advertising platform and we can consider them as a cross-functional team. It sounds pretty good, right? But after a while we started making a lot of money so we needed to expand. Expand everything. Within the last eight years we’ve hired 130 developers, 15 product owners, eight scrum masters, some UX designers, a team of researchers, and lots more. The growth was sustainable approx. till the end of 2016 and the major issues with our system appeared one by one after that. We now see the main cause as lying in the massive growth we went through during the last two years, when we nearly tripled our development capacity.</p><p>Do you remember that small cross-functional team? As long as we needed experienced people with knowledge of the system to share it with our new team members we decided to split it in half and made a most senior developers a team leader. It happened again and again until we got to the 25 teams we have now. We were so obsessed with hiring new people that we didn’t stop for a minute and ask ourselves if the current workflow and organizational structure could stand that expansion.</p><p>Focusing more on what we have now, I can say our teams are agile. They are mostly running Scrum and their workflow complies with the guidelines. The problem is that they are component-based. That creates a lack of commitment for the business value increment on the whole system and the business values we need to deliver to our (internal) customers. It also creates a strong need for communication and synchronization between the teams and we need to solve a situation in which one team gets stuck and waits until another delivers a work package that is a prerequisite.</p><p>The last straw that broke the camel’s back was a critical priority project that has been running for more than two years with more than 12 teams and six product owners involved and which is currently about a year behind schedule.</p><p><strong>Early thoughts</strong></p><p>Our first idea brought us to a project-based team with a single product owner and all the developer roles needed for achieving project goals. That was not possible for two reasons. No product manager or developer is able to cover the whole problem domain and we still need one person who will say what is more important and report on the status of the project as a whole. Another point is the fact that there are overhead costs related to the team-building process. We should expect the project to be long enough to let the team go through all <em>Tuckman’s group development stages</em> [1] to become effective and that cannot be guaranteed. Keeping that in my mind, I started to think about building some efficient system on top of our teams or maybe even rebuilding the teams to break the tech silos and support commitment.</p><p><strong>Portugal trip</strong></p><p>While reading many articles, watching videos, and going through numerous meetings I started to think about how other companies were handling these issues; are we the only company? No, for sure there must be some! Thanks to my dear friend Klara I suddenly got the opportunity to find out. As she is working in the Lisbon office of a big international company I decided to go there and see it with my own eyes. What I actually experienced was much better than I’d expected. I visited seven companies in Lisbon and Porto and talked about the process with managers at all levels, including scrum masters, team leaders, engineering managers, and even C-level executives. Every company was different and every single one had certain problems. They had one thing in common — they expanded so quickly that their former processes became obsolete. We were all able to agree that the way out of this is being as full-stack as possible but every company had chosen its own unique way of achieving it. The great inspiration for me was the chance to talk with Nuno Silva @ Pipedrive about their Tribes &amp; Missions [3] model and later also with the author of this model, CTO Martti Kuldma. On my way back, I was sitting in the plane, full of ideas and with a piece of paper, drawing my first draft of an adaptation of their model, and I was pretty sure we want it as well.</p><p><strong>Why project management?</strong></p><p>After returning to Prague I had a series of meetings with one goal — implementing tribes &amp; missions. Later on we came to the conclusion that we’re not ready for that approach.</p><p>At first it included breaking our teams into pieces and composing them back together into bigger cross-functional units. There were two issues. It was fresh in our mind how hard it was to find so many highly qualified people and we were afraid that such a big change would affect their motivation and increase staff turnover.</p><p>Second, we didn’t know how to measure the progress of the process implementation and we weren’t really sure if our company culture was ready for such a change and we didn’t want to do it in a big bang way. We also knew that some of our teams were not mature enough to embrace such a change and they sometimes have trust problems within the team, not to mention their commitment to business values. Those are very basic dysfunctions of the team [2] (Fig. 1) — right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/0*YLzBPOttNH8-CBPx" /><figcaption><strong>Fig. 1: Five dysfunctions of the team</strong></figcaption></figure><p>As long as our department is responsible for software that is making billions we cannot afford to make mistakes and start again. So my manager Tom came up with an idea which we should consider. Why reinvent the wheel and build a completely new process from scratch? Why not use something which is widely used and verified? Do we need to stabilize the current situation and hit our deadlines or do we have time to experiment? I must say I had not been thinking about that option before, but it started to make sense. We knew our process is based on chaos; no process is defined and the only reason why it worked is that we had really good people who somehow knew what to do. So we decided to implement an almost traditional project management framework on top of our agile teams and stabilize the situation in order to have some baseline for later experiments. We chose PRINCE2®️ Agile. I started by passing Taylorcox [4] PRINCE2 certification and built a process picture in my mind. At that point we knew we would have to establish a new Project Management department to have all the top-priority projects under transparent supervision. Remember the project that was one year overdue? That should not happen any more.</p><p><strong>First steps</strong></p><p>When I got permission to lead the change and stood at the head of the newly formed Project Management department I only knew three things:</p><ul><li>we want to implement Project Management principles to stabilize the delivery and make it more predictable</li><li>we don’t want to endanger teams’ agility at all</li><li>we want to further educate our people to be ready to embrace future changes</li></ul><p>So I defined three roles, <strong>Project Manager</strong>, <strong>Agile Coach,</strong> and <strong>Education Project Manager</strong>. Those three roles should cover all the areas mentioned above. We should be able to change the whole department from top to bottom and also bottom-up. Let’s do it, then!</p><p><strong>The Project Manager</strong> is responsible for project delivery from the very beginning till the final validation of the business outcome. He is a communication catalyst within the teams themselves and also between the teams and management in the sense of transparent reporting of the project status. He is also responsible for collecting the Project Product specification from a business manager and ensuring that all the parts of the specification from product owners are ready on time. It sounds a little bit like Waterfall and it really is and is not at the same time. We don’t want to perform lifelong analysis with a complete documentation and specification before writing a single line of code. Rather than that we’d like to focus on business case specification and the value the project will bring to our system. Changes of specification are still warmly welcomed, but we need to continuously measure the outcome benefits in comparison with the development effort needed for completing the project. So if we think about whether it is agile or not, it’s a Waterfall project startup with agile delivery.</p><p><strong>The Agile Coach </strong>is responsible for educating people in agile principles and developing the self-organization of the teams. We know that the changes may have a negative effect on team agility, so I decided to measure the team agility level in order to see if we can at least preserve the current agility level or even raise it. Describing how we performed an agile maturity assessment is beyond the scope of this article, but I will write something about that as well, for sure.</p><p>Maybe you’re wondering what the difference is between the scrum master mentioned above and the newly defined agile coach. The truth is that there should be almost none. The main reason we’re changing it is that we want to empower those people to change something and we’d like to give them permission to act across all the levels in the organization, not only within the team.</p><p>The <strong>Education Project Manager</strong>,<strong> </strong>as the title says, leads education projects. The key responsibility is to support the company culture by organizing knowledge-sharing sessions and meetups and encouraging our staff to present our company in public talks and articles. This role goes also far behind the scope of this article, but I mention it because it is also a key role needed to achieve my higher goals.</p><p><strong>The workflow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GykiF66JM2NkEIeC" /><figcaption><strong>Fig. 2: Project lifecycle</strong></figcaption></figure><p>Figure 2 describes the project lifecycle from the beginning till the end. We can divide it into four stages: Prioritization, Pre-project, Development, Closing-up.</p><p>In the <strong>Prioritization stage</strong> we collect all the ideas and business opportunities and divide them into what are called business streams. Every stream has its own responsible business manager who gives the product backlog item a unique priority within the stream. You can imagine a stream as a part of our business portfolio. However, the product backlog items may affect multiple streams, but there should always be one main stream where the business value increment will be the most significant. When we have the unique stream priority it is time for a global roadmap clash, where we discuss priorities across all the streams from a global perspective and we consider each item according to its impact on departments’ OKRs. With the global unique priorities set, we don’t need to be afraid of resource clashes on teams that so far have been overloaded. That’s because we can always apply a high-priority-goes-first rule when needed. As we have the priorities approved by the board we can proceed to the next stage — <strong>Pre-project</strong>.</p><p>In that particular stage we collect the minimal requirements specification needed for business case competition, definition of acceptance criteria, and estimation of approximate complexity. In order to build a first concept of the roadmap we need to analyse which project will affect overloaded resources such as the big data team, etc. At the beginning of the stage a project manager assigned to a priority project will complete a business case outline and present the project to the Development Architecture Board, which includes the product architect (responsible for vision compliance) and all senior team leaders (responsible for one or more technological areas). This group is able to give expert estimates of the project’s complexity as a whole and also its complexity on the team level. <strong>The first draft of the roadmap is created at this point.</strong></p><p>Since we have the first estimates we know roughly which projects are more about to proceed to the next stage and which are not. Those excluded will wait until the next priority meeting, where they will be reprioritized. The others which will be the most likely to be processed need their business cases to be completed and then brought to the architecture board again to be broken down more precisely. This architecture board is much bigger and includes all the leaders of all the teams that are affected, who can give more precise estimates. <strong>The final roadmap is created</strong> and once it is approved the <strong>development stage</strong> can begin.</p><p>The development stage itself is not so interesting because it is a normal Scrum where the teams process a prioritized backlog maintained by the specialized product owner. On the other hand, an assigned project manager is responsible for the synchronization of the teams, dependency management, and reporting of project status to the board level.</p><p>When the work is done the Closing-up project stage takes place. Apart from formal presentation of the output and acceptance by the business, which is a part of the process the whole time, including each sprint review, we evaluate project metrics such as effort estimate vs. real time spent (in sprints per team). Later we measure the benefits as defined in the business case and evaluate whether we’ve lived up to our expectations.</p><p>The whole process is not bound up with projects. All the stages happen iteratively every quarter so that we can continuously evaluate the business value increment the project should bring and re-prioritize if the goals are changed.</p><p><strong>Conclusion</strong></p><p>You may see there are many things in common with Waterfall and there are, for sure, also some ideas shared with SAFE or other scaled agile frameworks. We control our time, scope, and money on projects, but we are focused on business value, we have something similar to SAFE’s collective planning during development architecture boards and we try to make the projects last on quarter at most. Does it remind you of trains?</p><p>We hereby state that there is no “good agile” or “bad project management” and all we want is to increase commitment and transparency and be on time with our projects. We also want to have a baseline which we will use to bounce off and by which we will measure the progress we made in future months.</p><p>At the end I want to say there probably won’t be another tribes and mission model in the world but there will, for sure, be another department based on highly-motivated, self-organized teams with great commitment to our global goals. I believe that we should tie down our process a little in order to loosen it a lot, take one small step back to make two great ones in the future.</p><p><strong>Bibliography</strong></p><p>[1] Bruce Tuckman’s Team Development Model (1965) — available online <a href="https://www.lfhe.ac.uk/download.cfm/docid/3C6230CF-61E8-4C5E-9A0C1C81DCDEDCA2">https://www.lfhe.ac.uk/download.cfm/docid/3C6230CF-61E8-4C5E-9A0C1C81DCDEDCA2</a></p><p>[2] Five Dysfunctions of the Team, Patrick Lencioni, 2002, ISBN 978–0787960759</p><p>[3] What is Tribes &amp; Missions, Martti Kuldma, 21.02.2019, <a href="https://www.youtube.com/watch?v=M6-2XSPSy5Y">https://www.youtube.com/watch?v=M6-2XSPSy5Y</a></p><p>[4] TaylorCox PRINCE2 Agile certification <a href="https://www.tx.cz/prince2">https://www.tx.cz/prince2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9aa6c3548868" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>