<?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 Myron Kokhanovskyi on Medium]]></title>
        <description><![CDATA[Stories by Myron Kokhanovskyi on Medium]]></description>
        <link>https://medium.com/@myronkokhanovskyi?source=rss-e706a5e4c98b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*t2K6b6DBp9QitgJ02M1z8g.jpeg</url>
            <title>Stories by Myron Kokhanovskyi on Medium</title>
            <link>https://medium.com/@myronkokhanovskyi?source=rss-e706a5e4c98b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:51:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@myronkokhanovskyi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Agile Mindset (part 2).]]></title>
            <link>https://medium.com/@myronkokhanovskyi/the-agile-mindset-part-2-e3706c9a3751?source=rss-e706a5e4c98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3706c9a3751</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Myron Kokhanovskyi]]></dc:creator>
            <pubDate>Mon, 16 Apr 2018 06:01:01 GMT</pubDate>
            <atom:updated>2018-04-16T06:01:01.216Z</atom:updated>
            <content:encoded><![CDATA[<p>In the previous post,<a href="https://medium.com/@myronkokhanovskyi/the-agile-mindset-part-1-9f9905b290cc"> The Agile Mindset (part 1)</a>, I’ve started to share my vision of Agile Mindset. In this post, I’ll continue with a few more aspects, that in my opinion, define this term as well as touch upon some practical examples of an Agile-minded organization.</p><h3>Failing fast, Failing better.</h3><p>In traditional software development methodologies failing is considered as a bad and embarrassing thing to admit.</p><p>One of the main disadvantages of traditional Waterfall approach to software development is the fact that you only fail once, and that is at the end of the project. When I talk about failing, I’m talking about failing to deliver value, not failing to hit the deadline.</p><p>Fail Fast Succeed Sooner philosophy is based on iterative approach, where you work for some time, and then check if you are actually delivering something valuable.</p><p>And if it turns out that you have <em>failed</em> to deliver something valuable, it means that you already found out that you failed and probably have the information/knowledge on what needs to change in order to deliver something valuable next time. The<em> faster</em> you find out the cause of your failure, the sooner you can make a change and <em>succeed.</em></p><p>I think that this concept is pretty popular and is being understood and adopted by companies without too much of a pushback, so I won’t spend much time on this.</p><p>But, I think it is important to mention that it should be spread across your organization and incorporated it in the culture. As a Project Manager, this is definitely something that you should be doing to help the organization become more mature within the Agile Mindset.</p><h3>Value-based priorities &amp; goals.</h3><p>A great way to distinguish an Agile Team from a non Agile Team, is to take a look at their goals and prioritization process.</p><p>Most Teams attempting to be Agile, will follow best practices like setting a Sprint Goal, and delegating Backlog Prioritization to a Product Owner or Product Manager. While that is all great, not always a Team can set a Sprint Goal that actually matters, and not always PM can prioritize the backlog according to the best value/risk/cost ratio by himself.</p><p>Here are a few guidelines to follow when setting goals and priorities.</p><h4>Defining value should be a collective effort.</h4><p>While PM usually has good information on how valuable is a Feature to a customer and has an idea on what benefits we might achieve is we build it, he definitely needs to understand <strong>the cost </strong>of work and <strong>the risk </strong>of it in order to make a decision.</p><p>Dev Team should be able to help by estimating the feature, doing some high-level planning and discovering main risks or displaying the amount of uncertainty of their estimates.</p><p>What’s even more important though, is that the Team needs to have a clear understanding of what are the underlying reasons for us to want to build this feature, and what kind of value are we expecting.</p><p>Knowing this should prompt the Team to think about <strong>other ways of achieving the expected results</strong>, <strong>challenging the assumptions of PM </strong>and ultimately <strong>help define the proper value of the particular feature in regards to other items in the backlog.</strong></p><h4>Not only Features have value.</h4><p>Here i want to touch briefly on things like Technical Debt, Refactoring and all those extra tasks which PMs usually respond “we’ll do them later, when we will have time”.</p><p>Well, we all know how it goes from there. After a few months of the Product being used by the customers, something horrible happens. Dev Team is being attacked with accusations. And then it turns out that none of it would happen if we would do that refactoring. We note this during the retrospective and get everybody’s agreement to include time for refactoring during each sprint. And you’re lucky if that stands for at least 1 future sprint :)</p><p>That is again something that should be brought up very early in product development and managed accordingly. We usually work with limited resources but situations like this are manageable with the right approach and negotiation tactic. :)</p><blockquote><em>P.S.</em> <em>Things like POC can also have lots of value. By doing them, you will decrease uncertainty and gain knowledge that you didn’t have before, which should help you assess the value a bit better. Try to do those as early as possible. Use POCs for High-Value, High Risk/Uncertainty items on your backlog, to try decreasing the risk.</em></blockquote><h4>Setting Goals.</h4><p>Goals are great. If you do them right, they will help tremendously. I usually advise the Team that I work with, to set the goals in different areas that are related to Performance.</p><p><strong>Team’s Performance Goals.</strong></p><p>Team’s performance is usually being assessed on the amount of work they can do, and it’s quality. But there are also things like predictability, the accuracy of estimations, ability to find the best possible solution for a given problem, help PO with decisions that will ensure the best value will be delivered, and ability to make decisions on their own, and much much more.</p><p>We are now starting to see more and more Dev Teams becoming Product Teams, and I personally think this is the way to go. A Product Team has to share responsibility with Product Owner on achieving Product Goals (Adoption, Revenue, CSAT, etc.). And therefore a Team’s performance can no longer be judged on how much work can they do during a Sprint, and amount of bugs they’ve introduced with the release.</p><p>Think about Setting Team Goals related to the following aspects:</p><ol><li><strong>Achieving a Sprint Goal.</strong></li><li><strong>Planned vs Actual Work Done ratio.</strong></li><li><strong>Achieving Product/Project Related Goals.</strong></li><li><strong>Quality Related Goals.</strong></li></ol><p>I surely recommend trying out OKRs as a way of Team Goal Setting, even if OKRs are not implemented in your Organization at scale yet. Implementing them in your Team can be a good Test Project to see showcase the benefits to the Leadership and potentially implement it company-wide.</p><p>And of course, you should use Metrics to help you achieve those goals. I’ll be digging into Metrics in my future posts. For now, i’d suggest taking a look at <strong>Velocity &amp; Cycle Time </strong>as I consider them to be the most essential for Teams to keep track of.</p><h3>Ownership &amp; Self Organization.</h3><p>This brings me to the last, as I see it, core aspect of Agile Mindset, which is Ownership &amp; Self Organization.</p><p>I think the best way to explain how i see those terms in practice, is to describe a Team that doesn’t have these values in their Mindset. We’ll call them “The Opposite Team” for convenience. Let’s take a look at 5 statements that would describe them</p><ol><li><em>The Opposite Team, does what they are told to do. Nothing more, nothing less.</em></li></ol><p><em>2. The Opposite Team needs managers to take responsibility and puts blame on other people/teams when something bad happens.</em></p><p><em>3. The Opposite Team doesn’t care if product or project succeeds.</em></p><p><em>4. The Opposite Team has lots of excuses.</em></p><p><em>5. The Opposite Team complains a lot but doesn’t propose anything to make the situation better.</em></p><p>It will be very hard to succeed with such a Team. Therefore, as a PM it’s our role to support and help the Team with adopting and practicing these values.</p><h3>In Conclusion.</h3><p>To sum up, let’s recap the components that, in my opinion, form <strong>Agile Mindset:</strong></p><ol><li><strong>Account for Uncertainty.</strong></li><li><strong>Get comfortable with Change.</strong></li><li><strong>Fail Fast, and Fail Better.</strong></li><li><strong>Set Value Based Priorities &amp; Goals.</strong></li><li><strong>Self Organize &amp; Take Ownership.</strong></li></ol><p>Agile is hard to practice, there will surely be a lot of impediments on the way of making your organization or Team truly Agile and yes it will take time. But if you are sure that Agile is the way to go — you should go all the way.</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3706c9a3751" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Agile Mindset (part 1).]]></title>
            <link>https://medium.com/@myronkokhanovskyi/the-agile-mindset-part-1-9f9905b290cc?source=rss-e706a5e4c98b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f9905b290cc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Myron Kokhanovskyi]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 06:19:17 GMT</pubDate>
            <atom:updated>2018-02-28T15:44:43.046Z</atom:updated>
            <content:encoded><![CDATA[<p>For quite some time, the idea of starting a Project Management blog has been in my head. Finally, I decided to give it a try and see where this goes.</p><p>After more than 5 years managing projects in IT, there are plenty of things that I’d like to share. In general, I consider experience sharing a great way to learn, so most of the things you’ll see here will be related to real work situations that I’ve experienced during my career. Let’s go right in.</p><h3>Agile Approach</h3><p>If you work in software development, you may have already formed your understanding of what Agile is. But, different people interpret the concept of Agile differently. I am a big fan of Agile. After managing a few of my first projects using a “traditional” approach, I thought that there should be a much better way to do this. I’ve been learning and practicing Agile approach ever since.</p><p>For me, Agile is a mindset, which drives you towards making particular decisions, and doing things in a particular way that leads to success.</p><blockquote>In order for Agile to work though, you have to make sure that this “mindset” is being shared across all involved parties.</blockquote><blockquote>You have to make sure, that everyone is on board with what it brings to the table and understands the consequences of “being Agile”.</blockquote><p>As a Project Manager, your primary established role is to ensure that a project you are managing, is being delivered according to expectations (time, budget, quality, requirements etc.) of your “client”. The problem with all this is that usually, those “expectations” are basically being considered as constant variables with a very little room for change (at least in “software house” kind of environment). And that’s where things get interesting, because <strong>most clients/stakeholders, want to limit “agility” of those variables mentioned above, while keeping their options to make changes.</strong></p><p>It depends on whether you work in a Product Company or a Software House, but at some point, you are being asked to provide Estimates/Timelines/Roadmaps. You work with the Team and put together some numbers. In most cases, no matter how you articulate that the estimate is still an estimate and nothing more, those numbers will become the final game. And then the whole success of a project as well as you as a Project Manager is being defined by how close to actual numbers you get at the end. It’s the mindset which has been around for ages and it’s not very Agile.</p><p>So how are you supposed to change all those people’s mindset to Agile? It’s good to start with explaining a few things that lie in a core of what Agile tries to solve. Depending on your case, you’ll have to talk a lot and educate people. It will be hard work to get them to switch to the Agile mindset, but it’ll pay off.</p><h4>Software Development is filled with uncertainty.</h4><p>And the only way to decrease the amount of uncertainty, is to actually spend time and resources on activities dedicated specifically to that — decreasing uncertainty. The paradox is, that doing that — might lead you to even more uncertainty. Here is an example.</p><blockquote>Lets say, the project you’re taking on right now with your Team, involves a task of a getting a list of GPS locations for a particular device. The requirements specify a 3rd party API that should be used to get that information.</blockquote><blockquote>During the planning session, it turns out — that the Team can’t really estimate it, because they do not know anything about that API. Trying to get even remotely accurate estimate — is worthless right now. So you say, OK. Go ahead and spend a few hours on research, try to get information that you need so we can estimate it tomorrow.</blockquote><blockquote>The next day you gather the Team back and try estimating it again. Well it turns out, that during the research, the Team found out that due to some restrictions, it will be impossible to integrate with that API. And now you are not only left with no estimation, but with a bigger problem, and more uncertainty.</blockquote><p>There are different kinds of uncertainty and there are also plenty of ways to deal with it. I’m planing to write a whole article dedicated just to that, in the short time future.</p><p>The important thing, is to have everyone around understand that in software development — we are rarely, if ever, 100% certain of what will it take to deliver.</p><h4>Getting comfortable with change.</h4><p>Change is inevitable. It will come in different shapes and forms. And thats OK… as long as it’s for the good of the project.</p><p>If we are talking about a change in requirements — the Team is usually the one that’s unhappy about those. In most cases, some of the work on the project has been done, and then out of nowhere, there is a change from the client that crosses most of that work out. But in other cases, it’s the Team that changes the estimates or states that, there will be additional work to be done.</p><blockquote>Agile tells us to <em>“respond to change”</em> rather than just to follow a plan. But why?</blockquote><p>Well, its all about doing what’s best for the product. Most projects are aimed at building some sort of a product for people that will be using it. And a sure enough way to fail is to create something that no-one will use. Sure, you can still succeed with the project in terms of delivering what you promised on time/budget/scope, but fail to deliver a valuable product.</p><p>The change, no matter who it comes from, is good, as long as this change “works for the product”. Here are some examples.</p><blockquote><strong>Good Change:</strong><br>After a few sprints, the Team delivered an MVP of an iOS application for simultaneous picture sharing to multiple social media accounts. The client conducted a few usability interviews with early adopters, gained great feedback and came back to the Team with a new set of requirements. This is great, as using this feedback a team can make the product better for the customers and have a higher chance of success. Even if implementing those changes will mean completely re-defining the existing logic of the app.</blockquote><blockquote><strong>Bad Change: </strong><br>After playing around with an MVP for few weeks, a Client has requested to also create a User Profile functionality for the picture sharing iOS app. He had created a mock-up with a fairly complicated structure. He hasn’t tested this with any potential customers yet but feels that this is needed. <br>In this case, the Team should try to push back, and have the Client provide some proof that this is what customers want and need. If that’s going to be the case, then the Team can also propose to automatically create User Profile from users social media account by implementing 3rd party API, and testing that with the users, rather than developing the whole functionality from scratch.</blockquote><p>In the end, it’s all about making something that people will want to use. So making changes to your existing work which will improve the chances of success for your product — is absolutely necessary.</p><p>Lets end this one here for now :) In the next post, i’ll continue to share my thoughts on this topic, and will focus on a few other aspects of the Agile Mindset.</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f9905b290cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>