<?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 Vadim Davidov on Medium]]></title>
        <description><![CDATA[Stories by Vadim Davidov on Medium]]></description>
        <link>https://medium.com/@vadimdavidov?source=rss-1c0a66fa975a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JnfJrIfKSOKGaTLf.</url>
            <title>Stories by Vadim Davidov on Medium</title>
            <link>https://medium.com/@vadimdavidov?source=rss-1c0a66fa975a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 14 Nov 2026 07:29:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vadimdavidov/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[[Agile Risk Management]::]]></title>
            <link>https://medium.com/@vadimdavidov/agile-risk-management-8b6200a63a1c?source=rss-1c0a66fa975a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b6200a63a1c</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile-stories]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Vadim Davidov]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 09:35:09 GMT</pubDate>
            <atom:updated>2017-12-06T09:37:02.238Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*_h7qZUfhzn_87OT76CQRiw.jpeg" /></figure><p>A Risk is an uncertain event or condition that, if it occurs, has an effect on at least one objective.</p><p>There are four steps to conduct risks in Agile environment::<br>(1)<strong> Identify <br></strong>(2)<strong> Assess<br></strong>(3)<strong> Response<br></strong>(4)<strong> Review</strong></p><p><strong>IDENTIFY::</strong><br>Risk identification is an iterative process to create a register of risks. All Scrum events: Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective allow identifying supposed risks.</p><p>One of useful technique is <em>Strengths, Weaknesses, Opportunities, and Threats </em>(<a href="https://en.wikipedia.org/wiki/SWOT_analysis">SWOT</a>) analysis in order to identify risks</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*a9C8SkIjo_ZmvLtxyCL1Ow.png" /><figcaption>SWOT</figcaption></figure><p><strong>ASSESS::</strong><br>Once risks have been identified, they should be evaluated and prioritized. One of the most useful ways of prioritizing risks is using an impact vs. likelihood matrix.</p><p>An impact vs. likelihood matrix is a two-dimensional<br>representation of the amount of impact a risk has on the<br>project and how likely that impact is to happen. With this<br>knowledge, risks can be prioritized, and the team will know what<br>to focus on preventing, and what to monitor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*P5oW_jxIi3VbkL_beaer4g.jpeg" /><figcaption>Impact vs. Likelihood Matrix</figcaption></figure><p><strong>RESPONSE::</strong><br>After a register of risks has been created and assigned statuses according to Impact vs. Likelihood Matrix (low, medium, high) a team is informed of the potential magnitude of risks. Based on the status of the risk, the following actions are recommended:</p><ul><li><strong>Mitigate</strong>:: pre-event actions to reduce the likelihood or impact of a risk</li><li><strong>Avoid</strong>:: eliminate the risk by choosing an alternative approach</li><li><strong>Transfer</strong>:: risks are transferred to another area</li><li><strong>Accept</strong>:: no action taken</li></ul><p><em>High risks</em> need to be mitigated as soon as possible if risks are <em>medium</em> the team can decide it should be avoided or transferred, and <em>low risks</em> could be accepted without taking any actions.</p><p><strong>REVIEW::</strong><br>The risk register is reevaluated at every Scrum event (Sprint Planning, Daily Scrums, Sprint Review). During the review, the probability and impact of the risks are re-assessed for better and likewise, new risks are identified.</p><p>Risk is a good opportunity to improve your processes and product!</p><p>Be Agile!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b6200a63a1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>