<?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 Shabbir Khan on Medium]]></title>
        <description><![CDATA[Stories by Shabbir Khan on Medium]]></description>
        <link>https://medium.com/@shabbirkhan?source=rss-2f0ddad4a1b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZXOCiD6h76fC-emf.jpg</url>
            <title>Stories by Shabbir Khan on Medium</title>
            <link>https://medium.com/@shabbirkhan?source=rss-2f0ddad4a1b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:44:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shabbirkhan/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[Benefits and Challenges of Outsourcing]]></title>
            <link>https://medium.com/@shabbirkhan/benefits-and-challenges-of-outsourcing-9fb1e98c0cb?source=rss-2f0ddad4a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fb1e98c0cb</guid>
            <dc:creator><![CDATA[Shabbir Khan]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 20:47:03 GMT</pubDate>
            <atom:updated>2023-03-21T06:12:38.291Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>In a Period of Global Economic Uncertainty</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xz75AtHMoO0BJgM4f3V1GA.png" /></figure><p><em>We are all living in the most interesting times.</em></p><p>Life has become lot more challenging for the software development managers all over the world. Economies are slowing down because of rapidly rising interest rates to counter an inflationary boom. If pushed too far, too many economies may enter a contracting economic phase. More vulnerable economies may fall into a self-reinforcing downwards spiral — a deflationary bust. We’ve just stepped into a long period of global economic uncertainty.</p><p>Massive layoffs in the technology industry are ongoing. It is possible that you are left with fewer resources in your engineering team. Your project budgets may have been further reduced as part of the most recent cost saving measures undertaken by your company. However, life must go on.</p><p>You are still responsible for delivering on some key projects for improving your organization’s operational efficiency while maintaining a competitive edge over other companies in your market segment. No other choice.</p><p>Outsourcing software development projects has always been a good option for reducing project costs, however, this approach comes with its own unique challenges.</p><p><strong>Let us examine common pitfalls and how to mitigate some risks associated with outsourcing projects overseas.</strong></p><p>Size of the vendor you are outsourcing your project to matters a lot. Equally important is the size of the talent pool available to the managers of the overseas team for staffing your project. Avoid any vendor that staffs your project with software developers who are working in a freelancing mode or are part of the project team on a contractual basis.</p><p>The talent pool available must be preferably employed by the overseas vendor. Of course, few exceptions can be made for overcoming a known skills gap in the overseas team. However, this talent pool should be big enough to quickly handle any future issues related to an unforeseen attrition or replacement of an overseas team member.</p><p><em>You expect your overseas team to work as an agile talent pod with each member striving towards a common goal. Therefore, quality of each individual member that is part of the overseas team is critical to the success of your project. A large variance in the quality of individual team members will slow down the overall progress of your project.</em></p><p>Building a high-quality development team is non-trivial though. To begin with, overseas vendor must have implemented an elaborate screening process to build its talent pool. More smarter vendors reduce the variance in the quality of their developers by investing heavily into the training of their employees using university programs or technology bootcamps that are organized by well-known training companies that are affiliated with universities.</p><p>Overseas team members may have excellent role-specific knowledge and technical skills but ignoring soft skills required for completing a project successfully is perilous. All reliable overseas vendors put a lot of emphasis on training their employees not only in technical skills but also in soft skills including teamwork, fluency in communicating in a language preferred by the client, emotional intelligence, problem solving skills, critical thinking, persuasion, creativity, time management, stress management, leadership, adaptability, resourcefulness, and openness to reviews and criticism.</p><p>Time zone differences commonly cause communications delays and negatively impact delivery schedules. This could be overcome by using an overseas team that practices agile methodology including daily sprint planning, scrums, demos, retrospectives and daily communications between your project team and the overseas team.</p><p>Only counting on good coding skills of your overseas team does not guarantee success. Lack of good project control and ill-defined performance expectations generally lead to a disaster. Many questions come to mind in this respect. Do you have good project managers in place — both in the overseas team as well as in your own engineering team? Do members of both teams have access to application domain experts with experience in your industry? Do both teams use a common source code control system, task tracking tools, and bug reporting software? How fast are technical and non-technical issues being addressed by the managers?</p><p>Project managers, quality assurance managers, and software developers need to pay close attention to documentation at every stage of the project to avoid any knowledge transfer issues that may lead to more than expected software maintenance costs in future after the project is done.</p><p>Culture trumps everything. Cultural differences may lead to a misunderstanding and even a potential conflict. Both parties need to be fully aware of each other’s cultural nuances for a smooth execution of the plan. In particular, the management of the local outsourcing team has a responsibility to inculcate its own corporate culture, ethics, and values in the members of the overseas team for achieving common goals.</p><p><strong>There is art and science involved in choosing the most suitable business engagement model for outsourcing:</strong></p><p><strong>Fixed price model</strong> works well only in short-term situations where software requirements, project scope, and budgets are well-defined. Be ready to pay extra fees if there are any changes to the pre-approved requirements or project scope.</p><p><strong>Time and Material model </strong>is more flexible for a long-term engagement. It allows you to change software requirements and project scope during the development process. Time and material model applies previously negotiated fixed rates (hourly, monthly, quarterly, or yearly) for each team member on a role-specific basis.</p><p><strong>Offshore Development model</strong> is an integrated business model suitable for well-funded startups and large multinational corporations that prefer dedicated remote workers overseas to augment their own human resources. In this case, the company using the services of a dedicated team working in an offshore development center (ODC) pays its overseas partner for building, managing, and maintaining the infrastructure of the ODC; rent, utilities, and local purchases; running a payroll service on behalf of its business partner, and complying with all local regulations including country’s corporate law, local taxes, and custom duties on imported equipment.</p><p>Legal processes vary from country to country regarding labor laws, confidentiality, liability, performance warranties, data protection, security, and intellectual property rights. It is imperative that both the outsourcing team and the overseas team have clearly defined all deliverables, delivery schedules, legal protections, and mutual obligations in a written, enforceable contract before starting a project. Commonly overlooked areas include dispute resolution mechanisms for handling breach of an agreement and for providing appropriate remedies to the aggrieved party.</p><h4>In conclusion, partnering with an offshore vendor brings major benefits if you are cognizant of the challenges involved. It is a great business strategy for developing and testing new products at affordable costs and staying ahead of the competition provided detailed planning is done and proper processes are put in place for a successful execution.</h4><p><em>Shabbir Khan is currently serving as a Director of Emerging Technologies at xloop Digital.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fb1e98c0cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seeking Happiness in Product Management? Start Coding!]]></title>
            <link>https://medium.com/@shabbirkhan/seeking-happiness-in-product-management-start-coding-1c35fd6f08c5?source=rss-2f0ddad4a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c35fd6f08c5</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Shabbir Khan]]></dc:creator>
            <pubDate>Thu, 22 Jun 2017 21:16:43 GMT</pubDate>
            <atom:updated>2017-06-22T21:16:43.040Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Part 1</strong></h3><p><strong>By Shabbir Khan</strong></p><p>Let’s say that you’ve been doing product management most of your life. You were successful in progressing from a junior level position to a pretty senior position in product management at a large public company after years of hard work. You’ve become a domain expert in more than one technologies.</p><p>You’ve mastered the art of keeping your sales and field engineers happy.</p><p>Engineers in your product teams respect you because you know so much about the latest technologies and your product roadmaps. You also read their source code every night to stay on top of their progress without telling them about it.</p><p>Marketing is happy because you help them craft the most effective positioning statements to keep your products differentiated from the competition.</p><p>Managers are happy because you are good at producing solid PRDs (product requirements documents) and delivering release after release like clockwork. CFO loves your pricing strategies because you’ve been using the latest research in behavioral economics for pricing your products.</p><p>You control your cost of goods sold (COGS) like a hawk. Your products meet the profit margin goals that are consistent with your company’s business model. Everybody in the company is happy with your performance.</p><p><strong><em>Everything was going great for you till you foolishly accept a job offering you a VP Product Management position at a software startup targeting millions of end-users.</em></strong></p><p>You were never ready for the new painful reality — reality of working for an underfunded startup that doesn’t know when it will be able to raise its next round of funding. It is a SaaS company with a dubious customer lifetime value (LTV). You suddenly find yourself living in the belly of a beast.</p><p>Company doesn’t have the money to hire a design engineer to give you the user experience you are looking for. It doesn’t have the money to attract more experienced engineers who can build a large-scale cloud app.</p><p>Your front-end engineers have been using an outdated framework (MVC) for building traditional apps in C# using .Net or C++ for a Microsoft Windows platform. Couple of engineers have built small web sites using HTML, CSS, and JavaScript. There are some engineers who have built mobile apps in Objective-C but nothing that can scale up to handle millions of users.</p><p>Your backend engineers are real good at coding PHP and J2EE servlets accessing traditional SQL databases. Although your engineering team is excited about developing a cloud-based application (using a NoSQL database), nobody has produced and deployed a real product in the cloud.</p><p>You also discover that although you can deliver most of your product’s functionality in a browser, there is a critical part of the app that could only run in a native mode. Now you are worried about supporting a large variety of devices — all with different screen sizes.</p><blockquote>“This is a job from hell”, you start saying to yourself. You wake up in the middle of the night dreading your next day at work. All you can see is that you’ll be wasting another day convincing your engineers to adopt a full-stack application mindset for scalability, security, and performance in the cloud. You are worried about your next meeting with the CEO because you don’t have a good answer about your product’s delivery date.</blockquote><blockquote>I was faced with a similar situation at the last startup I was a part of. It was pretty painful till one day I told myself, “quit this job or start coding yourself and lead the engineering team to develop this product”.</blockquote><p><em>I used to program before moving into product management but that was many years ago. Let me chronicle how I was able to change the situation and reclaim my happiness as a product manager.</em></p><h4>Ready to get hit by a cocktail shaker?</h4><p>I immediately called a friend who used to work for Google. We went to a local Starbucks. He listened to my problems. I described the new application stack I had in mind for deploying in the cloud. He liked it but warned me that I’ll be confronting a bigger issue. If I make any change in the front-end, it has the potential to percolate all the way to the backend. And if I change anything in the backend, it will cause a ripple effect all the way to the front-end.</p><p>“It will be like getting hit with a cocktail shaker”, he told me with a big smile on his face while shaking an imaginary cocktail shaker in his hands.</p><p>I decided to minimize the <em>cocktail shaker</em> effect. I thought I’ll be able to tame this beast if I could make my front-end and backed engineering teams agree upon a RESTful API for the entire product before they start doing any coding.</p><p>I was confident because I had a very clear vision of what the product was supposed to do. I knew what functionality our customers were looking for in the user interface. I had it all in my head so I started calling all hands engineering team meetings to explain what was in my head.</p><p>Learning to design a RESTful API is relatively easy. Luckily, there are plenty of sites on the Internet for teaching you how to design a RESTful API. All you’ve to do is to google using the key words, e.g., design a RESTful api.</p><p>Before I knew it, I was talking a language that included verbs (GET, POST, PUT, PATCH, DELETE), nouns (e.g., users, contacts, messages, notifications), and filtering, sorting, and searching of results.</p><h4>A new disaster hits me !</h4><p>Getting an agreement on the need for a RESTful API for the entire product was easier but achieving that goal proved much harder. Nobody could agree on anything and our RESTful API team meetings started degenerating in chaos without any end in sight.</p><p>I stopped holding RESTful API meetings with all of the engineers in the same room.</p><p>I started pairing up only one front-end engineer with one backend engineer making them responsible for designing the RESTful APIs for only one <em>microservice</em> at a time. I started holding shorter meetings with each pair of engineers focused only on an individual microservice.</p><p>It worked. Before we knew it, we had the whole RESTful API done. I told everybody if they wanted any changes to any of the microservices they should come to me.</p><p>We also standardized on using JSON for exchanging data between the frontend devices and backend servers. It is a widely used format in the industry. A word of advice: avoid using XML unless you are building a content management system or XML is the only thing you know.</p><p>I also started worrying about security in a public cloud. I had few experimental EC2 instances running in the AWS cloud. One month, for no apparent reason, I started seeing my Amazon bill going through the roof. I immediately called Amazon support and found out that my EC2 instances were sending a lot of outbound Internet traffic that I was not responsible for.</p><p>I was sure that none of my EC2 program were causing this traffic. It turned out that somebody was constantly probing my ports and hitting them with some random packets resulting in an outbound traffic that I was not expecting.</p><p>Lesson learnt. Security is important. First of all, there are lot of hackers out there who love to break into systems just for fun. There are non-state actors (including some of your competitors) who may be interested in knowing what you are doing. And let’s not forget the state-sponsored actors including the Chinese, Russians, British, and, of course, the NSA. They are all out there to get hold of your data if you are paying any attention to the revelations made by Edward Snowden and Julian Assange.</p><p>It was a good time to become lot more serious about security. I had no choice but to close all unnecessary ports, use TLS, deploy a virtual private cloud solution, and enforce stricter access controls on all assets.</p><p>I had started feeling a bit more confident with a RESTful API design in my hand. I thought that all of the engineers in my product team will become full-stack programmers soon. Rest of the implementation should be smooth.</p><p>Time to have a party and celebrate? It was too early to celebrate. My troubles had just started. Wait till you see Part 2.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c35fd6f08c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>