<?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 illumisoft on Medium]]></title>
        <description><![CDATA[Stories by illumisoft on Medium]]></description>
        <link>https://medium.com/@illumisoft?source=rss-909cc6bafbe0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*o8rkRpefVUB_zRXdhVheEw.png</url>
            <title>Stories by illumisoft on Medium</title>
            <link>https://medium.com/@illumisoft?source=rss-909cc6bafbe0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:04:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@illumisoft/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[A strong MVP keeps your developer on task, on budget and on time]]></title>
            <link>https://medium.com/@illumisoft/a-strong-mvp-keeps-your-developer-on-task-on-budget-and-on-time-464903e7d6a1?source=rss-909cc6bafbe0------2</link>
            <guid isPermaLink="false">https://medium.com/p/464903e7d6a1</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[illumisoft]]></dc:creator>
            <pubDate>Thu, 17 May 2018 00:26:29 GMT</pubDate>
            <atom:updated>2018-05-17T00:26:29.685Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zcuhtWsmBy0ecQVI.jpg" /><figcaption>Keep your project on budget and on schedule by building a strong MVP.</figcaption></figure><p>Keep it simple and short. Ultimately, that’s what a minimally viable product does. It keeps your software development project on task, which is true no matter what your budget or schedule looks like. Your bottom line should center around creating that MVP.</p><p>Your developer is there to help you solidify that MVP idea. Whether you have a fixed budget or schedule, make sure you can paint a clear picture of your vision. That way, your developer can take your ideas and help you identify the highest valued thing they can work on.</p><p>When a prospective client first approaches us, they usually have this grandiose idea. It can be difficult to narrow down that idea into a minimally viable product. Don’t get us wrong; big ideas are great, especially for when you’re ready to scale up. But from the get-go, you should be able to scale down that idea. Be ready to figure out the smallest part you can sell and start making money right away.</p><p>Think about it this way: All businesses function kind of like a snowball. To grow your business, first figure out what’s the smallest snowball you can make. Then, start rolling right away so that your snowball can start accumulating.</p><p>The only way your developer can help you identify your MVP is if they stay in lockstep with you. This is especially true during the initial stages of your product. <a href="https://illumisoft.com/four-pillars-of-success/">That’s why solid, open communication with your developer is key to a successful project.</a></p><p>A clearly-defined MVP will help your developer stay within your budget. It also keeps everything on schedule. (For us, your budget and schedule are heavily intertwined because we charge hourly.) Understanding how critical your MVP is toward your bottom line will turn your idea into the truly valuable product you had imagined.</p><h3>Planning for contingency makes your bottom line a top priority</h3><p>We need to make sure we can deliver something valuable that you can make money with. Planning for contingency allows us to focus on that bottom line.</p><p>What if you started spending money before you identified your minimally viable product? Your project could end up hosed. <a href="https://qubit-labs.com/mvp-important-software-development-projects/">It’s risky because you never planned for things that might go wrong.</a> Understanding your project, budget and special features is a good start. Yet planning for contingency is also critical because something can always go wrong. That’s why a good developer will give you project cost estimates based on a wide range of scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g0uLMqZCVwvsC2D3.jpg" /><figcaption>If you don’t plan for contingency, what could go wrong?</figcaption></figure><p>Think of contingency in software development like building or fixing a house. When you renovate your home, you have to budget for contingency. Let’s say you want to redo the kitchen, the bathrooms and the bedrooms, and you also want to paint the walls. You need to figure out what things you absolutely need to have when renovating.</p><p>What happens if you decide to demolish the kitchen and find out that all the pipes busted? Now you’ve found 40 years of water damage that you need to fix. It sets you back right now, but you still have a fixed budget. What do you want to give up? Can you live with pink walls in the bedroom?</p><p>Planning for contingency allows you to adjust your vision, budget and/or schedule. <a href="https://illumisoft.com/new-bright-idea-steps-consider-start/">With that, you can focus on your new bright idea and your bottom line.</a> It’s about managing expectations for your project.</p><h3>A quick summary of our approach to project cost estimations</h3><p>If a hard and fast budget/schedule for your project is top priority for your business, we’ve got good news and bad news. The bad news is <a href="https://www.toptal.com/agile/software-costs-estimation-in-agile-project-management">many developers struggle with being able to give you a project cost estimation</a>. This is even more true for intrinsically or inherently complex projects. (Think building a rocket, for instance.)</p><p>The good news is some developers who did their math homework will be able to give you a reasonable ballpark number for your cost estimate. In our case, we use a three-point estimation technique. It includes a “most likely” cost, an “optimistic” cost and a “pessimistic” cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IH9pNty2HtUt2avt.jpg" /><figcaption>A 3-point estimation gives you a more complete picture of project costs.</figcaption></figure><p>Our three-point estimation technique is a modified version of the PERT method that was first developed in the 1950s by the U.S. Navy Seals. <a href="http://www.dtic.mil/dtic/tr/fulltext/u2/735902.pdf">PERT — or, Program Evaluation Research Task — was a methodology for evaluating objectives of the Fleet Ballistic Missile program.</a></p><h3>A 3-point cost estimation gives you the good, the bad and the most likely</h3><ol><li>We first learn your business needs and how you envision using your system.</li><li>Then, we break it down into all necessary subsystems and further break those down into individual tasks. Those tasks are necessary to implement the system.</li><li>We then estimate each task using three points of reference on the basis of complexity: Most likely, optimistic and pessimistic.</li></ol><p>We also use reference data from previous projects to translate complexity into an approximate number of hours. We then multiply the number of hours against our hourly rate. The result: an estimated most likely cost, optimistic cost and pessimistic cost.</p><p>Finally, we calculate the weighted mean of these three estimated costs to produce the total expected cost to the system. The final result gives you a project cost estimation on a bell curve of probability for the cost to fall within a given range.</p><p>Software development is inherently unique. So cost estimates are hyper-individualized and tailored for each client’s project.</p><h3>Finding curve balls in your project exposes risks and unknowns</h3><p>You might think your project cost estimate will look like a standard bell curve. That means you think the project is as likely to fall under cost as it is to run over cost. That’s not always the case in software development and, actually, in all engineering.</p><p>Suppose you ask your developer to execute a task. They may have an idea how much time and money it will cost to do that. Using our three-point estimation technique, we can estimate the complexity and determine that: In the best case scenario, this project will be really easy; most likely, it’ll be pretty easy; but… there might be something that throws off the whole project, in which case it’ll be really hard. In this case, you don’t have a standard bell curve anymore.</p><p>“So you get a curve that is individual to the entire project, and it’s almost never a standard bell curve,” said Dustin Ewan, vice president of software development at illumisoft.</p><p>Developers usually have a lot of certainty that a project cost will fall in the easy range, but there might be something that throws it off. If we do hit a couple of snags, it can go way, way beyond the budget we had anticipated. Or, even worse, <a href="https://illumisoft.com/software-puts-risk/">it could be catastrophic</a> to your business. <a href="https://www.farreachinc.com/blog/far-reach/2017/09/21/cone-of-uncertainty-in-software-development">That’s why part of our project cost estimation includes a cone of uncertainty.</a></p><p>At the start of the project, the “cone” is very wide because there are so many unknowns about the project. It’s difficult to claim that the project will cost X number of hours/dollars because of all the uncertainty.</p><p>Over time, the cone narrows as your developer goes through the project because they’re eliminating those unknowns. That means the “cone” will start to converge on expected costs for the project. And if somewhere in the middle, your developer hits a snag, then the cone starts to converge at a higher projected cost. We know then that the project will go over budget.</p><p>Estimating project costs takes a day or two to create.</p><h3>How all this ties into budget and schedule</h3><p>Even if you have a large budget, almost nobody plans for contingency.</p><p>Once you receive a project cost estimate, don’t be tempted to focus only on the most likely, or expected, cost. Sure, we estimated that the project will land within a certain range of costs. And we came back with a project cost estimate for both best and worst case scenarios. But try to avoid focusing only on that expected cost.</p><p>“You might say, ‘Oh, you can do it for this much money; I heard what I needed to hear,’ Ewan said. “And you might think at that point that we should just start building. But we really need to figure out where the value lies and what your minimally viable product is, because we have such a wide cone of uncertainty at the beginning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZAt3Zg1BP9UiFD4K.jpg" /><figcaption>Give your project room to breathe by identifying your MVP upfront.</figcaption></figure><p>“If something goes wrong, we need to make sure we can deliver something valuable to you, that you can actually turn around and make money with.”</p><p>By identifying upfront your minimally viable product, we can focus on delivering the highest valued part of your project. That way, if something goes wrong, we can still deliver something of value within your budget.</p><p><a href="https://illumisoft.com/hire-a-software-developer/">If you have a fixed budget, that means it’s even more critical to identify your minimally viable product.</a> If something goes wrong, you could end up one mistake away from going belly up on the project.</p><p>On the flip side, if you don’t have a fixed budget, the project has more wiggle room to pivot from your original idea.</p><p>Illumisoft utilizes time and materials contracts. To us, your budget and schedule are the same. Our total cost estimate is based on the number of hours it takes for one developer to complete your project.</p><h3>Time and materials contracts make your schedule more flexible</h3><p>That’s not to say your schedule is inflexible with time and materials. In fact, we can speed up your schedule somewhat by adding more developers to a project than we factored in the estimation.</p><p>While your schedule is relatively flexible with time and materials, your budget is rather fixed. In other words, we can’t lower costs by adding more developers to a project. In software development, this is the “mythical man month.” To speed up your timeline, it’s going to cost more. Why? Because communication overhead takes time (and money).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rP8xJgL6ZXHcz0Fb.jpg" /><figcaption>Time and materials contracts keep your developer aligned with your vision.</figcaption></figure><p>For example, the formula of adding one more developer to your project looks like this:</p><p>(2 x the amount of work) + communication overhead = total project cost for the period of time the developers worked</p><p>“So, the faster that you move on your project, the more it will cost because you’re paying in overhead,” Ewan said. “If you have a fixed schedule and you don’t have a fixed budget, it’s totally worth it.”</p><p>But, if your schedule and budget are both fixed, the only thing your developer can do is remove features. Again, this is why having a minimally viable product is critical. You can scale down the project to focus on delivering a product to sell right off the bat.</p><p>What if your project’s schedule is pretty loose, but you’re operating on a strict budget? In that case, we recommend hiring one developer who can fully commit 40 hours a week to your project.</p><p>“That’s really the optimization of using your budget wisely,” Ewan said.</p><p>If your developer fully commits to your project, then your developer avoids context switching. With more than one project on their plate, they start the day working on one project and end working on another. So, each time they switch tasks, they have to unload everything they were thinking about that other project and get back on track.</p><p>The problem? Now you’re paying for overhead for the developer to get himself back up to speed with what he was working on. The more you reduce the complexity, the less effort the developer must exert to reorient.</p><h3>Developing an MVP protects you from contingency</h3><p>Having a minimally viable product is critical, even when your budget and schedule are flexible. In fact, identifying and developing a minimally viable product naturally creates contingency around unknowns.</p><p>“A lot of people have such a naive view of the project,” Ewan said. “They think, ‘Nope, this is what I’m going to buy. This is how much money I have. They said this is how long it’s going to take.’”</p><p>That kind of strict attitude toward your project sets you and your developer up for failure.</p><p>“If we don’t set the stage for the possibility that there’s going to be something we don’t expect, then we have very dissatisfied customers,” Ewan said. “But, if we talk about these things and we get them to focus on what an MVP is — you know, what’s critical and what’s the nice-to-haves, then we can deliver value and certainty within their budget.”</p><p>Got a project in mind? Let’s set up an appointment and talk about what we can do for you.</p><figure><a href="https://illumisoft.com/"><img alt="" src="https://cdn-images-1.medium.com/max/548/0*HkF56YcIO7cKZCc2.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=464903e7d6a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Accountability: How developers should be good stewards of your time and money]]></title>
            <link>https://medium.com/@illumisoft/project-accountability-how-developers-should-be-good-stewards-of-your-time-and-money-a6750c84c4d3?source=rss-909cc6bafbe0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6750c84c4d3</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[accountability]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[illumisoft]]></dc:creator>
            <pubDate>Wed, 09 May 2018 21:51:06 GMT</pubDate>
            <atom:updated>2018-05-09T21:51:06.945Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gfePIwc1FdKcPdPz.jpg" /><figcaption>Your developer’s commitment to accountability will make or break the project.</figcaption></figure><p>Your vendor’s [lack of] accountability sets the stage for a successful software development project. Accountability requires open communication with your developer. It ensures an honest, realistic and goal-driven assessment of your project’s budget and schedule. That’s why <a href="https://illumisoft.com/four-pillars-of-success/">accountability is one of our four pillars to project success</a>.</p><p>Successful projects need two types of accountability: external and internal. External accountability involves good stewardship of your time and money. It also needs open communication from your developer on the status of your project. Internal accountability ensures your developer has created what you actually wanted. That means solid planning and application of that plan to their software architecture.</p><p>Hiring a developer who prioritizes accountability leaves you with a high-quality product. This guarantees timeliness and cost savings down the road.</p><h3>Weekly updates keep the relationship professional and on task</h3><p>Software developers should be transparent in their communication with you. Illumisoft fosters transparency by providing weekly updates on the status of your project.</p><p>Dustin Ewan, vice president of software development at illumisoft, created this concept at a previous company with another developer.</p><p>Their company had a client who invested hundreds of millions into new technologies. Unfortunately, the relationship lacked accountability. They struggled to find a way to give the client peace of mind. Getting the product right was even more critical because emotions were running high.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*coew-P4QRuadI8IV.jpg" /><figcaption>It’s difficult to communicate about the project when emotions are high.</figcaption></figure><p>“Once a company is in so deep with their vendor, it’s really hard to get out,” Ewan said. “If you have a relationship with a vendor who doesn’t hold themselves accountable, that relationship can turn sour, first of all. It can be painful; but not only that, you can just be stuck in a really bad situation.”</p><p>Ewan found that the only way to start bridging the gap was by providing weekly updates. Succinct, written communication had removed the emotion. It also allowed the client to focus on the state of the project.</p><p>The concept came from a bad experience, but the succinct format mended their relationship. And the best part for our clients? It helps prevent future relationships from going sour.</p><h3>Weekly updates list priority objectives and any known risks</h3><p>Our clients receive a super succinct weekly update from us. That update includes an executive summary of objectives we accomplished or made progress on.</p><p>The update also covers prioritized objectives for the coming week. That list is numbered so you can see what we’ve prioritized as the most important task. After reviewing the list, you’re also free to make adjustments yourself and tell us what you’d like us to focus on next.</p><p>Finally, the update includes any high or severe risks we’ve encountered. We only expose risks that are critical enough to raise to your attention when it’s 100 percent likely a high-consequence risk will occur</p><h3>Let us sweat the small stuff; we only expose high risks to you</h3><p>We identify, categorize and expose risks through a tool known as a Risk Matrix.</p><p>We categorize risks by severity of the consequences and likelihood the risk will occur. For example, if there is a 60 to 80 percent chance we will miss a hard deadline — and we’ve identified that missing the deadline is critical to project success — we will include it in the weekly update.</p><p>We only bring a risk to your attention if it crosses a high threshold. Examples include missing a deadline or exceeding the budget.</p><p>“There’s really no point in telling you every little thing that’s going on because then it’s just worrisome,” Ewan said.</p><p>You can also ask us to notify you of moderate risks, before they cross a high threshold. We will ask you about your risk appetite at the beginning of the project. That way, you’re exposed to whatever level of risk you need to feel comfortable.</p><p>When a high-consequence risk is 100 percent likely to occur, we will raise that flag and tell you immediately.</p><h3>Good software development lies in a firm foundation</h3><p>Your developer’s commitment to external accountability will be visible to you. Internal accountability, on the other hand, is more technical in nature.</p><p>“One thing a lot of people don’t really understand about programming is that there are infinite ways to accomplish a task,” Ewan said. “People imagine that: ‘Here’s where I am and here’s where I want to be, and there’s a straight line between them.’ It’s not like that at all in programming.”</p><p><a href="https://illumisoft.com/software-development-art-science/">Our founder, Dan Prince, likes to say that software development is art.</a> Think about it. Someone tells you to paint a picture of a woman; just imagine how many variations of that you could get. There’s all sorts of flourishment that you can do, and you could take it as deep or as shallow as you want.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WQ9EHISmeddzCTxR.jpg" /><figcaption>Having the right tools doesn’t matter if everybody uses different ones.</figcaption></figure><p>But what if you had to hand your painting off to somebody else and then they had to work on it after you? Other artists have their own styles and may use different tools, such as charcoal or pastels. If you made it hyper-personalized, there’s no way another artist could add to that painting without the adjustments sticking out.</p><h3>An architecture-first approach gets it right the first time</h3><p>Another even better analogy is building a house. Whenever you decide to build a house, you always prepare a blueprint of it first. Imagine trying to build a house without a blueprint and instead build it organically. If you didn’t plan ahead, there’s very little room to make adjustments to the house without having to start all over.</p><p>Software development works the same way. In fact, illumisoft utilizes an architecture-first approach to our clients’ projects.</p><p>“By taking a look at how we organize our code upfront, we leave ourselves lots of room to expand,” Ewan said. “And we can make changes easily during the project because we have a solid architecture.”</p><p><a href="https://blog.ndepend.com/introduction-clean-architecture/">First developed by Robert C. Martin (aka Uncle Bob),</a> the Clean Architecture concept creates straightforward processes for software development. This allows project managers to scale up quickly by bringing in extra developers. New team members can then immediately identify the architecture and start working.</p><p>Without well-defined architecture, a team of, say, five developers could end up disjointed. They unwittingly add necessary complexity to the project. The more they code unguided, the more difficult it will be to merge the code produced by each developer.</p><p>“At first, things are going along pretty well and it seems like you’re making a lot of progress. But because you have five different developers all writing the code in their own way — without a shared common architecture or understanding of the architecture — it becomes more and more complex each time someone contributes to the code,” Ewan said.</p><h3>Clean Architecture reduces overhead costs, saving you time and money</h3><p>Sloppy projects tend to happen with developers who work for cheap. At first, you might think you’re getting a bargain and that you did the right thing by hiring the developer for $30 an hour. At first they are flying, but everything is going to grind to a halt because the project will become increasingly complex. As the complexity of the project increases, the developers have to spend more and more of their time communicating about how the code works and less and less time actually working on the project. <a href="https://illumisoft.com/avoid-customer-support-expense-due-to-poor-software-development/">This increases your project’s overhead costs, all because your vendor didn’t establish architecture of the project beforehand.</a></p><p>“They might be cheap, but how much of that money is just getting thrown away and wasted on overhead because they’re not holding themselves accountable to the quality of the product that they’re producing?” Ewan said.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BZy0bvlPOb0d52n0.jpg" /><figcaption>Thinking about architecture upfront saves time and money.</figcaption></figure><p>It’s like the house analogy. If your developers don’t use the same tools and materials to build your house, you’ll still get a house. That house is going to look terrible and be unnecessarily expensive and dysfunctional. One guy might be working in brick, and another guy might be working in wood. When they meet up, they’ll have to figure out how they’re going to join the two materials together.</p><p>That’s why software architecture is vital to timely, cost-efficient project success. Vendors whose entire team understands the architecture can quickly and easily add developers. There’s no thought to how to organize the code; it’s already dictated in the architecture.</p><h3>Hire a developer who reduces — and doesn’t accumulate — technical debt</h3><p>Sorting through code that has not been well organized can also take a long time. One of our clients had a developer who worked for several years coding everything organically. We are still digging into his code and trying to figure out what he was thinking. There was no consistent thought process or organization from one idea to the next.</p><p>“There are so many traps and gotchas; it’s like the butterfly effect,” Ewan said. “Everything is so complex and interconnected that we don’t know where these butterfly effect type things are in the code. If we make a little change over here, it might have huge repercussions somewhere else because of how poorly or organically it was written.</p><p>“He wasn’t holding himself accountable to the code that he was writing.”</p><p>Our client is still paying off tons of technical debt because that developer lacked forethought. As a client, you often don’t know that you’re acquiring technical debt while it’s happening. But that’s exactly what happens when a vendor doesn’t hold themselves accountable. The vendor acquires technical debt for their client that the client will have to pay off later.</p><p>So, you can either pay to avoid the technical debt upfront — which is typically cheaper — by hiring a developer who considers software architecture from the beginning <em>and</em> holds themselves accountable to you through open communication… or you can pay off the technical debt later with who knows how much compound interest. Nobody knows how much time it will take to fix the project to make it more workable.</p><p>We recommend finding a vendor who understands the importance of avoiding technical debt.</p><h3>Accountability to your project gives you a high-quality product</h3><p>Accountability to you and your project all comes down to affect your bottom line.</p><p>But exactly what accountability looks like is often kind of difficult to describe. Of course, your developer must be a good steward of your time. Any time spent communicating about the project is time you have to pay for. You rely on your developer’s tech expertise. It all boils down to your vendor being a good steward of your money — whether you understand what they’re doing or not.</p><p>This is the part where you might feel leery or defensive of your developer. <a href="https://illumisoft.com/four-pillars-of-success/">That’s why developing trust in the relationship with your vendor is also vital to project success.</a> Weekly updates on your project are a great way to stay on the same page as your vendor. Your developer should communicate with you in ways that resonate with you. At the same time, your developer should focus on reducing project complexity. Simplicity reduces overhead time on problems that they should not need to discuss at all.</p><p>Ultimately, Clean Architecture offers a high-quality product that does what you wanted. It’s done in such a way that you can pass the project off to other developers as well.</p><p>Want to talk more about what accountability looks like for you? Let us know.</p><figure><a href="https://illumisoft.com/"><img alt="" src="https://cdn-images-1.medium.com/max/548/0*SOCGJ0ZHat-ACfu9.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6750c84c4d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Expectations Facilitates Successful Projects]]></title>
            <link>https://medium.com/@illumisoft/managing-expectations-facilitates-successful-projects-aa4a82bc21f7?source=rss-909cc6bafbe0------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa4a82bc21f7</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[expectations]]></category>
            <dc:creator><![CDATA[illumisoft]]></dc:creator>
            <pubDate>Wed, 02 May 2018 22:05:16 GMT</pubDate>
            <atom:updated>2018-05-02T22:05:16.405Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VDIrdP9s3ugz_3r3.jpg" /><figcaption>Managing expectations keeps everyone on the same page.</figcaption></figure><p>The best kind of project is the one you were expecting, right? One of the best things you can do to tackle a software development project is maintaining a positive, working relationship with your developer. Managing expectations helps both parties envision the same processes to achieve your goal.</p><p>As easy as that might sound, it doesn’t always go down that way. Your developer might produce exactly what you specified in the contract, but for one reason or another, it didn’t turn out the way you wanted. Perhaps your vision of the product pivoted, or you didn’t really know what you wanted in the first place. Either way, you end up dissatisfied because your developer didn’t deliver to your level of satisfaction.</p><p>Take one of our firsthand accounts as an example. When Dustin Ewan, a managing partner with illumisoft, was working in South Korea, his company decided to outsource part of a project to an overseas vendor to reduce costs on developing an online bookstore. They got the bookstore, but “it was just a trainwreck of code.”</p><p>“We couldn’t modify it without breaking anything,” Ewan said. “It wasn’t well put together. Just junk.”</p><p>Part of that lesson learned is simple: You get what you pay for. You might think you’re getting a bargain, but more expensive software will have higher quality. So whose fault is it? Yours because you don’t know the technology, or the developer’s because they failed to go above and beyond your expectations?</p><p>In Ewan’s case, the overseas company took advantage of the fact that his company didn’t explicitly define that they wanted the online bookstore to be maintainable and scalable. But on the other hand, his company also made the assumption that them being developers would hold themselves technically accountable to the product that they were making.</p><p>We recognize that technology is really, really complicated, so <a href="http://www.sourcefuse.com/setting-and-managing-expectations/">aligning your expectations of the project with your developer will keep things running smoothly</a>. In fact, a good developer will acknowledge that the main goal is to build a solid, mutually beneficial relationship with you. Here are some ways to do that.</p><h3>Good Planning from the Start Saves Time, Money and the Relationship With Your Vendor</h3><p>Any great project starts out with great communication. In moving forward with your project, share your ideas and concerns with your developer. If that groundwork doesn’t get laid, the project might not turn out how you expected, costing time and money. <a href="http://galorath.com/blog/software-project-failure-costs-billions-better-estimation-planning-can-help/">Survey research backs up the fact that good planning reduces the cost and length of any software development project.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*DLldOBfTCpYEA5OX.jpg" /><figcaption>Getting the work done is not enough. Success requires constant communication and realignment.</figcaption></figure><p>Besides losing time and money, you could end up having a soured relationship with your developer. Any relationship can get damaged by a failure to communicate. If you don’t have a plan fully lined out to your developer, that’s OK. Just let them know so they can help you flesh out your idea into something more substantive and practical.</p><p>You might feel vulnerable or make assumptions here at the beginning of your project. Don’t leave concerns unspoken during the planning phase — or, really, at any time throughout the project. Here are a few reasons why speaking up makes smooth sailing.</p><h3>Make plans, not assumptions</h3><p>It’s tempting to make an assumption about your project or your developer. You might be guarded or on the defense because you’ve been burned in the past by a project gone wrong. Or, this might be your first software project and you fear showing all your cards or letting on that you really don’t know anything about coding.</p><p>We recognize those pain points, but in order to align our expectations, we have to remove those [unspoken] barriers in order to hold ourselves accountable to you and develop the best product on time and on budget.</p><p>That being said, try to avoid making any assumptions about the project. After all, your developer will only be able to create a product based on what you’ve specified. Developers should nevertheless admit when they make mistakes or fail to communicate with you. And we do screw up; we’re human too.</p><p>Recently, we took for granted our communication with a client when his project kept receiving errors. He notified us right away about the first error, so we let him know we’d look into it. But after he kept receiving errors and sending them our way to notify us, we didn’t respond, thinking our initial address of the issue was enough.</p><p>Our expectations weren’t aligned with that client; we thought we were communicating everything we needed to communicate and, apparently, he did not. We continually strive to have an outstanding relationship with our clients, and we believe that communication is the key to that. And in this case, we definitely did not live up to our own standards.</p><p>It really boiled down to miscommunication, and that’s on us. Unfortunately, this can happen to you with any developer. The worst thing you can do at this point is wait until it gets to a boiling point. Don’t wait until you’re already frustrated. If you find yourself in a position where you have concerns or doubts, don’t let those remain unspoken.</p><h3>You don’t have to let your guard down, but tell us why it’s up</h3><p>Establishing a mutual expectation from the start is a key component to building a partnership with your developer. From our point of view, we can go a long way toward doing that. We can build our side of the bridge out quite far, but in order for us to completely bridge the gap, you’re going to have to meet us a little bit.</p><p>Be open and honest with your developer by saying, “Hey, this is where I’m at; I’ve never worked with a vendor before, so I have these concerns,” or, “Hey, I worked with a vendor before, and we had some rough patches here, so I’m a little guarded about this.”</p><p>If you let us know you have been burned in some way in the past, we can build extra padding around this rough corner so that things go a little bit more smoothly.</p><p>“We can build that bridge out so far, but you need to meet us,” Ewan said. “You don’t necessarily have to let your guard down, but you have to tell us where those those pain points are. If you don’t communicate to that to us, then it’s going to be really hard for us to move forward because you have a hidden resentment. You’re basically laying the mines for us to step on, and then when we step on one of those mines, you’re going to be like, ‘Aha, I knew it!’”</p><p>Without communication, your partnership will be founded on a false dichotomy that sets up you and your developer for failure. It’s the same thing if you go see your doctor about some health conditions that you’re having, but don’t tell them about your lifestyle, diet or habits. As a result, you could get misdiagnosed, and the doctor might treat your health issue in the wrong way because their assumptions about why you have this symptom could be wrong.</p><p>We believe constant, consistent and honest communication bridges that gap. If you’re afraid to communicate because you want to protect yourself and your business, or you expect the developer to take advantage of you because you don’t know coding, that’s a mental, emotional barrier to overcome.</p><h3>Aligning Expectations is an Ongoing Process that Makes Sure You Get What You Want in the End</h3><p>Developers and clients don’t always keep their expectations aligned throughout a project. Sometimes, it’s as simple as a lack of communication. Other times, the strict outlines of your contract inhibit you and/or the developer from pivoting in a different direction.</p><p>Whatever the cause, managing and aligning expectations during the project is vital to project success. It’s an ongoing process too. Your vision of the end product could change, firstly. And as your developer exposes you to new technological capabilities, you might gain a fresh perspective on the scope of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o6Djh4gy-6RFKJkh.jpg" /><figcaption>Developers should be exposing their thoughts on how technology could help expand your vision.</figcaption></figure><p>You and your developer should both communicate any changes that should be made mid-project. But sometimes, your contract serves as a barrier to aligning expectations. In that case, be wary of entering a contract that restricts your ability to pivot the project, especially if your vision isn’t clearly lined out to your developer.</p><h3>Why illumisoft avoids fixed bid contracts</h3><p>Just to be upfront, we tend to avoid fixed bid contracts.</p><p>If you’re stuck in a fixed bid contract, it’s incredibly difficult to pivot the project because you’re locked into whatever the contract dictates. As a result, the contract often becomes the relationship in custom software development projects.</p><p>For those who don’t know, here’s how a fixed bid contract generally works: A client tells a vendor what he wants built, and they write a contract around the project. The vendor then builds exactly what’s in the contract, and it might not turn out to be what the client needs. This is possibly a result of an unknown pivot in the project, or perhaps the client didn’t have the foresight he thought he did from the beginning.</p><p>We want to be really tightly integrated with our clients; in fact, we want to feel like we’re part of your team. The contract gets in the way of building a partnership because it creates a division between you and the vendor. And once you get locked into a fixed bid contract, everything you do gets channeled through it.</p><p>With a fixed bid contract, everything’s black and white, for better or for worse — and we would say 90 percent of the time for worse, just because you can’t account for everything. <a href="https://robots.thoughtbot.com/why-fixed-bids-are-bad-for-clients-too">In software development, your needs for the project may not be fully understood or fleshed out enough — one of many flaws of a fixed bid contract that hurt both you and the vendor.</a></p><p>What makes a relationship great is when a vendor goes above and beyond expectations, and there’s no incentive to do that if it’s not in the contract. When there’s a contract in place, you might have some sort of dispute with your developer, but if they haven’t violated the contract, they might say, “Sorry, man, you signed this contract; you owe me money.”</p><p>That’s why we predominantly work with time and materials contracts. It’s pay as you go, so if we’re not living up to your expectations, then you can cut us loose anytime. The risk for us, to be sure, is having no guaranteed income. But our bottom line is dependent on us delighting our customers, and we find that time and materials contracts tend to jive with our philosophy.</p><p>Time and materials contracts operate two weeks at a time; your developer will bill you every two weeks, and if you like what they’re doing, you pay the bill and the developer keeps going. If you don’t like what the developer is doing, you don’t pay and the developer halts work on the project.</p><h3>A time and materials contract keeps expectations aligned and on track</h3><p>When you enter a time and materials contract, it constantly keeps you in the driver’s seat of the project. It allows your developer to pivot rapidly and to scale up and scale down quickly and as needed.</p><p>Time and materials contracts are also much more agile than fixed bid. When you’re in a fixed bid contract and you want to make a change, you must put in a change request, which becomes a whole ‘nother contract on top of the original contract.</p><p>“I think the best part about it is it makes the relationship be the relationship,” Ewan said. “We have to constantly communicate and maintain this relationship. But on a fixed bid contract, now the relationship is the contract. ‘You’ve said what you needed; I said what I was gonna offer. You signed your name. I signed my name. Oh, there’s a dispute? Let’s consult the contract instead of consulting each other.’”</p><p>At the same time, time and materials contracts need continuous realignment of expectations. Therein lies the biggest risk of time and materials: Everything could go off course from the project the way you want it.</p><p>But we alleviate this problem through constant, consistent communication, always making sure that the project is aligned and that we’re breaking through any relationship barriers. <a href="https://illumisoft.com/four-pillars-of-success/">These are just a few of the benefits to consistent communication, one of our four key pillars to project success.</a></p><h3>Managing Expectations Removes Doubt and Builds Trust</h3><p>Unless you know technology, there is no way you could guide a developer by saying, “Hey, I need you to build this software in a way that’s maintainable and scalable, so I can hand it off to somebody else.” If you’re not technical, it’s impossible. At the end of the day, you couldn’t even look at the code and tell if it was well put together or not.</p><p><a href="https://illumisoft.com/hire-a-software-developer/">As a non-techy client, there’s a number of questions you need to ask upfront.</a> Their answers themselves aren’t so important; what’s important is if they can communicate it to you in a way that you can understand. Can your developer communicate on your level?</p><p>This is why it’s so important to build a relationship with your developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XJLYTNw8tR-udr2J.jpg" /><figcaption>If a developer can’t communicate on your level, then why is he even there at all?</figcaption></figure><p>We’re all about building relationships with you so that we understand where your technical ability is, and where your concerns and passions are, and then communicating on that level. Otherwise there’s going to be a disconnect.</p><p>As we mentioned earlier, we know we dropped the ball in communication with one of our clients, all because our expectations weren’t aligned. Even though we thought we had adequately communicated, he needed a little bit more from us, so he got really frustrated and, as a result, the relationship became a little bit strained after that.</p><p>After resolving that conflict and identifying his communication needs, we are now better able to understand what other clients may need so they feel more comfortable during the project.</p><p>Our main goal in managing expectations is to remove doubt, alleviate concerns and, ultimately, build trust with our clients. By maintaining a time and materials contract, we remain grounded in a relationship that lasts every two weeks, allowing us to pivot quickly and realign expectations as needed. And constantly communicating with you shines light on any problems, allowing us to figure out together on how to maneuver around them.</p><figure><a href="https://illumisoft.com/"><img alt="" src="https://cdn-images-1.medium.com/max/548/0*PyhHBpKi-PSslnvS.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa4a82bc21f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Four Pillars of Software Project Success]]></title>
            <link>https://medium.com/@illumisoft/the-four-pillars-of-software-project-success-31b81027475c?source=rss-909cc6bafbe0------2</link>
            <guid isPermaLink="false">https://medium.com/p/31b81027475c</guid>
            <category><![CDATA[accountability]]></category>
            <category><![CDATA[scheduling]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[budget]]></category>
            <dc:creator><![CDATA[illumisoft]]></dc:creator>
            <pubDate>Tue, 01 May 2018 21:29:10 GMT</pubDate>
            <atom:updated>2018-05-01T21:46:36.513Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x6y_g4dP-MTn-yzg.jpg" /><figcaption>The four pillars of software project success are all connected.</figcaption></figure><p>Before you pick your software developer for your next technical enterprise, first ask yourself, what is <em>your</em> idea of a successful project? What should your expectations be in looking for a good vendor?</p><p>Communication, accountability, budget, and schedule are the four pillars of project success for nearly every software developer. If one of those pillars is slacking, it can hurt the whole project.</p><p>The four pillars are all connected in a sense. Let’s break it down for you:</p><p>If your developer is not communicating with you, then they’re probably not going to hit the budget, and they’re probably not going to deliver it on time. And they’re definitely not holding themselves accountable because they’re not in communication with you.</p><p>Communication is key to the success of projects, but absent of accountability for work and staying on budget and schedule, that communication is pretty useless.</p><p>“If all I’m communicating is, ‘Hey, we’re going to miss your budget… We’re going to miss your budget…. Hey, we’re going to miss your budget,’ at a certain point, you’re not holding yourself accountable to that budget anymore; you’re not being a steward of their money,” said Dustin Ewan, vice president of software development at illumisoft. “Same goes for the schedule, right? You have to deliver the project sometime. So they can be adjusting their schedule over and over and over, but if you’re not delivering, that’s also not a successful project.”</p><h3>Success is delightful</h3><p>Sometime, you might hear Dan Prince, CEO and founder of illumisoft, say he wants to “delight our customers.” People often ask us, what does that mean?</p><p>That’s where these four pillars come in, as a commitment to these four concepts.</p><p>“We would consider our clients to be delighted if we have successfully communicated throughout the lifetime of the project, successfully delivered the project on budget, successfully delivered the project on schedule and held ourselves accountable for any bumps and bruises along the way,” Ewan said.</p><h3>Being accountable builds trust</h3><p>Your vendor is a steward of your money and time while working on your project. In fact, you should expect your vendor to be accountable to you from day one.</p><p>Part of being accountable to you involves maintaining clear, accurate and consistent documentation on the progress of your project. Is documentation a priority for you? If not, it should be. Developers often document their progress so they can refer back to it later — an important step that keeps them accountable and everyone on the same page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4XqXKcc611L8a6Ge.jpg" /><figcaption>How does a good team hold themselves accountable?</figcaption></figure><p>“Documentation is a means to an end,” Ewan said. “If it’s documented, both sides can go back and verify, ‘This is what I said, this is what you agreed to. This was your word.’”</p><p>Documentation serves two purposes: 1) It holds the developers accountable, and 2) It acts as evidence of the relationship between the client and the vendor.</p><p>“It’s nice to say something like, ‘Hey, we have such a great relationship; we shouldn’t need to document any of this stuff,’ right? But a relationship is great… until it isn’t,” Ewan said. “At that point, that’s when you should have some documentation.</p><p>“You also spend a lot of time on the phone going, ‘Hey, remember that thing we were talking about six months ago?’ ‘Well, kind of.’ It’s nice to be able to go back to look that up easily.”</p><h3>What you should expect from your vendor</h3><p>A good software developer anywhere will document their progress in a way that’s easy for you to follow along. For example, at illumisoft, your developer will typically provide you with a weekly report that lays out accomplished objectives from the previous week, priority objectives for the coming week and any identified risks with the project that need to be shared with you.</p><p>Once the product is fully developed, those weekly reports collectively serve as a record of the entire scope of the project.</p><p>“It shows the evolution of the project over time,” Ewan said.</p><p>Your developer will also follow up with you to make sure they’ve aligned the product with your vision. Oftentimes, you may find that the project needs to pivot and go in a different direction. That happens a lot, and that’s OK. Just let your developer know, and they will realign their vision to match yours.</p><h3>Managing expectations keeps the plan aligned with your budget and schedule</h3><p>You might think staying on budget for a project is assumed to be a given, but budgets often change as needed. Unforeseen circumstances can drive costs up or down. Likewise, a schedule is assumed to be a given, but deadlines are often missed.</p><p>At illumisoft, we have found that most of our clients interpret budgets and schedules as being written in stone. One client may say she has $15,000 for the project and not a penny more. Another may say he needs the product to be ready by November, period.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tXIw_YeBh15hWCSV.jpg" /><figcaption>Consistent communication makes sure our understanding and vision are aligned.</figcaption></figure><p>“But we find that 90 percent of the time that budgets and schedules are really fluid because of those unknown variables,” Ewan said. “Being on budget and being on schedule is, you know, a fluid, living concept throughout the lifetime of the project. They’re not so set in stone as we might have imagined.”</p><p>Very rarely are budgets and schedules hit; there are just so many unknowns that can impact your plans.</p><p>“It could be anything, from missing this requirement when we communicated something we didn’t understand fully, a developer got sick, bugs… you know, just so many types of things that can be thrown into the mix that could cause it to go off course,” Ewan said.</p><p>Even processes that are typically smooth, such as integrating with third-party applications, could delay a project if your developer underestimates the complexity of that integration.</p><p>“We can make some pretty good estimates about how complicated the integration would be, within reason,” Ewan said.</p><h3>How to ensure your expectations are met</h3><p>After you’ve laid out the blueprint for your project with your developer, they will give you a budget and schedule that fits their ability to deliver. Understanding that the budget and schedule are fluid will help you manage your expectations.</p><p>So long as your developer stays accountable to you and communicates with you throughout the project, it leads to the natural conclusion of being on time and on budget.</p><h3>Open communication keeps you in the loop on the progress of your project</h3><p>Accountability, keeping on track with a budget and staying on schedule are all vital elements of a successful project. But what good is your project if you don’t know anything about it? That’s why you should expect solid, open communication from your vendor.</p><p>When budgets and schedules are unlikely to go as planned, the more important thing your developer can do at that time is communicate that to you. In fact, keeping you in the loop should be your vendor’s top priority.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7eLZ7ysiOJtLWx0v.jpg" /><figcaption>Open communication builds trust and positions the client and vendor for making strong planning decisions.</figcaption></figure><p>“If we just stay silent when we have a problem and we’re not going to raise a flag — we’re just going to be head down and try to hit the budget — then there’d be a certain point where our client is going to be like, ‘What’s going on?’” Ewan said. “At that point, we haven’t communicated effectively, so now it’s a problem.”</p><p>By communicating any setbacks to you, it’s easier to adjust your expectations for the project as well. Your developer can re-adjust the budget and schedule as needed in moving forward.</p><h3>What to do when budgets and schedules aren’t fluid</h3><p>Of course, there are some cases where budgets and schedules are quite the opposite of fluid. But open communication exposes those circumstances, allowing your developer to prioritize in order to meet your expectations.</p><p>For instance, let’s say you’re a startup company and you just received a $25,000 grant, and that’s all the money you have devoted to your project. Once you’ve let your developer know that’s your cap on the project, they can adjust our scope in a number of ways, such as removing lower-priority features or saving money on designs for the user interface.</p><p>Once you’ve communicated that your deadlines are hard and fast, or your budget is restrictive and limited, your developer will pivot the direction of the project so it fits within the scope of your vision while not exceeding those limits.</p><h3>What next?</h3><p>As a client, you’re probably thinking that you need to learn more about technology in order to find a good vendor. But that’s a fallacy. The truth is that the vendor should have moved in your direction in order for it to be a successful project.</p><p><a href="https://illumisoft.com/hire-a-software-developer/">A good vendor will not only have the tech expertise to meet your goals but will also help you develop a plan for your project in a way that is easy to understand</a>.</p><p>“We should be working with the client to develop a plan, to establish good communication, accountability, all of this, instead of relying on a client to kind of mine that information,” Ewan said. “Because then the client’s in a really vulnerable position; they’re operating on faith. ‘I don’t really know; I can’t understand what these guys were talking about… so I’m just going to roll the dice and hope that I can get what I need out of them.’ A good vendor should have already moved in the direction and been laying a plan.”</p><p>Let us move in your direction. Do you have any questions? Please feel free to give us a call.</p><figure><a href="https://illumisoft.com/"><img alt="" src="https://cdn-images-1.medium.com/max/548/0*6uHsbTAoeuBBqJbR.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31b81027475c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>