<?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 Max Bondorovsky on Medium]]></title>
        <description><![CDATA[Stories by Max Bondorovsky on Medium]]></description>
        <link>https://medium.com/@maxbondorovsky?source=rss-4f419a46b4f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Max Bondorovsky on Medium</title>
            <link>https://medium.com/@maxbondorovsky?source=rss-4f419a46b4f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:44:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@maxbondorovsky/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[Would you build a house like this?]]></title>
            <link>https://medium.com/@maxbondorovsky/would-you-build-a-house-like-this-50c8413e1f18?source=rss-4f419a46b4f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/50c8413e1f18</guid>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Max Bondorovsky]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 05:05:20 GMT</pubDate>
            <atom:updated>2020-01-07T05:05:20.456Z</atom:updated>
            <content:encoded><![CDATA[<p>“It’s tangible, it’s solid, it’s beautiful. It’s artistic, from my standpoint, and I just love real estate” For me, the key word in that quote is ‘tangible’, when people can physically see and touch, it crystallises the conceptual into real. Unfortunately, delivering code/software/application does not always provides that moment of crystallisation until the end and for the ‘dreamers’ it gives them the notation that anything can change until that moment. Mix that mentality with ‘Agile’ and you have a perfect recipe of future state not properly being defined and an ever changing scope and boundaries.</p><p>Agile is all about the changing landscape, however, when you are working on a project it needs to be closely coupled with a delivery view — can we actually deliver what we are saying within our constraints? The truth is, there will always be constraints on time and cost and the more things change the higher the risk of not delivering on time and on budget — this risk exponentially increases the further into the project you are. This is reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*3DVmjNT0azcoCGIFOsO_eg.jpeg" /></figure><p>While not all aspects of the design and solution need to be known up front, the direction, the goal and the foundations should be known, simply put, boundaries must be in place for successful delivery. Without boundaries the project can meander, resulting in non-delivery and cash burn. Ask yourself, if this was your own money, would you start paying someone to do something without knowing yourself what you want? (I am not referring here to exploratory, PoC, discovery or any other type of similar exercises)</p><p>If we draw a parallel to construction you would never start building a house without the proper design and end goal being defined. Most people realise that there are challenges and costs associated with changing design or components once they are ‘build complete’ and similarly they realise that they got time to change items that will only be done at a later stage e.g. flooring and fit out.</p><p>Just image if we approached construction the same way as we sometimes approach software — “just start pouring the slab and in the meantime I’ll figure out what the floor plan is” or “Don’t worry about the drainage design, we can always change that later” or my personal favourite “Just start building otherwise we will not finish on time”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/268/1*mP_SnZUF4uJvHwVx3uf2HA.jpeg" /></figure><p>As the delivery community it is our responsibility to educate stakeholders about the most efficient way to deliver value — which often means resisting the urge to start ‘build’ until the prerequisites for that build are done — requirements and design.</p><p>“I know my floorplan, so we can now put up the frame “not “start putting up the frame but I don’t know how it will look like at the end”. We all know which one will be more expensive at the end.</p><p>A quick search on the internet shows the basic home building steps are (source: <a href="https://bit.ly/2T12zFc):">https://bit.ly/2T12zFc):</a></p><ol><li>Prepare construction site and pour foundation</li><li>Construct rough framing</li><li>Complete rough plumbing, electrical and HVAC</li><li>Install insulation</li><li>Complete drywall and interior textures; start exterior finishes</li><li>Finish interior trim; install exterior driveways and walkways</li><li>Install hard-surface flooring and countertops, and complete exterior grading</li><li>Finish mechanical trims; install bathroom fixtures</li><li>Install mirrors, shower doors and finish flooring, and finish exterior landscaping</li></ol><p>Take these steps and compare them to any delivery project and similarities are obvious</p><p>This is how, I believe, we should be treating delivery — this approach also perfectly gels with agile and gives the customers flexibility to change items as we progress through the lifecycle and at the same time allowing clear prioritisation for delivery.</p><p>P.S. The quote at the start is from Donald Trump — unfortunately it was the best ‘tangible building’ quote that I could find.</p><h3>Published By</h3><h3>Max Bondorovsky</h3><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/would-you-build-house-like-max-bondorovsky"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50c8413e1f18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Context switching on projects]]></title>
            <link>https://medium.com/@maxbondorovsky/context-switching-on-projects-ab888992eb47?source=rss-4f419a46b4f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab888992eb47</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[multitasking]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[time-management]]></category>
            <dc:creator><![CDATA[Max Bondorovsky]]></dc:creator>
            <pubDate>Mon, 17 Apr 2017 10:00:19 GMT</pubDate>
            <atom:updated>2017-04-17T10:00:19.348Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me start off with a scenario — It’s Tuesday morning and you are sitting at your desk doing the task that you were working on since yesterday, you estimated it to be a 4 day task and it’s needed for a code deployment on Friday. In galaxy far far away (or that’s how it seems to you) a bunch of project managers &amp; test managers are sitting in a room in what appears to be a crisis session. Next thing you know, the meeting door flies open, the crisis session has concluded and you can see one of the project managers walking directly towards you — ‘here we go’ you think to yourself in a sarcastic tone. The PM explains that UAT has just commenced and users are unable to login into the system to start executing, the PM nicely asks you to urgently look and fix the blocking defect/issue — this is now the number one priority. You reply back saying that this is counterproductive and its context switching and that the 4 day task will now take 5 day to complete.</p><p>Now, let’s examine the above scenario, a scenario that I am sure we have all been in on both sides. Did the PM ask the person to context switch? Yes. Does context switching cause loss of productivity? Yes, up to 40% according to some articles. Was it a correct decision to request the change in priority/task? Yes, absolutely yes.</p><p>The new priority impacts UAT and is business facing, it is driving the critical path of the go-live date and the 1 day hit to the original task can be absorbed and still meet the code deployment date.</p><p>Lets dig a little bit deeper with our scenario and apply the real world lens to it. Projects, especially towards the pointy end, are fluid from a day to day aspect. What the top priority was on Monday morning might be trumped by something else throughout the day. Its just the way it is — all the best planning in the world need to acknowledge and cater for the ‘unknown’ — the only thing constant is change. When these unknowns are encountered a priority decision must be made against the current task list and sometimes its decided that it gets to go on the top of the list and other times to the bottom. These decisions are made by assessing the pros and cons, however, they are (relatively speaking) made on the fly.</p><p>Throughout your whole professional career you get taught about improving productivity, continuous improvement and reducing waste and you get drilled that context switching is one of the biggest killers of productivity. Context switching is something you do all day at work (and at home) and it varies from checking your email during a work task to stopping cooking because your baby is crying. It’s a known fact that your productivity suffers when you context switch but it is a fact of life. We don’t live in a perfectly linear world. The aim should be to reduce the context switching, not eliminate it. If you attempt to eliminate context switching, you might as well get on your unicorn and go home.</p><p>I read a great article by Larry Kim titled <a href="https://medium.com/the-mission/multitasking-is-killing-your-brain-79104e62e930">‘Multitasking is Killing Your Brain’</a> and he makes valid points and I want to differentiate what I am talking about here V’s Larry’s article. In my scenario the request is not for 2 tasks to be done in parallel, it is to pause the work on one, complete the new task and resume the original task. Lets entertain the idea of what would happen if in the scenario we allowed the person to complete the task he was working on. Firstly, UAT gets delayed by 3 days until the task concludes on Thursday and then we fix the blocking defect resulting in UAT and Go-live having a 3 day impact and the implications of that are self explanatory. This decision is a no brainer.</p><p>The scenario used, to a certain degree, is a simplification of the real world with exaggerated consequences but I have encountered these types of situation countless times. I am not advocating that we should all be context switching all the time and in actual fact, I would argue that a person should have no more than 2–3 tasks in flight at any given time however the reality of projects is that, sometimes, items come up that just take priority. We must embrace this fluidity and deal with it with an open mind, sure you might take a productivity hit to your task but sometimes that task is just not top priority anymore.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab888992eb47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Vs Waterfall. Methodology arguments must stop.]]></title>
            <link>https://medium.com/@maxbondorovsky/agile-vs-waterfall-methodology-arguments-must-stop-69ef0f6cd0df?source=rss-4f419a46b4f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/69ef0f6cd0df</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Max Bondorovsky]]></dc:creator>
            <pubDate>Mon, 17 Apr 2017 03:31:43 GMT</pubDate>
            <atom:updated>2017-04-17T03:31:43.950Z</atom:updated>
            <content:encoded><![CDATA[<p>Agile….waterfall….agile….waterfall……I am sick of hearing these methodology arguments, it almost feels like a civil war. In the last decade I have seen a radical shift of how organisations are approaching software delivery and it’s all for the better. Organisations and delivery need to continuously evolve to deal with the ever changing landscape and rapidly adjust to it. We have all seen what happens to organisations that don’t make these adjustments — Kodak, Nokia, Blackberry and the list goes on.</p><p>I do believe that the days of implementing a system that will be around for decades is no longer true, the world is changing too fast — we need to continuously improve and evolve with the market and the industry. What is even more apparent is that that organisations need to not only evolve with the industry that they play in but also with other industries. The lines between industries are getting blurrier. So how have most large organisations thought they would do that and become ‘nimble’? Doing agile, of course!</p><p>Agile — one of the most over used and misunderstood terms in IT. We use Post-It notes and put them on a whiteboard. We are Agile. We don’t do specs anymore because we do agile. We do stand ups. We are agile. I can’t tell you how long the build will take. We do agile. We do stand-ups (they are 30 minutes and we sit down). We are agile. We use Jira. We are agile.</p><p>I am sure many people can relate.</p><p>True story: I was in a meeting earlier in the week and we were asking if a project has done any technical design specifications for the solution that has recently been implemented and the answer was “No, we were doing that phase in agile, so we didn’t do any specs”</p><p>What a bunch of rubbish!</p><p>Firstly, let me start of by giving you my position, and it’s a simple position:</p><p>1) You can have truly successful projects using agile or waterfall and you can have failure projects using agile or waterfall. Pick the one that suits the project best and incorporate the best practices of both.</p><p>2) In a majority of large organisation it’s impossible to run pure agile or pure waterfall (at least for now) — there are just too many external factors — vendors, siloed delivery between various teams, reliance on teams using the other methodology and overly complicated compliance and legal processes. And before anyone attacks me, I know that you can get them involved in the team etc etc. But I have rarely seen that work.</p><p>3) Pragmatism over purism.</p><p>4) I prefer agile but the proper agile.</p><p>Secondly, why is it always about the methodology?! It’s more to do with the people, the culture and the attitude. Lack of specs cannot be blamed on the chosen methodology — its just poor form and laziness. The beauty of Scrum and other agile practices is that it made people question the value of certain documents, as the manifesto states — working software over comprehensive documentation. This does not mean software over any documentation.</p><p>Thirdly, each methodology has its benefits and what agile brought was a change in the attitude towards software delivery. It made the business (product owners) realise that they are ultimately accountable for the benefits of the delivery. It allowed them to be involved in the process from start to finish. It empowered them with decision making all through the lifecycle. It also allowed the ‘builders’ to have access to the stakeholders and truly understand why they are building it and the value that the end product adds to the organisation. This brings me to my final point.</p><p>I have touched on this briefly, success of delivery is all about the people and the drive towards the common goal. It’s a team sport that needs commitment and dedication from all players. We, as IT professionals, need always remember that we are building software for a user. Whether its internal or external, the goal is to meet their objections, add value and deliver the best outcome possible. We need to remember that perfection does not exist — we need to build and iterate. We need to embrace change and acknowledge that product owners will change their mind and we need to accept that, at the same time as making it transparent to them the impact of the change. Software delivery is all about collaboration.</p><p>We need to end these methodology arguments and take the best from all theories and move forward. Blaming methodology for not doing ‘the right thing’ or skipping key steps is just excuses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69ef0f6cd0df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>