<?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 Fatima Tayyip Sahovic on Medium]]></title>
        <description><![CDATA[Stories by Fatima Tayyip Sahovic on Medium]]></description>
        <link>https://medium.com/@fatimata_48437?source=rss-9556995a3a40------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zl1z23w_2DZAPcZOPBjTFA.jpeg</url>
            <title>Stories by Fatima Tayyip Sahovic on Medium</title>
            <link>https://medium.com/@fatimata_48437?source=rss-9556995a3a40------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:09:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fatimata_48437/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[Ground Rules to Running Successful Projects]]></title>
            <link>https://medium.com/maestral-solutions/ground-rules-to-running-successful-projects-b4a9be6cdee5?source=rss-9556995a3a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4a9be6cdee5</guid>
            <category><![CDATA[pm-toolkit]]></category>
            <category><![CDATA[pdaas]]></category>
            <category><![CDATA[pm-tools]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Fatima Tayyip Sahovic]]></dc:creator>
            <pubDate>Tue, 22 Dec 2020 13:04:36 GMT</pubDate>
            <atom:updated>2020-12-22T13:04:36.287Z</atom:updated>
            <content:encoded><![CDATA[<p>Being a Project Manager means always striving to bring out the best from projects; best from the time-frame you work with, best from colleagues, best from any unexpected situation or bump on the road during the product development. That’s our default mode.</p><p>However, there will come a moment in every PM’s life when things start lagging. It is easy to start getting reluctant in these moments and all of a sudden you have trouble catching up with the tasks, fearing that the team won’t hit project milestones as a result of this situation.</p><h3>The PM Toolkit for Project Success</h3><p>After years of working in project management, you encounter a lot of such moments both in your and your colleagues’ teams. The good news is that gets easier as your experience grows, especially if you have the right assets to help you navigate throughout this period.</p><p>Here are some guidelines and project management tools for running projects that enable the successful delivery of the software product, no matter the circumstances. If you’ve found yourself in a situation mentioned earlier in this post, you can use this list to identify the moment where things went wrong and learn how to avoid the pitfalls next time around.</p><p>Let’s dive in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jY9fTft4QBRO4cAH.jpg" /></figure><h3>Pre-Planning and Planning</h3><p>Pre-planning is the stage you should never, ever overlook — this activity sets the foundations for successful product delivery.</p><p>The goal of pre-planning is to:</p><ul><li>Identify the product vision</li><li>Define the product roadmap</li><li>Build an architecture blueprint</li></ul><p>In this phase, you define the MVP scope, prioritize features, gather technical requirements, and do a high-level time and cost estimation.</p><p>Once pre-planning is complete, it’s time to plan!</p><p>During this phase, you need to work out releases and iterations for the first few releases. This will ensure there is cadence around what will be released in the next couple of iterations.</p><p>Release planning can be done right after the backlog is created or after the first iterations are complete.</p><h3>Goals-Setting: The How-To</h3><p>Once you have defined the outline, it’s time to focus on the release goal — to build a shippable product.</p><p>There are various techniques you can choose from, and one of the most popular options is definitely <strong>SMART goal-setting</strong>. There is a good reason why this technique has remained so popular for a long time — it really works!</p><p>SMART goals characteristics:</p><p><strong>1. S</strong>pecific</p><p>Your job is to ensure that goals are clearly defined. Goals must be defined in such a way that they are very easy to comprehend, they need to be significant, yet simple. Clearly defined goals should answer the five “W”s: What? Why? Who? Where? Which?</p><p><strong>2.</strong> <strong>M</strong>easurable</p><p>Once you have defined specific goals, you need to ensure that they are measurable. Assessing your work and tracking the team’s progress become tremendously easier after implementing this step.</p><p><strong>3.</strong> <strong>A</strong>chievable</p><p>I can’t stress enough the importance of setting realistic, achievable goals. Wrong assessment at this point can pose many challenges down the road. Once your goals are clearly defined and you know how you will track them, it is your responsibility to create general guidelines on the best approach the team can take to accomplish each of these goals.</p><p><strong>4.</strong> <strong>R</strong>elevant</p><p>Relevant goals are realistic, reasonable, and result-oriented. For each goal that you set ask yourself the question: “Does this goal support the product needs?” and “Is chasing this goal a good investment of our time?”</p><p>The more relevant the goals, the more remarkable the results.</p><p><strong>5. T</strong>ime-bound</p><p>Always set a suitable deadline for your project, respecting the team’s capabilities and product time-goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fM7gFEDbPMGXAk4S.jpg" /></figure><h3>Brainstorming and Balance</h3><p>Once the hard work of planning and outlining your work is done, what’s next? The brainstorming, of course!</p><p>Layout all the team’s tasks to be done in the upcoming period. Go through the list, task by task, and write down everything that comes to your mind in regards to how that specific task/objective should be approached. This will waken up creativity with the team members and bring innovation to the process.</p><p>Here are some suggestions to follow and ensure that you have examined every angle of the project:</p><ul><li>Set a reasonable Group size</li><li>Look out for anchoring</li><li>Make sure you invite the people with the relevant skill-set</li><li>Define a clear and concise goal(s) with subgoals</li><li>Share ideas in writing to ensure every voice is heard</li><li>Make sure everyone reads out their ideas</li><li>Arrange team building game to strike the balance between productivity and fun</li><li>Create and Lead Creativity Exercises</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JTJMYDF_GpfZlGJo.jpg" /></figure><h3>Use The Right Tools:</h3><p>There are many great tools out there that can be used to manage projects. The key is identifying the ones that are right for building <em>your </em>product — just because something worked for one of your previous projects, doesn’t mean it will work as well this time, too.</p><p>Always remember: If you invest, you get the best!</p><p>To conclude this quick project success guide, we prepared a list of coordination and collaboration tools that will help you run the project successfully, especially if you have various people working remotely:</p><ul><li>Atlassian (Jira and Confluence (Knowledge Base)</li><li>Asana</li><li>ClickUp</li><li>Smarsheet</li></ul><blockquote><em>“No one can whistle a symphony. It takes a whole orchestra.”</em></blockquote><blockquote><em>H.E. Luccock</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4a9be6cdee5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/ground-rules-to-running-successful-projects-b4a9be6cdee5">Ground Rules to Running Successful Projects</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[Leapfrogging From Waterfall To Agile]]></title>
            <link>https://medium.com/maestral-solutions/leapfrogging-from-waterfall-to-agile-6f7dc8b82f30?source=rss-9556995a3a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f7dc8b82f30</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Fatima Tayyip Sahovic]]></dc:creator>
            <pubDate>Wed, 25 Dec 2019 13:42:00 GMT</pubDate>
            <atom:updated>2019-12-31T12:22:56.564Z</atom:updated>
            <content:encoded><![CDATA[<p>Contrary to popular belief, Waterfall is still alive and well (yes, even in software development). True, Agile as a delivery model has been winning “the battle” for quite some time now, and it is even making a name on its own in industries other than software, and making a noticeable impact — <a href="https://www.forbes.com/sites/insights-scrumalliance/2018/10/25/how-healthcare-education-and-marketing-organizations-are-using-scrum-to-thrive/#74fddbd11519">Forbes</a> agrees btw.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*I0ktHoYeft4c_rcNUw_R2A.jpeg" /></figure><p>Despite the downfalls of Waterfall that came to light when technology irrevocably disrupted the business landscape, it was hard turning our backs to something we‘ve gotten so used to.</p><p>Many organizations have fallen into a trap of thinking they have implemented Agile simply because they’ve introduced a few Scrum ceremonies. Realizing the approach of choice was in fact only Waterfall in disguise, and not Agile, was the hard part.</p><p>As a Professional Scrum Master and a Project manager for almost a decade, when I look back, the things that started to make me believe that we are doing Waterfall in disguise were directly related to the things I disliked about the Waterfall approach. <strong>The teams lacked flexibility and room for trial/error, preventing delivery on newly introduced, but crucial requirements that emerged mid-project. Long-term, this affected the quality of work and led to delays and unwanted disruptions. </strong>Not to mention that testing wasn’t continuously executed, but only done at the end of the process. Going back to fix bugs was extremely difficult and time-consuming.</p><blockquote>While embracing Agile promises that hold so many attractive advantages like <strong>faster product/features delivery, increased productivity, better capacity to manage changing priorities</strong>, to name a few, this was still a tough decision for our time. Especially when you have questions like this one hanging over your head:</blockquote><p><strong>How could we transition to Agile when we have Legacy? How to make a decision about transition when we are already so successful in our work so far?</strong></p><p>The transition to Agile is such a complex process compared to starting off Agile in a green field. However, when the time comes, it’s important to have a strong vision and strategy, and the right team to help you along the way.</p><h3>The Big Decision: Going Agile</h3><p>I’ll share our team’s experience with the client to whom we suggested the long-dreaded but necessary transition, including the challenges we faced and how we overcame them.</p><p><strong>About the client:</strong> A large multinational company offering device insurance and financing to telecom, retailers, and enterprises. We are engaged in building the next-generation platform that gets the value users have to a new level, as well as providing sustainment services for its legacy platform.</p><p><strong>Our goal: </strong>Identify the most suiting and simple process to motivate 100+ experienced professionals to get out their starting blocks and start working differently to improve operations together.</p><p>It’s crucial to find time to talk to people who are going to be affected by this change. According to research, <em>the biggest detractors of organizational agility are longtime employees (29%) — staff who are comfortable in their current roles and staunchly resistant to change.</em> Take time to talk to them, make it clear that yes, there will be challenges, but yes, there’s a plan in place to confidently overcome them. And of course, highlight the expected benefits thanks to which it will all be worth it in the end.</p><p><strong>Our strategy: </strong>As our team was well-organized and integrated with the client’s teams, we had clearly defined roles, and our collaboration was running smoothly, we came to a conclusion that an external Agile Coach will add value and help us achieve our goal in an efficient manner.</p><p>Although the strategy seemed simple, the tactics and going through with this journey was definitely not. There were infinite workflows to be created and implemented during this transition. We kept thinking “<em>How do we carry the momentum forward and how will this actually look like, once the process rolled out?</em>”</p><h4>Going Agile survival kit</h4><p>Our role during transformation became even more important than before: we had to keep the momentum going even through the turbulent times ahead. Below I listed out the things that helped us drive change successfully. If you’re working with distributed teams, feel free to use this like a check-list for the transition period:</p><ul><li><strong><em>Analytical mindset</em> </strong>— don’t forget to pay even more attention than usual to how activities in different roles are interconnected and how they affect each other</li><li><strong><em>Good communication</em> —</strong> review current communication procedures and tools to assess if they will support the team throughout the process</li><li><strong><em>Courage</em> </strong>— it’s hard to adjust the team’s mindset to do something disruptive when things are going smoothly as they are. Keep reminding everyone that what awaits, brings more rewards than the process undergoing at the moment</li></ul><h3><strong>Challenges and Solutions</strong></h3><h4><strong>Roles:</strong></h4><p>With the waterfall approach, we had one manager role, which was not sustainable in terms of continually delivering quality work in the long run. <br>This role was split into two: product manager, who was fiercely focused on managing the overall product value, and a delivery manager who ensured that everyone on the team is delivering their best work and was managing CI/CD pipeline. The result was improved organization capabilities, a stable, quality codebase, which brought us one step closer to the feedback loops.</p><h4><strong>Planning and Estimation</strong>:</h4><p>Trying to accurately<em> </em>estimate upcoming development activities before each phase is complete has cost us a lot of time and wrong expectations. And no, extensive experience in estimating doesn’t make you better at it when planning <em>that </em>far away into the future. <br>The new, agile approach allows us to plan in reasonable chunks (sprints or increments). This made the estimation process much more reasonable and considerably increased accuracy. Additionally, when we finish a successful iteration and get the stakeholder buy-in, we used our worn team velocity as a predictive measure.</p><h4><strong>Daily Scrums:</strong></h4><p>Having daily, brief and efficient in-person interaction with the team is extremely convenient and sounds like such an obvious activity. Unfortunately, this wasn’t the case when we started out. The waterfall cycles demanded weekly status from developers, who were updating the estimated schedule. The communication was slow and caused important information getting lost. Instead of speeding up to get behind schedule, we had to set aside time to re-plan and still get back on track with our tasks. Since teams who are behind their schedule at multiple milestones rarely get delivered on time, other options had to be introduced. Daily Scrums entered our daily routine, skyrocketing productivity. Listening to developers’ tasks and impediments every day benefited the entire team, because this way we avoided multiple interpretations of a status report, and we also get a daily confirmation that the entire team is on the same page.</p><h4><strong>Communication:</strong></h4><p>Communication of the daily status to our peers was motivating as each member had to articulate what they did yesterday, what they plan on doing today and what the impediments they have that hold them from completing their assignments. During a long 6 +month waterfall development cycle, slipping a week or two seemed harmless, but when you look at it from an Agile perspective, that very same number of weeks sounds alarming (well, because it is). Whether the challenge was technical or non-technical nature, any impediments are brought to the surface and addressed on a daily basis. Open and continuous communication flow highlights and supports accountability and dramatically improves efficiency.</p><h4><strong>Product Design:</strong></h4><p>Designing, reviewing, and finalizing dozens of deliverables in the waterfall quality gate irrefutably pushes stress to harmful and destructively high levels. Then it stops being a design problem and becomes the whole team’s problem. In the Agile approach, designing and testing became well-integrated with the rest of the development activities, which led to better solutions and outcomes, leaving the team more content since this way seemed to everyone much more logical.</p><h4><strong>Feedback loop:</strong></h4><p>No matter how great the starting idea, there is always room for improvement. Especially after getting feedback from the stakeholders and end-users. The sooner you become aware of this feedback, the better. The problem was that the UAT testing happens at the end of the traditional waterfall lifecycle.<br>I still recall the overwhelming stress when we had to do the end product all at once after the feedback came too late. In the end, the significant changes cost us a lot of time and effort. When operating with agility, getting feedback from a fully empowered product team/UAT team in the course of each sprint allowed the developer to make the correction as part of the sprint, provided more insight to the testing team before they tested the feature/enhancement and eliminated the risk of acceptance testing.</p><h3><strong>Looking back &amp; assessing the transition end-results</strong></h3><p>In our case, <strong>the transition helped our organization fully harvest the benefits of an Agile methodology by addressing the technical, managerial and organizational components of moving to a new approach. </strong>We’ve only decided to embark on this journey after assessing the benefits of the Agile approach vs. Waterfall and analyzing how it will affect the product quality and team.</p><p>There is no definite list of tasks to be executed in the exact right order that guarantees a successful transition. <strong>It is crucial that you have a crystal clear understanding of the current state of things and a vision where you want to take the team.</strong> Managing expectations and later on listening and talking to the team will help everyone act more positive about the change.</p><p><strong>The communication with the Technical Leads was one of the most important components of this endeavour. </strong>They were the main drivers in transforming operations by finding the right risk appetite in the organization, and afterwards the perfect timing for the important leaps that would ease the pains of the transition.</p><p><strong>You can expect and should be ready to manage behavioural shifts such as moving from managing individuals to building and leading teams</strong>. We went from manual routines to automated standards and from minimizing risks to an experimental mindset and exploring opportunities, thus boosting team creativity and productivity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f7dc8b82f30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/leapfrogging-from-waterfall-to-agile-6f7dc8b82f30">Leapfrogging From Waterfall To Agile</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[Product Development in (Mobile) Insurance Industry — Best Practices]]></title>
            <link>https://medium.com/maestral-solutions/product-development-in-mobile-insurance-industry-best-practices-a6abce7e9a49?source=rss-9556995a3a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6abce7e9a49</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[mobile-insurance]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Fatima Tayyip Sahovic]]></dc:creator>
            <pubDate>Wed, 17 Jul 2019 07:33:44 GMT</pubDate>
            <atom:updated>2019-07-17T12:49:41.626Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Development in (Mobile) Insurance Industry — Best Practices</h3><p>We’ve reached the point where getting lost in the glow of a smartphone screen has become a cultural certitude, a new norm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*mdRpT8Dyy37Zd-baSOfCng.png" /></figure><p>The shift from the traditional areas such as households and cars towards the mobile-driven world in the insurance industry was inevitable, launching this industry branch into a stream of steady growth.</p><p><strong><em>According to Reuters, mobile insurance industry revenue is projected to hit $27 billion by the end of 2020.</em></strong></p><p>In the era of digitalization and well-informed audiences, all organizations looking to remain competitive and grow are expected to incorporate sophisticated software.</p><p>This is definitely not a one-time thing. The rule applies both to their day-to-day operations as well as channels of engaging with the customers.</p><p>This is the step that enables organizations to effectively communicate and partner with customers to help them achieve their goals.</p><p>The mobile insurance industry is no exception to this rule. Digitalization enables insurer companies to enrich their offerings to match the needs of the modern mobile user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*sMcZtn6IrVKYAra5SjedUw.jpeg" /></figure><p>Successful companies have far moved from providing simple insurance plans and now provide their customers with full coverage for lost, stolen, damaged or malfunctioning devices, moving on to multi-device coverage, integrated device security, technical support, warranty, door-to-door services retention, and leasing programs.</p><p>Making innovative insurance plans a reality and a smooth journey for your audience helps in reducing churn and unlocking a steady revenue stream and needs to be supported by the right software product.</p><p>We’ve been successfully collaborating with one of the largest US mobile insurance companies for years, and we started the collaboration by building a next-generation platform for their services, coupled with power BI reporting.</p><p>Like many other insurance providers, our client was facing the common challenges of competing in the global economy: adopting a mobile-first approach, embracing disruptive technologies, successfully navigating the digital transformation path, automating workflows, integrating financial services, while at the same time providing an unmatched experience for the customers, to name a few.</p><p>To overcome these challenges, we started building a platform that easily integrates with a carrier’s or dealers’ system and enables effortless management of all aspects of the mobile insurance program.</p><p>This platform supports managing of all aspects of the mobile insurance, from subscriber enrollment to claim fulfillment. The platform’s goal is to remove the burden of program management, making it possible to deliver faster adjudication and replacement services to subscribers. Apart from Mobile insurance, the platform also supports Financial Services.</p><h3>Going back to the beginning</h3><p>Dozens of projects of this scope taught us that the only way to successfully tackle the development process and answer complex and extensive requirements is by taking a proactive stand, every day.</p><p>We started with creating a clear and strong version of what the global architecture needs to look like and understand all the nuances of the changes that need to be implemented. To ensure a transparent and consistent flow of information throughout the process, we defined the communication channels and procedures that are honored in our day-to-day operations.</p><p>Another important aspect to keep in mind is <em>smart reinforcement</em>; it’s important that you always have a clear vision of the scope and timeline. With a passion for getting the job done<em> with the highest quality, according to all standards and on time</em>, we managed to always keep track of our progress and where we need to be at what times. In turn, this resulted in improved CI&amp;CD pipeline and consistency in decision making.</p><p>The base strategy and a starting point were building a super-functional platform with offerings ranging from complimentary insurance scheme to bundled insurance with inexpensively priced mobile security offerings.</p><h3>The platform requirements and their evolvement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6EZ6UVzdHsxZjYt2XCdgOg.png" /></figure><p>Tapping into today’s wireless ecosystem, we had to make sure that the product supports the company’s goal: <strong>being agile and responsive in every stage of the device’s life, from the manufacturing to trade-in and re-marketing.</strong></p><p>Besides the core offering, the platform’s functionalities need to support complementary services, regardless of the phase, a device is in during its lifecycle.</p><p>The solution enables the client to enrich insurance plans with comprehensive protection, such as single device protection pack, multi-device protection pack, convenient repair options, such as equipment service, repair program and equipment protection plus.</p><p>Other significant product requirements including:</p><p>· Distribution made available via multiple channels: call center, online claims portals, vendor management system</p><p>· Post-Sales Support on devices and insurances</p><p>· Digital transformation and differentiation from the competition: Apps that combine all the services provided by the insurance companies</p><p>· Consistent service delivery from one region to another by rearchitecting the technology landscape</p><p>Deciding on building solution of this complexity seems challenging, but it pays off in terms of building a fruitful, long-lasting relationship with the client while upping the skills bar of your own team.</p><h3>Keep in mind</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*CvwEurAcoM6zVr8ItqvFTQ.jpeg" /></figure><p>The basic principle leading us when building software products is simple, and proven to be a recipe for success: <strong>Always keep in mind how the end-user engages with the product, and how effectively the solution serves them.</strong></p><p>This time we were quite thrilled to be unlocking the sterling digital experience for the users of mobile insurance services by allowing them to leverage the investment they made in their fleet of devices.</p><p>Any unanswered questions about the product development process in the mobile insurance industry? Just type your comments below, we are looking forward to hearing from you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6abce7e9a49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/product-development-in-mobile-insurance-industry-best-practices-a6abce7e9a49">Product Development in (Mobile) Insurance Industry — Best Practices</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[Challenges Of Working With Distributed Teams]]></title>
            <link>https://medium.com/maestral-solutions/challenges-of-working-with-distributed-teams-c16a89f40b8a?source=rss-9556995a3a40------2</link>
            <guid isPermaLink="false">https://medium.com/p/c16a89f40b8a</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[outsourcing]]></category>
            <dc:creator><![CDATA[Fatima Tayyip Sahovic]]></dc:creator>
            <pubDate>Mon, 19 Nov 2018 15:52:31 GMT</pubDate>
            <atom:updated>2018-12-03T16:28:08.674Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This blog focuses on teams that specialize in developing software products.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/1*REqkLL0kWC63xoA1PBueSg.png" /></figure><h3>First things first:<strong> What is a distributed team?</strong></h3><p>A group of people who work together but are separated by their geographical location, regardless of whether they stay in a different building or a different time zone.</p><p>Organizational structures may also vary, from only one member being in a different location to everyone being spread out across the globe. A team doesn’t have to be under the same roof as you to create magic, nor do they have to be employed at your company.</p><h4>Engaging such a team to develop your software product can provide substantial benefits.</h4><p><strong>Also, your competitive edge (business growth) depend on it.</strong></p><p>Partnering up with such a group of specialized experts has undeniable PROS:</p><ul><li>access to talent in one place,</li><li>teams that have experience of working together,</li><li>out of box thinking,</li><li>diverse teams drive creativity,</li><li>cost-effectiveness.</li></ul><p>However, naturally, certain challenges might arise when partnering with such teams. Being aware of those challenges can help you avoid potential issues and all the fuss that goes with it.</p><p>Having worked with distributed teams for over a decade, we have identified the challenges specific to working in this setting.</p><h3>So what are <strong>the key challenges?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mhpOpiCRovc1RHasoPymKw.jpeg" /></figure><ul><li>lack of in-person interaction,</li><li>timezone mismatch,</li><li>product delivery issues, and</li><li>cultural differences</li></ul><p><em>Let’s look at these more closely.</em></p><h4><strong>Lack of in-person interaction</strong></h4><p>Although there’s a number of communication technologies available, lack of actual in-person interaction can make it difficult to feel the energy, read emotions and judge the body language. Consequently, this makes it difficult to develop authentic relationships and to nurture a team spirit.</p><p>It can also be the source of misunderstandings leading to lack of trust and sometimes causing costly consequences. To prevent such issues from arising, it is of utmost importance to utilize existing collaboration tools properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*u9UBEG83ngj2mMBrA9hqzQ.png" /></figure><p><em>E-mail only</em> is not the best option, and we always advocate the use of tools with real-time communication options, integrated video chat, emojis, and gifs - all of which contribute to more human interaction.</p><p>Additionally, we strongly advocate creating a <strong>working agreement</strong> which clearly defines team communication procedures and ensures that they are frequent and concrete.</p><p>As a bonus, try to organize a visit to each other, or attend a conference together. This truly fortifies the relationship.</p><h4><strong>Time zone mismatch</strong></h4><p>Globally distributed teams often have issues identifying time overlap for productive meetings and timely feedback. It is important to include the update meetings in your working agreement so that all teams are reassured they will receive timely feedback.</p><p>Moreover, time zone differences have a psychological effect on the team’s dynamics. There’s a danger of people’s mood mismatch depending on the time of the day at their location. To avoid such negative effects, it is important to nurture private relationships and forge alliances between teams so they learn to understand and support each other.</p><p>A great tip that works for us is to always plan <strong>a few minutes of informal chat</strong> before the official part of the meetings so that people can relax and build mutual trust.</p><h4><strong>Cultural differences</strong></h4><p>While cultural diversity is a major asset to the project, it often causes issues related to language barriers and work culture. <strong>More fluent speakers in teams tend to speak more and position themselves as thought-leaders.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*A1JYbMl31T5FHWPylX-kug.jpeg" /></figure><p>It is important for team leaders to recognize those with less confidence and <strong>encourage them to speak up</strong> in the meetings. Another way of mitigating these differences is making sure there is written evidence regarding project activities; <strong>meeting minutes </strong>do not take long to write up and are highly useful and appreciated. Additionally, they allow more introverted team members to share thoughts.</p><p>Different nations have different work practices. By allowing people to share insights about their culture, you help reduce potential misunderstandings. This certainly results in honorable work ethics, healthier communication, and positive team dynamics. Again, <strong>informal chats help, but working agreements fortify the quality of output.</strong></p><h4><strong>Product Delivery issues</strong></h4><p>The process of delivering the requirements can be quite challenging because more often than not, teams are faced with <strong>confusing or incomplete solution design documents</strong> that are hard to read and digest.</p><p>We have found a couple of approaches that helped us eliminate the potential issues with product delivery:</p><ul><li><strong>Technical Grooming sessions </strong>where the product owner answers any questions the team has with regards to the solution design documentation, or an epic provided by the client; this allows the team to break down the epic and create additional user stories.</li><li><strong>JAD sessions</strong> where experts (product team and technical leads) come together to share their views about the product, sync the perspectives and develop a sense of project ownership.</li></ul><p>In our experience, the technical grooming sessions were particularly of great benefit to business intelligence teams.</p><h3>IN THE END, IT ALL BOILS DOWN TO CHEMISTRY</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*EXMaEw01qQmkgyJ0_Gy9IA.jpeg" /></figure><p>Challenges can easily be turned into assets if tackled properly. Just remember, it takes continuous work on individual level, consideration of others, an open mind and some serious planning. This way the team builds up their unique chemistry, and as a result, they achieve effective velocity.</p><p>If you have any comments, questions or suggestions, please feel free to contact us at <em>info@maestralsolutions.com</em> or connect with us on <a href="https://www.linkedin.com/company/maestral-solutions-llc/">Linkedin</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c16a89f40b8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maestral-solutions/challenges-of-working-with-distributed-teams-c16a89f40b8a">Challenges Of Working With Distributed Teams</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>