<?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 Leila Catic on Medium]]></title>
        <description><![CDATA[Stories by Leila Catic on Medium]]></description>
        <link>https://medium.com/@leila.catic?source=rss-ba7c6e1bbe78------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FeWQPM3b0BtN-Pb4VvNXTA.jpeg</url>
            <title>Stories by Leila Catic on Medium</title>
            <link>https://medium.com/@leila.catic?source=rss-ba7c6e1bbe78------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:24:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leila.catic/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 Tales: A Cross-Functional Team Reflects On a Seamless Software Delivery]]></title>
            <link>https://medium.com/maestral-solutions/agile-tales-a-cross-functional-team-reflect-on-a-seamless-software-delivery-2721150276df?source=rss-ba7c6e1bbe78------2</link>
            <guid isPermaLink="false">https://medium.com/p/2721150276df</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile-development]]></category>
            <dc:creator><![CDATA[Leila Catic]]></dc:creator>
            <pubDate>Mon, 11 Nov 2019 14:28:39 GMT</pubDate>
            <atom:updated>2019-11-11T15:23:55.296Z</atom:updated>
            <content:encoded><![CDATA[<p>Over a year ago we embarked on an exciting journey with <a href="https://www.linkedin.com/company/virgil-holdings-inc/"><strong>Virgil Holdings</strong></a>.</p><p>Virgil takes great pride in being the largest community of hospitality talent at 5.7 million members — and growing.</p><p><a href="https://www.hcareers.com/"><strong>HCareers</strong></a><strong> </strong>is<strong> </strong>their well-established hospitality recruitment platform. It is a real-time, tech-first solution for employers and professionals in North America’s hospitality industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AH1HClcuByfuNp81" /><figcaption>Team members (Daria, Amar, and Ena)</figcaption></figure><p>With an aim <strong>to revolutionize job search in the hospitality industry, </strong>they decided to build a next-generation platform<strong>. </strong>A challenge welcomed both-handedly by our team of software experts (Product Owner/Project Manager, UI/UX Designer, Developers, Testing Engineers, and DevOps Engineers).</p><p>It didn’t take long before we agreed that the <strong><em>Product Delivery engagement model</em> </strong>was the right fit for this partnership. You can read more about our working principles and different Maestral engagement models<a href="https://maestralsolutions.com/engagement-models/"> <strong>here</strong></a>.</p><p>Once the platform has been successfully launched, we conducted a little team survey to reflect on the work done. Retrospectives are king.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QXTjXoJBQJhSlSl5" /><figcaption>The whole team</figcaption></figure><p>Team members interviewed: <br><em>Ena (PM)<br>Benjamin (UI/UX)<br>Alican (Dev)<br>Ervin (Dev)<br>Daria (QA)</em></p><h3>We asked:</h3><p><strong>1. As a PM you are responsible for multiple parts of the process: managing the team’s efficiency, client expectations and end-user expectations — which skill did you find most valuable in balancing all of these?</strong></p><p><em>Ena (PM): </em>I found strong communication skills to be the most valuable asset. With such a diverse team from both our side as well as the client’s, good communication was essential to make sure we were always on the same page. Naturally, it is not always easy to communicate effectively when there are many people involved.</p><p>Sometimes team members don’t get a chance to speak or voice their opinions, so we made sure to keep our communication channels open —<em> direct conversations saved us a lot of time.</em> Thanks to expectations set early in the process, the communication flow was smooth. The Virgil team was exceptionally professional, meetings were productive and efficient, and every chance to have a good laugh before or after our standups was well used!</p><p><strong>2. Working with a distributed team can seem like a big challenge. Were there any obstacles in your collaboration that the time difference caused and how did the team approach these?</strong></p><p><em>Ena (PM): </em>The time difference did not seem to be a big issue in our case. It all comes down to setting expectations on time, mutually respecting agreements and each other’s time while taking our responsibilities vigorously serious.</p><p>We organized the communication flow that suited everyone best. Slack was our main communication tool, but we reported weekly status emails to make sure we were all on track throughout the week. Besides this, we had our regular stand-ups and ad hoc meetings when needed. To bridge the distance, we used webcams during our meetings. It changed the nature of our relationship tremendously because it helped put a face to a name. I believe this was one of the key things that helped us have good communication and interaction with the Virgil team.</p><p><strong>3. How much did the scope change since the start of the project?</strong></p><p><em>Ena (PM):</em> You don’t even want to know the answer to this question haha. A lot! Talk about agile. Joking aside, we understand that when it comes to business software, changes are an inevitable part of the process. With time you learn how to structure the agile process to handle them effectively. However, good luck is nothing but a result of good planning, so we put an emphasis on estimation, planning and direct communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bqf78woKoDnIf5g9" /><figcaption>Team members (Alican and Amar)</figcaption></figure><p><strong>4. How would you describe the challenge of designing the career portal?</strong></p><p><em>Benjamin (UI/UX): </em>It shouldn’t be a surprise that one of the most important factors a designer should consider when designing a product is the audience. If you plan to design a product your users will love, you must have an idea of what your audience actually wants and needs. This means user research should be an essential part of the UX design process.</p><p>A system like a career portal needed to be well-organized, understandable and feature-rich without being overwhelming. Users should be able to focus on finding the perfect career or the perfect candidate and not on searching for buttons and options all over the screen. It is always a challenge to deal with data-heavy platforms, but one I happily embraced.</p><p><strong>5. From the perspective of a QA, what advice would you give to others testing recruitment sites?</strong> (QA)</p><p><em>Ervin (Dev): </em>Automation testing should be considered mandatory for platforms like this one. Automation tests can save you when launching to production and will ensure quality over the long run.</p><p><em>Daria (QA): </em>The recruitment site is like every other site when it comes to testing: every part of the application should work as expected and provide the best experience for job seekers. However, the Hcareers portal collects thousands and thousands of CVs and cover letters, so security was a top priority.</p><p><strong>6. What were the best 3 things about working on the HCareers engagement?</strong></p><p><em>Ena (PM): </em>The team dynamic on Virgil is like no other — with a team of 13 we are a very tight-knit group.</p><p><em>Daria (QA): </em>The team.</p><p><em>Alican (Dev): </em>The team spirit. Working with a big team enables learning and understanding multiple perspectives; looking at things from a different angle.</p><p><em>Ervin (Dev): </em>Team, great selection of technologies (the most popular in the industry), openness to new ideas.</p><h3>Conclusion</h3><p>It’s no secret that diverse, cross-functional teams deliver fantastic results. But it’s important to remember that this is true only when the process is properly managed and structured to support the product vision.</p><p>As with all complex processes, there are challenges. The difference with having an experienced software partner is that they know how to overcome them less painfully. The case we described above gives a unique, honest insight into a very productive client /software partner relationship. We hope this inspires you to improve on your current team organization and deliver in a more efficient manner.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2721150276df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/agile-tales-a-cross-functional-team-reflect-on-a-seamless-software-delivery-2721150276df">Agile Tales: A Cross-Functional Team Reflects On a Seamless Software Delivery</a> was originally published in <a href="https://medium.com/maestral-solutions">Maestral, an HTEC Group Company</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Partner Story: Building Next-Generation Platform for #1 Hospitality Career Site]]></title>
            <link>https://medium.com/maestral-solutions/aws-partner-story-building-next-generation-platform-for-1-hospitality-career-site-8d2048c5a3c0?source=rss-ba7c6e1bbe78------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d2048c5a3c0</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[career-website]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Leila Catic]]></dc:creator>
            <pubDate>Wed, 30 Oct 2019 15:30:12 GMT</pubDate>
            <atom:updated>2019-10-31T14:49:53.613Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS Partner Story: Building the Next-Generation Platform for #1 Hospitality Career Site</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6GDvcQcAUCVsMSoGcfVd4g.jpeg" /></figure><p><strong>HCareers — the largest hospitality recruitment and career platform in North America</strong></p><p>Virgil Holdings Inc. owns and operates HCareers, the world’s most comprehensive career navigation, and recruiting platform. The HCareers platform utilizes proprietary machine learning algorithms and micro-assessments to match job seekers to the perfect career path, employment opportunity, and developmental resources. They serve a diverse customer base including individual job seekers, corporate recruiters, job boards, higher education institutions, trade associations, workforce agencies, and nonprofits. <em>Virgil’s mission is to create greater transparency in the career navigation process for all job seekers.</em></p><p>With years of experience in running a well-established career platform, Virgil wanted to revolutionize the job search in the hospitality industry. The plan was to merge the existing Virgil and HCareers functionality into a next-generation platform featuring improved infrastructure and user experience.</p><p>Virgil selected Maestral based on the recommendation of a past Maestral client. With no existing team that was familiar with the next-generation technologies, Virgil was looking for a single product development partner with the capacity to run User Experience Design, Development and DevOps.</p><p><strong>HCareers 2.0</strong></p><p>The new improved technical solution was to make it easier for hospitality job seekers to find ideal opportunities matching their career goals, while also helping employers find the right talent quickly and easily.</p><p>The vast majority of infrastructure we used in building the new platform was provisioned as a fully managed service by AWS.</p><p>AWS was chosen as the cloud computing platform for its capacity to enable fast and reliable product delivery through a comprehensive set of services. The platform offers a wide range of benefits that were a perfect fit for building HCareers 2.0.</p><ul><li>The platform <em>security and reliability</em> are unparalleled</li><li><em>Flexible costs</em><strong>: </strong>pay-as-you-go model allows for cost optimization</li><li><em>High availability</em> ensures continuous delivery of value to users</li><li><em>Auto Scaling</em> helps maintain steady, predictable performance at the lowest possible cost</li><li><em>RDS Automated Restore</em><strong> </strong>provides piece of mind for data continuity</li></ul><p><strong>Leveraged AWS Technologies</strong></p><p>Apart from using standard cloud services such as AWS S3 for object storage and AWS EC2 for virtual machine workloads, we decided to use AWS Fargate as a container orchestrator, AWS RDS as a managed RDBMS, ElasticSearch for real-time data access, SQS for Message Queuing Service and SNS for sending various notifications to Message SQS.</p><ul><li><strong>AWS S3 Buckets </strong>— Used to store common files like database seeds, job seeker resumes, the company’s image gallery and public application images.</li><li><strong>AWS EC2 Instances </strong>— Used to host an Open VPN Server that provides external users access to resources provisioned on private internal subnets.</li><li><strong>AWS Fargate</strong> — Used to achieve scalable and managed service for Docker containers without the need for maintenance of underlying virtual machines. AWS Fargate enabled rapid development and testing, and then seamless transition into production.</li><li><strong>AWS RDS </strong>— With automated backups, retention, and restore point in time features, AWS RDS enabled easy and fast access to the database for development, staging, and production workloads.</li><li><strong>ElasticSearch </strong>— Used to support advanced searches by job seekers and real-time scoring calculations to determine user/company fit based on data input from users.</li><li><strong>SNS and SQS</strong> — Leveraged to keep all services in sync and for various background tasks. Both services are easy to set up, maintain, and consume by custom apps and services.</li></ul><p>AWS services are by default <strong>highly available, configurable, stable, flexible, and scalable with automatic data backups and data retention options</strong>. Development teams prefer them since they are easy to use and consume, and even more so because they are easy to integrate with other services. The collection of AWS services cost-effectively enable rapid prototyping, development, testing, and continuous integration/continuous deployment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d2048c5a3c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/aws-partner-story-building-next-generation-platform-for-1-hospitality-career-site-8d2048c5a3c0">AWS Partner Story: Building Next-Generation Platform for #1 Hospitality Career Site</a> was originally published in <a href="https://medium.com/maestral-solutions">Maestral, an HTEC Group Company</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Win The “Estimates” Game]]></title>
            <link>https://medium.com/maestral-solutions/how-to-win-the-estimates-game-43dba2ddea1?source=rss-ba7c6e1bbe78------2</link>
            <guid isPermaLink="false">https://medium.com/p/43dba2ddea1</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[estimation-proces]]></category>
            <dc:creator><![CDATA[Leila Catic]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 14:18:57 GMT</pubDate>
            <atom:updated>2019-09-25T14:28:39.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vUSR4qvwwpkIVCW2s_AUdQ.jpeg" /></figure><p>Known as “the dark art”, software estimation torments everyone across different industries. There’s no way around estimation, and there is no escaping it. In software development, things tend to get even more complicated. Managing different expectations, ever-evolving requirements, keeping up with technologies advances and updates and making sure that everything mentioned does not affect your team’s productivity. Talk about challenging! <br> <br> BUT — it’s not all bad news when it comes to the estimates. There are actually ways to learn how to play the estimates game, and once you’re familiar with these, you’ll stop looking at estimates as unnecessary task and understand how they can bring value to your teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*Aj-EhcJlUtycNQ7U1x7qNA.png" /><figcaption>Source: <a href="https://twitter.com/onek2go/status/714059284049428480">Twitter</a></figcaption></figure><h4><strong>With many projects in the bag, here are a few gems of wisdom from our team:</strong></h4><p>In order to answer the question: “How do I get better at estimates?”, let’s start at the beginning and define this process. You’ll probably come across many different explanations when you do the research on the topic, but here’s a definition we believe sums it up pretty well:</p><blockquote>Estimation (or estimating) is <strong>the process of finding an estimate, or approximation, which is a value that is usable for some purpose even if input data may be incomplete, uncertain, or unstable</strong>.</blockquote><p>So, if the input data may be incomplete, uncertain or unstable why do we even need estimates? Simply put; in order for someone to put their trust and resources in you, they have to know, with at least some level of certainty, answers to the following questions:</p><ul><li>What do we get for our money?</li><li>Can we predict our costs?</li><li>What will it cost to create the product we want?</li><li>When can we launch?</li><li>Will we get a quality product for our investment?</li><li>Will it grow our business?</li><li>Will it deliver business value?</li><li>What kind of team to put together?</li></ul><p>Obviously, these are serious matters and at this point you might find yourself turning to comforting excuses. So, in case you ever need to feel a bit better before embarking on the estimates journey, we picked some of our favorite excuses we’ve heard over time:</p><blockquote>“Estimates are rarely even close to accurate”<br>“All you are doing when you estimate a piece of work is to set false expectations”<br>“In practice, estimation is seen s a commitment, not as a best guess”<br>“We don’t have enough information to provide an estimate”<br>“Clients don’t even know what they want”<br>“Why do we even estimate if there is a deadline”</blockquote><p>Now, after you’ve given yourself some time to grieve over the fact you have to begin the estimation process, let’s jump to an important question will help you become Estimation Superhero:</p><h3><strong>Why do we suck at estimates?</strong></h3><p>There are significant mental “challenges” which affect the way we think and reason when it comes to estimates. Understanding the effects of our brain playing tricks on us will definitely help you avoid some of the most common mistakes that occur. Take a look at the list below and see if you recognize the thought patterns in any of the following:</p><p><strong>The Halo Effect </strong>If you’ve formed an opinion that overall the project will be easy, all your estimates for the component parts are likely to be lower than if you viewed the project as difficult (also known as the “devil” effect).</p><p><strong>Framing Effect</strong> Refers to the way our mind perceives data differently depending on how it is presented.</p><p><strong>Over Confidence / Under Confidence</strong> We are very likely to be confident in an estimate if we have convinced ourselves that we know what we’re talking about.</p><p><strong>Anchoring / Peer Pressure </strong>Is an effect that causes you to bias your estimate based on estimates you’ve already seen or produced.</p><p>Another factor to be considered is <strong>the moment when you make predictions</strong>, and this is an important one. Take your time to evaluate all variables that might impact the project — requirements, dedicated team, business context, technology and priorities, as these will be unique for every new project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*ENB67Mbt2Pz8y9Hs8wfJMA.png" /><figcaption>Source: <a href="http://www.agilenutshell.com/cone_of_uncertainty">Agile in a Nutshell</a></figcaption></figure><p>Now that you understand what your brain has in store for you, it’s time for the next, essential phase — choosing the right method.</p><h3>How do I choose the right estimation method?</h3><p>Choosing the right method and approach you’ll use is equally important as successfully completing the process. By now we all know that there is no universal “best approach”, and that accuracy of your estimates strongly depends on the context. But, choosing the method based on the phase you’re currently in can give you a push in the right direction. Depending on the phase you are currently in, be it the<strong> inception/pre-sales</strong> or <strong>elaboration/construction</strong>, you’ll need a different method that will help you create reliable estimates.</p><h4>Inception/Pre-Sales:</h4><p>In this phase, we are talking about <strong>high-level estimates. </strong>We’ll cover the estimates that occur during project selection and approval period, and prior to project initiation.</p><p><strong>Rough Order of Magnitude </strong>The main purpose of the ROM estimate is to provide decision-makers with the information necessary to make a decision on whether it makes sense to move forward with the project. This is actually an estimation of a project’s level of effort and cost to complete. A ROM estimate takes place very early in a project’s life cycle — during the project selection and approval period and prior to project initiation in most cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDMSgL2eL1xLgKhN2hXGJA.jpeg" /></figure><p><strong>Expert Judgment </strong>Expert Judgement is supported by historical data, previous experience and process guidelines. There is some <a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.18.2813&amp;rep=rep1&amp;type=pdf">controversy around this method</a> — for example, it can be subjective, prone to error and bias, that it is difficult to quantify and validate the estimates and so on. At the same time, the advantages to using expert judgment are numerous: speed (they are quick to produce), require little resources in terms of time and cost and they can be as accurate as other more expensive methods.</p><blockquote>The scope is huge! This can’t go under a year! <br>- every senior software developer ever</blockquote><p><strong>Comparative or analogous / relative estimation </strong>This method is based on previous projects, using extrapolated data and overall project success. Make sure you leverage best case practices from the past and don’t forget to make adjustments for mistakes you remember making along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*k1hS6Tsu_AC1vm4yv5iHoA.png" /></figure><p><strong>T-Shirt Sizing / Top-Down </strong>This method, even though it lacks detailed analysis, works best for a quick first-pass at a prospective project to assess its viability. High-level work breakdown structure helps you create rough estimates on the expected workload throughout the time and helps set the initial expectations. Top-Down method is a great way to start and allows your team to adapt to changes in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VPgc3hXGx6l-RX_jETT2Uw.png" /></figure><p><strong>PERT Three Point Estimate </strong>Turn to this method when you’re working on projects that are especially unique, such as in research and development where you encounter many unknowns. The PERT Three Point Estimate technique is a type of three point estimate. The only difference is that it applies weighting so that the most likely estimate is weighted 4 times more than the other two estimates (optimistic and pessimistic).</p><ol><li>Estimating time/cost</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/229/1*Ml5PsCQpM0RLvjPZCyrf0g.png" /><figcaption><strong>E</strong>=estimate, <strong>o</strong>=optimistic estimate, <strong>p</strong>=pessimistic estimate, <strong>m</strong>=most likely estimate</figcaption></figure><p>2. Calculating Standard Deviation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*IxwhMBsVyzugk8K0W25gpg.png" /><figcaption><strong>SD</strong>=standard deviation, <strong>p</strong>=pessimistic estimate, <strong>o</strong>=optimistic estimate</figcaption></figure><p>3. Projecting Estimates to Confidence Level</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*qBgeExEjqkzJ0MWGGbYLKQ.png" /><figcaption>Software development will usually use 95% confidence level</figcaption></figure><h4>Elaboration/Construction</h4><p>“The project is in the full swing and we can all finally take a break from estimates!” Unfortunately, it’s highly unlikely you’ll be lucky enough to hear or say this sentence. Let’s move on to project execution, post project initiation and sprint planning, and estimation that will, in the end, make your life easier.</p><p><strong>Bottom-up / Story Points </strong>Don’t fear to commit to this method just because it can be more time consuming compared to other techniques. It’s best to decide on this method once you are already committed to a project because it uses a detailed work breakdown structure. Each task is estimated individually, and afterwards, the estimates are rolled up to give the higher level numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*reLTL4jGD3ObvZXW66M9VA.png" /></figure><h3>Coping with RFP Estimates</h3><p>Throughout the time, we’ve had our share of challenging projects. The initial step, estimating a project based on Request for Proposal (RFP) is never easy, but always worth it. Estimating RFP requires you to know every detail of the project and ask all the right questions in order to present estimates that are relevant for your client.<br>In the end, these projects only amounted to the extensive experience of our team members, so we were able to put together action steps that guarantee smoothly running process. We’re positive these points will make your life easier:</p><ul><li><strong>GET FAMILIAR </strong>— put together all the information you possess and get familiar with the product before you continue</li><li><strong>USE ESTIMATION SHEETS — </strong>put all the requirements/or assumptions into the initial backlog in a form of an epic or high-level requirements</li><li><strong>DISCUSS WITH THE TEAM — </strong>the team should collect all the questions or concerns after reviewing the initial backlog</li><li><strong>GET FEEDBACK — </strong>get in touch with a client and get the missing information or details, if possible, to fill in the blanks</li><li>and to the most exciting part — now you are ready to<strong> SHIP IT!</strong></li></ul><h3>Learnings to take with you</h3><p>Estimates — we can’t live with them and can’t live without them. It is a long journey but definitely an important, dare we say crucial one. Before you leave, let’s cover the most important learnings to keep in mind:</p><ul><li>Only high-level estimates are possible in the early stages of projects, but the<strong> level of uncertainty has to be communicated clearly</strong></li><li>There are a couple of methods available to help you provide the estimates in an early stage of a project where <strong>three-point estimation is the one most used</strong></li><li><strong>Bottom-Up Method</strong> uses a detailed work breakdown structure, and is best once you are already committed to a project</li><li><strong>Never, ever skip the step of getting familiar with the product</strong>. After that, use all available tools and previous experience, but don’t forget to discuss it and review it. After taking these steps, you are bound to succeed.</li></ul><p>Happy estimating!</p><p>Here at Maestral Solutions, we make sure to gain in-depth understanding of your business and specific requirements, align estimates with plans and goals so the final outcome brings absolute satisfaction with the completed project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43dba2ddea1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/how-to-win-the-estimates-game-43dba2ddea1">How To Win The “Estimates” Game</a> was originally published in <a href="https://medium.com/maestral-solutions">Maestral, an HTEC Group Company</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>