The latest articles on DEV Community by Nikita Puzankov (@humb1t). https://dev.to/humb1t https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F147642%2Fd77b8dad-507a-4685-b192-1a3522766f5d.jpeg https://dev.to/humb1t en Nikita Puzankov Fri, 22 Mar 2019 12:53:17 +0000 https://dev.to/humb1t/planning-and-priorities-2k4f https://dev.to/humb1t/planning-and-priorities-2k4f <p>In the enterprise world, there are more tasks to be done than tasks which could be done in a timely manner. So to choose which of them we can complete and what features we can deliver we should have plan and priorities.</p> <h2> Quality Attributes </h2> <p>The idea for this post came to me when I was watching <a href="https://www.youtube.com/watch?v=x30DcBfCJRI">Introduction to Software Architecture</a> by George Fairbanks. He mentioned a good way to make math works for you when you need to work with quality attributes.</p> <h3> [H,M] </h3> <p>George suggested using three grades L, M, H (from low to high) and two properties - the first one is <em>Business Value</em> and <em>Implementation Complexity</em> as a second one. In result, any feature which you plan to implement and to deliver can be estimated as [H,M] or [M,H] etc. This remembers me another man with partially the same idea.</p> <h2> Risks </h2> <p>This was <a class="mentioned-user" href="https://dev.to/yegor256">@yegor256</a> and my <a href="https://www.yegor256.com/2015/08/04/nine-steps-start-software-project.html#risks">favourite article</a> on his blog where he described a method with two properties and ten grades to measure risks. It's one paragraph about that, please just read it.</p> <h2> --Divide-- Measure and Conquer </h2> <p>So I will try to generalize this approach and map it into enterprise routine of planning and issues prioritization.</p> <p>George's formula can be transformed into V * C where V is a business value or "priority" from a customer perspective, C is system complexity or implementation complexity which can be examined from Jira issue for example. You have priorities (Blocker, Critical, etc.) and this is <em>V</em>, you also have estimations and this is <em>C</em>. Multiplying, sum or another function between them will provide a measure by which you can sort your Service Requests and understand which of them should go first and you can make a plan with due dates and this is very important thing to the customer.</p> <p>In combination with Yegor's combination of probability multiplied by impact, you can also plan and prioritize risks mitigation.</p> <p>It was a map part, now just reduce and you will have a sorted set of incoming tasks which could be spread across your team to solve.</p> <p>Thanks for reading - keep calm and develop software!</p> planning dev software enterprise Nikita Puzankov Thu, 21 Mar 2019 05:17:55 +0000 https://dev.to/humb1t/hello-world-4444 https://dev.to/humb1t/hello-world-4444 <h2> Hello World! </h2> <p>It's my first blog post on <a href="dev.to">dev.to</a></p> helloworld