<?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 Alex Pyankov on Medium]]></title>
        <description><![CDATA[Stories by Alex Pyankov on Medium]]></description>
        <link>https://medium.com/@alexpy?source=rss-3691febd8543------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zq86n0mRoGRIYTQo.</url>
            <title>Stories by Alex Pyankov on Medium</title>
            <link>https://medium.com/@alexpy?source=rss-3691febd8543------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:21:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexpy/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[…uck! I’m an Introvert!]]></title>
            <link>https://medium.com/@alexpy/uck-im-an-introvert-2242b5f96d81?source=rss-3691febd8543------2</link>
            <guid isPermaLink="false">https://medium.com/p/2242b5f96d81</guid>
            <category><![CDATA[introvert]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Alex Pyankov]]></dc:creator>
            <pubDate>Thu, 09 Jun 2022 15:18:30 GMT</pubDate>
            <atom:updated>2022-06-09T15:18:30.626Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s not unusual to realise and accept something about yourself after many years that you didn’t want to accept or was not giving up hope that it wasn’t true. Yesterday, I gave up my hopes that I’m just a hidden extrovert that wants to be released. No, as my former colleague said after I got “ENTJ” on Myers-Briggs test: “What?! You’re an Extrovert?! Ha-ha…”.</p><p>She was so right back then, but it didn’t seem funny to me at all. I wanted to be extroverted, all the pictures of the world in my head were showing colourful illustrations of myself being fluent with people around me, kicking off conversations with any stranger, and so on and so forth, just like we all saw on the TV. It seemed like introversion is a flaw that I need to deal with. Of course, you better not “deal” with nature. It just wins in the end whatever you do.</p><p>Couple of days ago, I just went into the book store to get a cup of coffee (that’s what the modern book stores are for!) and a sausage roll (a bonus, to get some oil on your fingers before touching books). Well, there was an intention to get a kids book for a kid I was holding in my non-coffee-occupied hand as well, hence visit was legit and that crucial sausage roll helped me to calm him down. After a quick meal, we went to shelves with business literature (kids books can wait).</p><p>My son started recommending right away. He can’t read, but picture looked promising — a burning Earth with an airplane, that must be good book! And it’s rather thick! “Daddy — I want you to read this to me with a night light” [that we have grabbed after a minute in the shop (-$30)]. The book was “Davos Man: How Billionaires Devoured the World” by Peter S. Goodman (Link to Kindle Edition: <a href="https://amzn.to/3NDEcXG">https://amzn.to/3NDEcXG</a>). Honestly, I wasn’t impressed on the first pages due to a load of negativity poured over wealthy/ultra-rich business owners like Bezos, Dimon, Benioff, etc from the very first pages trying to highlight their cynicism and deceptive manners. It’s written by journalist but it feels quite water-ish to my palate, like it’s going round and round about the same thing over and over (feels like there was an request to write 600 pages, so here we are…). It’s not a bad read, very educational and entertaining, there are dives into a history of events about modern monetary system, trade unions, World Economic Forum (the one in Davos), but $12 for eBook would be a much more reasonable price than $35 that I paid for a paper one, just to make my boy a bit happier (no one saves on kids, right?).</p><p>After I got my hands occupied with coffee and a Davos guy, with book light looking outside of my pocket, I spotted the book that later changed my life (or turned it back on track?) — “The Introvert Entrepreneur: Amplify Your Strengths and Create Success on Your Terms in Ten Steps” by Beth Buelow (<a href="https://amzn.to/3tswVlv">https://amzn.to/3tswVlv</a>). It doesn’t look flashy, no burning planets or planes, but it just got my eyes on it, I had even put a coffee cup on the floor. It’s like this stupid serendipity (not some serene stupidity, be careful while reading) that one can feel, that deep touch into your gut (sausage roll, eh?).</p><p>The back of the book says: “An introvert trying to be a fake extrovert is just that: a fake extrovert”. That put me into a highly oscillating mode: is it me or not? Might be me… so let’s read some inner pages:</p><ol><li>“You are a walking contradiction”. Of course I am, that’s my strongest point — instability!</li><li>“On the one hand, you are an introvert. You tend to prefer ample alone time” — somewhat… “You appreciate blocks of uninterrupted time” — definitely. “You enjoy going deep rather than broad in whatever catches your fancy” — that’s for sure, I’m in a rabbit hole in 2 mins after opening first email.</li><li>“On the other hand, you are an entrepreneur. You are required to interact with employees, partners, clients, and customers on a regular basis.” — yesss… “You have to wear multiple hats, taking on everything…” — duh, I’m a team leader, I have to…</li><li>Sold.</li></ol><p>Now to the point, the more I read into the book, the more I find myself matching the profile of that typical introvert described in it. It was such an eye-opener and an insight on that I need to change a label. I have all the same problems and overcoming them is my kind of “working on weaknesses”. From other research and literature it’s known that it’s just better to amplify your strengths instead of working on weaknesses to achieve “better” success. I don’t remember the author, but “you can raise your weakness only to an average level, while your strength might become outstanding”. And it gave me this needed reality check that I need to stop acting like an extroverted person, I need to stop pretending to be someone I am not. All I need to do is to update my profile from ENTJ into INTJ and move on. The book is full of stories and recipes, and one of the most important (given in the very beginning) is how introverts and extroverts think and act, how we process information. This is a “killer feature” and extremely important to leverage strength of introverts in various capacities. I’m in some kind of love with the book right now, and I hope not to be disappointed to the very end.</p><p>…and then I added another $35 dollars to the bill, and kid brought be to the kid’s section, where instead of the book he took a puzzle of 200 pieces that he apparently cannot assemble himself. The price of soy latte on that day spiked at $135 AUD...</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2242b5f96d81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Evolution of Standup for 1 Particular Team]]></title>
            <link>https://medium.com/@alexpy/the-evolution-of-standup-for-1-particular-team-b5985c00e9ec?source=rss-3691febd8543------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5985c00e9ec</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[stand-up-meeting]]></category>
            <dc:creator><![CDATA[Alex Pyankov]]></dc:creator>
            <pubDate>Sun, 26 Dec 2021 01:01:42 GMT</pubDate>
            <atom:updated>2021-12-26T05:02:36.406Z</atom:updated>
            <content:encoded><![CDATA[<p>There’re 2 well-known unresolved problems in software development: how to name things and when to flush cache. In the software development management, which includes people in the equation, unresolved problems are just an on-going flow. One of those is how to do the standup meeting, which is a quick check-in meeting to cover yesterday’s work, today’s plan, and any impediments that need resolution by other teams, which are to be addressed by scrum master or person with a similar role.</p><p>Sounds simple and quick, but it might become a little rabbit-hole going down through a bunch of infernal circles. Why? Mostly, people find it either too long or largely non-relevant for them, and if it’s not relevant, they switch out and count it a waste. We don’t like waste, we’re lean, we don’t like “muda”, so we need to adjust this meeting to make it right. The goal was to make it standard 15 minutes and not lose a lot at the same time.</p><p>I’ll share my experience with what we were doing in my team for the last couple of years and some lessons learned. Perhaps, all this knowledge exists in some book already, but I was busy reading another one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5t9bq1IdtjdhjV2y" /><figcaption>Photo by <a href="https://unsplash.com/@aronvisuals?utm_source=medium&amp;utm_medium=referral">Aron Visuals</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Stage 1. Small in-office team having too long meetings</h3><p>We were a team of 4–5 working in the same office. Sometimes people were working from home, but infrequently. Problem: standups are taking 30 mins+. That was difficult to stand that much, we are IT workers, not athletes. It’s easy to guess that standups became discussions and mind wonderings; they were covering all the work done yesterday in superfine details that other people were picking up quickly and were throwing ideas around, brainstorming, and trying to make decision and solution design right there. We just wanted to share all our thoughts.</p><p>What have we done to get it done faster? Tried to work off the sprint board to follow tickets. Did it help? Not much, still mind wondering, etc, but on each ticket, which took even longer, but covered more issues. So we went further and brought… a timer! Bought a Teams app with a standup timer and async standup for those that are away, 15 minutes are split amongst participants equally, and timer beeps when you need to wrap up, and calls out people randomly. Quite good! Drawbacks: we lost a screen with a board, because app was eating the whole screen. Well, they fixed it later on, but it’s still a bit of hassle of clicking on 2 screens: in the timer-app — switch to next person, in Jira select the next person. So we just killed Jira screen and started to rely on memory.</p><p>Anyway, target of 15 mins had been achieved!</p><h3>Stage 2. Larger team with 1 always remote person.</h3><p>Surprisingly, the previous set up worked for 5–7 people as well, but having a hybrid team brought some challenges in screen sharing. We had a standup TV with a board and timer, and a Chromebook representing a remote developer. This multiscreen setup was quite hard to launch… Somehow timer died off in favour of sprint board (it’s been resurrected), but some timing inertia remained and we managed to maintain some speed and focus for this meeting without going astray in solution mode.</p><p>Lesson learned: use tools and “scaffolding” to develop habits so that you can drop scaffolds, but habits will remain.</p><h3><strong>Stage 3. More people go remote</strong></h3><p>We have got 2–3 people in remote mode and some new people on board, team size is still 6–7. Still the same flow, what I’ve done yesterday, today, blockers, but habits of short focus updates started to fade, plus we started to work in a few streams: data and apps, which were not intersecting often thus attention was drawn away from the stuff one’s not across. So we brought timer app back. :) Occasionally, we used async standups in Teams for those who were not able to attend.</p><p>Lesson learned: reintroduce abandoned tools if habit fades.</p><h3>Stage 4. All people go remote</h3><p>Pandemic hits, and work-from-home becomes a standard. Our setup developed in the pre-pandemic times stood still and didn’t shutter, it actually became better — no more sound issues like not hearing people in the office that gathered around a laptop, but… the duration bloated back into 30–45 mins, and sometimes an hour and over! I suppose everybody experienced that during the transition to remote time. The off-the-meeting time, when we could do the ad-hoc follow up on a few issues with a few people, disappeared, and it kicked off expansion of the standup time and making each update followed up instantly (or we just missed some socialising time those days).</p><p>Anyway, no one cared about timer app anymore, we had our faces in Teams filling the screen, and the only thing we have done in attempt to reduce discussions — we used this flow: blockers, plan for today, what I’ve done yesterday. It helped to focus on upcoming things and blocker resolution instead of status updates. What wasn’t good: distraction from second screen, brain workload from multiple faces moving on the screen… together mode in Teams with Cheshire cats was very handy. :)</p><p>Lesson learned: sometimes, especially at the challenging times, we need to be tolerable to our routines and just drag along for some time in a suboptimal state.</p><h3>Stage 5. 2-pizza team in hybrid-mode</h3><p>In a few months, after we all got some weight, but COVID cases in Queensland went down to zero, office reopened with a bunch of restrictions and we started to work 2 days from the office and 3 days from home. Though, 1 person got stuck overseas and we had 1 person in an always remote mode. Interestingly, after we got back to the office, the TV and the Chromebook were never used. We just joined Teams from someones laptop to get remote person in and were throwing in updates with a very small amount of discussions. Being in the office reliefs the need to go into details, and having people waiting for you puts a bit of pressure to be on track with standup plan. Though, everytime we went remote, the meeting bloated a bit.</p><p>After a few months, anxiety and news got calmer somehow, so we didn’t dive into general talks during virtual standups, and finally started being on time, well… 15–30 mins with no timers and boards on-screen, but some people were distracted by the other screen and not fully present in the meeting.</p><p>Lesson learned: self healing happens.</p><h3>Stage 6. Large team in hybrid-mode</h3><p>Team grew to 11–12 people… that’s quite big for scrum, and we couldn’t really split it as we were working on the big project. The project manager we got into the team, proposed bringing back Jira board to maintain focus and go through each ticket, but as a consequence, the meeting duration increased. Well, nothing new. Tickets were describing in a fine details, other people started to lose focus, a lot of stuff became not relevant for them, and it’s 30–60 minutes again. We have somewhat like 3–4 streams of work going through the team that don’t cross each other on the way to the big goal. Something has to be changed.</p><p>Lesson learned: increase in team size very likely will need a change in routines.</p><h3>Stage 7. Large team in hybrid-mode with async updates</h3><p>Timer might help, but there’s so many new things to talk through… so we decided to look from perspective of why we need to catch up, what is the most important thing of this meeting — blockers. The current solution is that we use nowadays is to post updates and daily plans in asynchronous mode into Teams (using that little app with the timer) and leave the meeting time for blockers and general updates.</p><p>Results:</p><ol><li>We dramatically cut down the meeting time to 15–20 mins.</li><li>It’s of a great help for me as a team leader to get everything in writing that I can refer too and spend more time comprehending (written updates via email or something else was on my mind for the last year or so…)</li><li>Feeling of waste has been decreased, because people aren’t blocked by irrelevant information, and only the potentially relevant things are communicated in the synchronous mode.</li><li>Quality of written updates seems to be a bit higher as people have sometime to think on writing and don’t have any pressure.</li><li>No sprint board to look at that might make someones mind wander or act as a distraction.</li><li>Laser focus on problem resolution, which is crucial to achieve a good flow of work. We also included into “blockers” anything that particular person needs assistance with to broadcast the call for help. The helpers are assigned instantly at the meeting in the morning to avoid uncertainty.</li></ol><p>Interestingly enough, the last couple of weeks the team shrunk in size down to 4–5 people as everybody went on the Christmas leaves, and we flipped back to sync standup as we managed to get it done in 15 mins. Lesson learned: perception of speed and time makes a difference. Everybody is ready to spend 15 mins on somewhat relevant things, but more than that is a no. Attention span is short, and as leaders and managers we need to build systems, processes, and habits that are a good fit for staff we care about and a good fit for the environment we are in. Nothing stands still though, and search for optimal solution is generally local due to too many variables in the game, but as we are empowered for changes, lets just embrace the change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5985c00e9ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sprint Your Sprint]]></title>
            <link>https://medium.com/@alexpy/sprint-your-sprint-89968e45d562?source=rss-3691febd8543------2</link>
            <guid isPermaLink="false">https://medium.com/p/89968e45d562</guid>
            <category><![CDATA[priming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[high-throughput]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[week-1]]></category>
            <dc:creator><![CDATA[Alex Pyankov]]></dc:creator>
            <pubDate>Tue, 20 Jul 2021 14:12:03 GMT</pubDate>
            <atom:updated>2022-06-10T23:40:12.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0cSmfE2fQz-8zFU5" /><figcaption>Photo by <a href="https://unsplash.com/@nhoizey?utm_source=medium&amp;utm_medium=referral">Nicolas Hoizey</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This post is to share some experience in my journey to the perfect (or ideal if you like) Scrum process for software development, highlighting hidden gems, and some pitfalls.</p><p>In software development we are constantly observing a couple of “unnatural” laws in a very vivid action with astonishing news headlines about another multigazillion dollar project delayed / cancelled / needs another gazillion, so the guilty are:</p><ol><li>Parkinson’s Law (<a href="https://en.wikipedia.org/wiki/Parkinson&#39;s_law">https://en.wikipedia.org/wiki/Parkinson&#39;s_law</a>), when work expands to occupy all the time given.</li><li>Hofstadter’s Law (<a href="https://en.wikipedia.org/wiki/Hofstadter&#39;s_law">https://en.wikipedia.org/wiki/Hofstadter&#39;s_law</a>), when this expanded work bloats further and overflows all meaningful boundaries (in other words, whatever you plan for… it will take more time, even if you add more time to your plan).</li></ol><p>Check out the articles, it’s somewhat enlightening.</p><p>Ok, we got laws, but is it possible to break them?<br>It’s not physics, so should be easier, right? Not quite... We need to deal with behavioural machine, and this machine is… you or me. Let’s break the brain.</p><p>But first of all, I want to thank all the participants in making my mind on how to fight aforementioned laws:</p><ol><li>Kudos to <a href="https://amzn.to/39bw7ue">Daniel Kahneman and his “Thinking Fast and Slow” book</a> for telling me about <strong>priming</strong>.</li><li>Kudos to <a href="https://amzn.to/3xeb8Pu">Alistair Cockburn’s “Agile Software Development” book</a> for telling me about <strong>agile</strong> methodologies and how to select a proper one.</li><li>Kudos to Jeff Sutherland for the <a href="https://amzn.to/3tswBmw"><strong>Scrum</strong> book</a> I listened to, entertaining and educational.</li><li>Some sort of kudos to my former employer for involuntary dragging me into this agile thing (I should have written “<strong>Obstacle</strong> Is The Way” before Holiday, damn!).</li><li>Kudos to Pivotal Labs for ensuring me that <strong>sprints of 1 week</strong> actually work (I was just watching how other people were doing stuff rather quickly).</li></ol><p>…And finally, my answer to the laws:<br><strong>make your sprint look like a sprint — short and superfast!<br></strong>While agile manifesto defines principles, scrum defines workflow, you must define the period — so make it 1 week, from Monday to Friday.</p><p>If you (my first and dearest reader) is looking for a recipe, here it goes:</p><ol><li>Monday (seed day): sprint planning (30 mins) in the morning</li><li>Tuesday: daily scrum (15 mins).</li><li>Wednesday: daily scrum (15 mins)</li><li>Thursday: daily scrum (15 mins), sprint refinement (1hr).</li><li>Friday (harvest day): daily scrum (15 mins), sprint review (1hr), sprint retro (30 mins).</li></ol><p>Total minimal meeting time during a week: 4 hrs.<br>(We are finishing at midday on Friday to leave afternoon for learning, exploration, black/white magic, alchemy, just switching off for the weekend earlier, etc)</p><h3>Benefits</h3><ul><li>Natural schedule (until society decides to change Grigorian calendar to some other emperor of the universe);</li><li>no weekend breaks inside the sprint after which you need to recollect your braincells on where have I left this stuff?..</li><li>short turnaround time makes people break user stories into a smaller increments that can be delivered within a week — it creates this great satisfying feeling of progress for the team;</li><li>priming effects of the timebox of 1 week makes the sprint more likely to be completed in full (keep Parkinson at bay, and get Hofstadter manageable);</li><li>probability to keep plans somewhat stable for a week is much higher than for two week, which raises team’s morale by decreasing amount of unplanned work;</li><li>according to a very nice book called <a href="https://amzn.to/3xFBbQV">“The Goal” by Eliyahu Goldratt</a>, and thanks to the DevOps movement, smaller batch size is one of the keys to higher throughput of the system (system == development team);</li><li>more focussed work (need to get the shit done by this Friday, not next Friday, or Friday after next Friday, or even further);</li><li>less mental wondering on what to do next, can I switch to that user story and back — what you see is all there is, and for the short sprint your Kanban board looks neater and smaller;</li><li>more accurate velocity of the team (there’re no long-lasting items with low accuracy of estimations in the short sprints);</li><li>faster retro actions (people remember more things at retro time for the last week than for the last 2–3 weeks).</li></ul><h3>Downsides</h3><ul><li>More pressure on the product owner / team leads / project managers / etc, because they finally need to get the backlog in a good shape at least once a week (no slacking allowed);</li><li>it might be challenging to break user story into small sub-stories, which can be a bit technical and not delivering user value by themselves, but they bring the state of the system closer to desired — this is actually crucial thing about small sprints — increments might not deliver business value, but they move the state of the system closer to this goal with fairly predictable rate (here goes happy project manager!);</li><li>might not work for large teams (&gt;9 people) due to the higher communication tax (all the meetings are longer, and we aim for 10–15% of the workweek to be spend on “compulsory” meetings).</li></ul><h3>Conclusion</h3><p>If you’re struggling with the performance of the team, and your team is not large one, try the sprints of 1 week, deploy on Friday, and break the “laws”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89968e45d562" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>