<?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[Ryan Sinha for ITWD Blog - Medium]]></title>
        <description><![CDATA[CEO’s opinion on what’s going on with the IT development in the U.S. - Medium]]></description>
        <link>https://medium.com/ryan-sinha-for-itwd-blog?source=rss----dd869b18079d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Ryan Sinha for ITWD Blog - Medium</title>
            <link>https://medium.com/ryan-sinha-for-itwd-blog?source=rss----dd869b18079d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:51:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ryan-sinha-for-itwd-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What Roles and Responsibilities Should Define the Startup Founder for the Success of IT Development]]></title>
            <link>https://medium.com/ryan-sinha-for-itwd-blog/what-roles-and-responsibilities-should-define-the-startup-founder-for-the-success-of-it-development-a40ef6be3939?source=rss----dd869b18079d---4</link>
            <guid isPermaLink="false">https://medium.com/p/a40ef6be3939</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[IT WatchDog Inc]]></dc:creator>
            <pubDate>Thu, 26 Sep 2019 11:37:41 GMT</pubDate>
            <atom:updated>2019-09-26T11:37:40.894Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QvbAUK7S5lIMOB67kQpbMA.png" /></figure><p>Talking about the startups, I always say that it is vital to building an efficient team to be a success. Moreover, the primary responsibility of a founder is to make every team member engaged in developing a potent product. It doesn’t mean that everyone has an equal part of the coding/UI work, but if everyone gives valuable input, you get a well-weighed product. Of course, the most significant part of the work still stays for the development team.</p><p>In IT WatchDog, we often consult startup founders, who want to optimize a technical team structure and function. Sometimes it is easier to move towards an external development than to wait for results of long-term transformation. Then we help with speeding-up the onboarding of new programmers as we engage them from the pre-contracted list. However, not every startup can afford managed service as we provide. That is why I’ve written this article. In it, I will share my expertise and help startup founders to organize efficient work by themselves. So, let’s have a closer look at the essential responsibilities and roles in the product team.</p><h3>Central Roles in the Agile IT Product Team</h3><p>The startup differs from the project of traditional business: to be a success, the startup should have its founders fully involved in finding the product-market fit. You face many challenges and have to define roles for the best speed and adaptability. It is especially important to set the right roles and workflow at the beginning as later the unsolved problems would scale.</p><p>The most important roles for the Agile team are:</p><ol><li>Product Owner, who could also be the Chief Executive Officer (CEO) or if your company grow you may give this role to an executive with a marketing background</li><li>Scrum Master, who could also be the Chief Operations Officer (COO) or HR-manager</li><li>Leader of the Community(-ies) of Practice (CoP), who could also be the Chief Technical Officer (CTO).</li></ol><p>For the startup, it is more useful to have the in-house Product Owner and Scrum Master because these people ensure the efficient workflow and clear vision of the project. The development team (i.e., the coders) can be easily outsourced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6cef92WvqkWEhTYj0wXsig.png" /></figure><h3>Product Owner: Responsibilities in a Team</h3><p>The Product Owner (PO) works closely with the customers. He organizes meetings, discussions, sprint demos — presentations of the product iterations with feedback from average customer representatives. PO role in the startup team is essential for:</p><ul><li>Creation of the product’s vision and prioritizing its features.</li><li>Managing finances and funding.</li><li>Hiring and team building. PO recruits specialists and makes them work together as a well-coordinated mechanism.</li><li>Supervising and cooperation with the Leader of Community(-ies) of Practice.</li></ul><p>If the CEO takes this role, he also manages legal, security, and taxation models to ensure a sustainable business model.</p><h3>Scrum Master: Responsibilities in the Team</h3><p>Scrum Master (SM) ensures the productive work of the team. He works as a servant leader to help the team practicing Agile most optimally. With time it becomes more mature, so SM provides new techniques to increase the value delivered. Also, SM helps to keep a regular rhythm of Scrum events.</p><p>If COO takes this role, he observes the effectiveness of operational and financial procedures on the spot. In the small team, there is no COO, so HR-manager or any team member can perform the role of SM.</p><h3>Leader of the Community(-ies) of Practice: Responsibilities in the Team</h3><p>Another vital role is the Leader of the CoP. The CTO may be the same person, but we insist that the product leadership stays on the Product Owner as he has a business perspective. The Leader of CoP works as a technology mentor for developers: UX, backend, DevOps, and QA.</p><p>There could be several developers of some specialty or the only one in the whole company. With growth, your startup becomes more than 9 people in the development team. Then you might think about distributing them into several teams working on the same product. Consider choosing the scaling framework, which we discussed in <a href="https://www.itwd.com/three-switches-of-scaling-your-product-development">another article</a>.</p><p>The Leader of the CoP is responsible for:</p><ul><li>Developing and implementing the technology strategy.</li><li>Solutioning and architecture building.</li><li>Ensuring the skills growth, and knowledge sharing.</li></ul><p>There are potentially four specialties of developers in a startup. Each of them makes a possible contribution to the product while collaborating inside one Agile team or several teams united by the scaled framework. Let’s look inside each group of developer specialties.</p><h4>UX Specialties</h4><p>The user experience developers create the best possible experience for the users of your software. Such team members create a functional and attractive design with the means of frontend development. For the efficient work, you should have such roles in the team:</p><ol><li>UX researcher undertakes the learning of the software audience. This developer runs usability tests, conducts user surveys, undertakes audits of systems, researches how the users interact with the prototype/product. This role can be performed by the Product Owner, or by the whole development team.</li><li>UX designer designs the interface of the product to create a distinct look and feel of the system, creates wireframes, design mockups, prototypes, frontend HTML/CSS, and templates.</li><li>Frontend developer builds a website with JavaScript, HTML and CSS technologies. He makes sure that the product is responsive (it functions normally on the PCs, tablets and mobile devices) and quick (the loading time is minimal).</li></ol><h4>Backend Specialties</h4><p>The role of backend developers is to create the core of the application. These team members make it possible for the logic of your product app to interact with cloud services. They also ensure robust interaction of the frontend and backend parts of the software through API endpoints. The essential roles for backend developers are:</p><ol><li>A backend developer is a specialist in PHP, Ruby, Java or other server-side technology. The coder creates and maintains the app logic, data and application integration, databases, performs deployment-related tasks.</li><li>A middleware developer connects the frontend and backend parts of the product. He responds for server-side software, which works for information flow between an application, and the server, database and OS.</li></ol><h4>DevOps Specialties</h4><p>DevOps people are specialists, which are focused on the management of cloud infrastructure. They add the new code to the repository before the deployment begins and test the new code. The objective of these specialists is to achieve a perfect user experience and improve the time-to-market. The key roles in this group of specialties:</p><ol><li>Cloud architect builds and manages the cloud infrastructure, chooses cloud platforms and services for the deployment, decides on the optimization of the deployment.</li><li>SRE, or site reliability engineer, works for the performance, availability, monitoring, and response to the incidents on the platforms and services the startup runs.</li><li>System administrator builds and maintains servers, user accounts, supports software engineers and managers. This specialist also works with the network infrastructure, supports development, and production infrastructures.</li></ol><h4>QA Specialties</h4><p>The quality assurance specialists exist to test the application and make sure that there are no bugs and errors. Its primary responsibility is the efficient and stable performance of the software. The key roles:</p><ol><li>QA analyst is responsible for the test plans. The specialist develops, manages, and performs manual and automatic testing, produces the related documentation and creates the test suites.</li><li>Tester has the only responsibility: to run tests. The specialist collects, reviews and analyzes the test results, and creates a report for the QA analyst.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmJQ1RQSWAf5P1lxOcvq3g.png" /></figure><h3>Building a Team for the Successful IT Development</h3><p>With this article, we tried to create a mental structure on optimal dev team structure and responsibilities. Use the list to identify which specialists would you need to develop an IT product.</p><p>When you have already defined the needed roles for your startup, finding the right specialists to hire is still a challenging assignment. As soon as you get a complete image of the team you need, you have three options:</p><ol><li>In-house development team.</li><li>Staff augmentation — partial outsourcing.</li><li>Dedicated development team — full outsourcing.</li></ol><p>I believe that the startup should have an in-house Product Owner and Scrum Master. The rest of the developer team may be easily outsourced. Especially with the managed services model of IT WatchDog. We offer the supervising of IT vendors that lowers the risks for your startup. We check the developers before you hire them and do control them during the whole workflow.</p><p>Working with the managed service, you get the result while concentrating on other tasks. In-house PO and SM focus on better knowledge of the needs, interests, and pains of the customers. These roles take care of funding and relations with investors. The Product Owner sets the development vector for the team, prioritizes the tasks, and controls the quality.</p><p>At the same time, the outsourced development team completes the tasks by priority, prepares the product to the sprint demos, controls the quality with the internal QA technologies.</p><p>Relying on the managed service in external development, you get a good job well done. You have the peace of mind that your MSP contracted the most appropriate IT vendor and set the most efficient workflow. As a result — you have an IT product of outstanding quality, but you don’t need to control every step of the developers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a40ef6be3939" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ryan-sinha-for-itwd-blog/what-roles-and-responsibilities-should-define-the-startup-founder-for-the-success-of-it-development-a40ef6be3939">What Roles and Responsibilities Should Define the Startup Founder for the Success of IT Development</a> was originally published in <a href="https://medium.com/ryan-sinha-for-itwd-blog">Ryan Sinha for ITWD Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Trust to Your ICO]]></title>
            <link>https://medium.com/ryan-sinha-for-itwd-blog/building-trust-to-your-ico-c5c0a4fd06c5?source=rss----dd869b18079d---4</link>
            <guid isPermaLink="false">https://medium.com/p/c5c0a4fd06c5</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ico]]></category>
            <dc:creator><![CDATA[IT WatchDog Inc]]></dc:creator>
            <pubDate>Thu, 19 Sep 2019 12:12:34 GMT</pubDate>
            <atom:updated>2019-09-19T12:12:34.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d1dz2jDePojXc2AJTWlTqA.png" /></figure><p>What did you hear about ICO (Initial Coin Offering) and how do you feel about it? We at <a href="https://itwd.com/">IT WatchDog</a> are regularly requested advisory for introducing blockchain technology into IT startups or checking its benefits for conventional business. The ICO is the most frequent request, so let’s dive into it in great detail.</p><p>I perfectly understand the state of mind of startup founders. They face a lack of funds for creating their novel product, so each method to hack the investment traditions could be the last chance to survive. With this article, I will shed light on this opportunity to raise funds from multiple investors via ICO, when you become issuer and administrator of a token.</p><p>I need to start with a notification that this instrument lives through not the best its days. The highest point of popularity of the ICO was in 2017. Since then, many investors have burnt their fingers on the downfall of the ICO/cryptocurrencies bubble. Today the funds raised are much smaller than a few years ago. Nevertheless, the general picture of the industry is nothing if your startup would be one of the hundreds, which raised money for further development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*AGdYNZaaEMpqXuPebz14WA.png" /></figure><p>Now investors are very cautious in choosing a project in which they will invest. Many cases of fraud have worsened the ICO reputation. So 2019 is the time for perfect products and skillful marketers. Prepare your campaign thoroughly and get your funds.</p><p><strong>ICO has several advantages over traditional fundraising:</strong></p><ul><li>Short-term outcome</li></ul><p>You can raise a significant amount in a relatively short period. You spend 4–6 months on an awareness campaign and get your investments in a period between minutes to weeks. Compare with 1–2 years spent for attracting the attention of investors or venture funds, negotiations, paperwork for the deal, and getting access to the funds. I even do not compare with satisfying regulatory requirements of IPO.</p><ul><li>Small investors</li></ul><p>The smaller payment a person makes, the less he will convert his doubts into delays. The ICO can attract a large number of small investors, which is the future of funding some new risky ventures.</p><ul><li>Reaching the new customers</li></ul><p>A hype made for selling the tokens to investors reaches the second goal at the same time. The customers read the news and come into the sales funnel. There is even the third level of outcomes, which is increasing the personal brands of the founders. Show them frequently during the ICO campaign, and later their words will sell the product to their audiences.</p><ul><li>Keeping your equity and voting rights</li></ul><p>Usually, by purchasing tokens, ICO investors do not receive any authority or rights on your company equity. You raise your funds and maintain control over the project.</p><ul><li>Less documentation compared with traditional fundraising;</li><li>You do not depend on geographical location: investors can purchase your tokens from anywhere in the world.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4mAYpgqa4X-QaDe4Q5rdcg.png" /></figure><p><strong>What Types of Tokens Are There?</strong></p><p>There are two large groups of tokens: Security and Utility ones.</p><ul><li>Security tokens. This category gives the right to receive basic assets, dividends, the right to interest payments, or some other benefits in the future. They are similar to stocks, derivatives, and bonds.</li><li>Utility tokens — give access to goods and services, which investors may use in the period of issuance. This criterium is the main for the Howey test, which the regulators use in their practice.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_b7RP6MYWu3rCGMqktNb0Q.png" /></figure><p>The USA is known to be a long-arm jurisdiction. It uses its laws for all regulated deals provided to US citizens from any other country. It means that you need to build your product on the ‘utility token’ model, which is not yet regulated by the US Securities and Exchange Commission. Two other options are more complicated and less profitable: to pass all prescribed steps on registering ‘security tokens’ (a mammoth-like procedure similar to IPO) or prohibiting US citizens from buying tokens with KYC-procedure (know-your-customer).</p><p>Keep an eye on ICO regulation being constantly changing (https://www.sec.gov/ICO). Under federal laws SEC supervises securities, and Security Tokens are financial securities that must comply with the rules of securities. To avoid problems with the SEC, you must build the working ecosystem, which uses tokens inside. Designing such architecture and implementing a business model in it is a tricky question defining startup success. It is something <a href="https://itwd.com/">IT WatchDog</a> helped many times as a consultancy. Feel free to apply before the ICO campaign wasted your money or left a negative imprint on reputation.</p><p>Now let’s talk on attracting investors and building trust in your ICO. You can develop a perfect product that will be useful to the whole world. However, your success depends on earning users’ trust, and convincing your venture is not a scam. Let’s go through the main points needed to succeed.</p><p><strong>Create Your Web Presence</strong></p><p>Create an optimized website for your ICO startup, where anyone can find all the necessary information. Make an animated video in which you present your product, its usefulness, stage of its development, and ultimate goals. It is also essential to insert subtitles in different languages ​​to make the video available to the maximum number of users.</p><p>Everything should look as transparent as possible. Use graphs and charts for a better experience. Describe the relevance of the problem that your product can solve and the importance of solving this problem. Do not try to exaggerate the prospects. There is a good proverb on this subject: “too good to be true”. So if the investor has such a thought, it will frighten him away.</p><p><strong>ICO White Paper</strong></p><p>The White Paper is a document that sets out detailed instructions for your project. Studying ICOs, the White Paper is the first thing to which investors pay attention. State all information clearly and accessibly, write everything with the easy to read font. Various charts, graphs, and photos will have a positive effect on perception. Here you describe your team, your product, its benefits, risk factors, token distribution (the procedure for the distribution of tokens among parties, fees, and expenses). The development roadmap is probably the most important thing. The potential investors evaluate not the dream of your product success, but the realistic style of your plans and stages of project progress. Be sure you have shown all the critical dates in this plan. Check if your plans look feasible. Otherwise, it may cause suspicion.</p><p><strong>Team</strong></p><p>The team is the base of your project. You must convince investors that real professionals are working on the product, and they put their professional reputation at stake in this project.</p><p>Introduce your team to users on White Paper, website, social networks. Briefly describe each team member:</p><p>• Specialty, and what position does he occupy in your startup;</p><p>• Track of records;</p><p>• Experience in this field;</p><p>• Links to his pages on LinkedIn and Twitter.</p><p>I advise you to go even further. Create an incentivized board of experts, who will care about the business success of your startup, not just making a successful ICO campaign. Select the experts in the industry, technical aspects, legal, finances. It would be best if you had a full scope of expertise to direct your business and make the right decisions.</p><p>This approach is widely used in startups being invested by venture funds. Such experts will make you necessary introductions in the industry and will give the needed signs of long-term ambition for potential ICO investors. Your audience will feel that the failure of the project may destroy the career of respected advisors, so the trust in your venture will be much higher.</p><p><strong>Promoting Your ICO</strong></p><p>Your success is how much investors will buy your tokens. You can come to this objective if you gain an outstanding audience reach. Media and social networks could do it.</p><p>Advertise everywhere you can. Try using ads on Facebook, Twitter, Reddit, Instagram (be careful, some of them may prohibit the ICO campaigns, so check before starting your media plan). Write your blogs on Steemit and Medium. Create groups in Slack or Telegram for communicating your audience.</p><p>Be sure you post your latest news and achievements as frequent updates are something showing your project to be viable. It is essential to be active in your community. Promptly and openly answer user questions to leave them without the slightest doubt.</p><p>Some ICO managers even cheat their audience by boosting with artificial methods the number of followers on social networks. Others believe that the main thing is not quantity, but quality. So invite influencers on making comments on your social pages and use other engagement techniques.</p><p><strong>Creating Minimum Viable Product (MVP)</strong></p><p>Why do you need an MVP? It is essentially a preliminary version of your product with the essential function in solving the problem of customers. The MVP release is the only way to show your strong intent for the investors. Moreover, it allows them to test the traction of your product by seeing the response of users and the growth numbers.</p><p>From an investor’s point of view, the open code of MVP will significantly increase the trust level of your idea. They will be able to check the quality of your code and see that it does what you state without any fake mechanisms.</p><p>To succeed in ICO, you need to go through many decisions. <a href="https://itwd.com/">IT WatchDog</a> may help with advisory before you start. We will identify the most appropriate blockchain use in your conventional business or business model for your startup. Then we will choose the right blockchain technology (as there are many of them) and develop architecture. If everything said is already made by your founders, we may help you to develop an MVP. Alternatively, we may add the blockchain functionality by <a href="https://www.itwd.com/plug-in-team-for-stanwood">adding an external plug-in team</a> with appropriate expertise. Make your ICO safe and profitable for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5c0a4fd06c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ryan-sinha-for-itwd-blog/building-trust-to-your-ico-c5c0a4fd06c5">Building Trust to Your ICO</a> was originally published in <a href="https://medium.com/ryan-sinha-for-itwd-blog">Ryan Sinha for ITWD Blog</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 Communicate With a Remote Team to Minimize the Fails]]></title>
            <link>https://medium.com/ryan-sinha-for-itwd-blog/how-to-communicate-with-a-remote-team-to-minimize-the-fails-e19259b54ca3?source=rss----dd869b18079d---4</link>
            <guid isPermaLink="false">https://medium.com/p/e19259b54ca3</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[IT WatchDog Inc]]></dc:creator>
            <pubDate>Mon, 09 Sep 2019 13:43:10 GMT</pubDate>
            <atom:updated>2019-09-09T13:43:10.342Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOQYhKPy20di3_Xx9eM2PA.jpeg" /></figure><p>The share of external IT development is continually growing. <a href="https://medium.com/ryan-sinha-for-itwd-blog/is-it-reasonable-for-startups-to-do-their-software-development-in-house-f2d83c020ac1">In my previous Medium article</a>, we researched the reasons why startup founders and top executives of traditional businesses decline from developing in-house. Instead, they are hiring remote freelancers or entire teams of employees. We at IT WatchDog well understand what such clients face during the first year.</p><p>As our primary focus is to provide a consultancy, we are often invited for late phases of such projects to redesign the workflow or replace the team. The people responsible for managing are usually at emotional burnout; the company has missed its deadlines and failed the market objectives.</p><p>My experience shows that ordering clients can always prevent such a loss of time and money. The managers of their IT vendor need to set the work in the right way. Of course, the workflow is not the strong point of IT outsourcers. Big chance that your vendor will be chaotic, and you will need to set the workflow on your own. To protect from such risks, I always recommend working under a managed service model with companies like <a href="https://itwd.com/">IT WatchDog</a>. For those companies that could not afford a managed service, we decided to write this article with advice.</p><p>It is always easier to ignore the systemic problems and treat the situation with the replacement of a remote team/employee. You can even return to in-house teams. However, remember the time-to-market accelerating, focusing on your product-market fit and other benefits. You, as a manager, will never get your company to the highest margin if you do not use the full potential of external development. So better to implement a system of effective management of the remote team before it is too late.</p><h3>Distribution of Accountability</h3><p>The conventional model of management demands the individual accountability of each particular specialist. Due to such a role-distribution model, employee engagement was low. Each employee tried to make the imitation of business, while the manager had to fight the fires by catching employees for new assignments.</p><p><strong>1. Team-Spread Accountability</strong></p><p>Nowadays, IT developers work predominantly under Agile management methodology. According to it, the accountability for the task lies on the entire team. This model significantly fuels the interest of team members to collaborate and communicate with each other. You may imagine how this is important when you do not co-locate your people.</p><p><strong>2. Another Way to Control</strong></p><p>In Agile methodology, a manager is called the Product Owner. He is engaged in product development, communication with customers, and collaboration with stakeholders. He does not need to «oversee» the slacking employees.</p><p>How is accountability assured? Agile is a unique way to collaborate as the effectiveness is reached by the other way to communicate. There are no financial penalties or painful speeches from a manager. For keeping accountability, you keep the rhythm of events and remind the team responsibilities.</p><p><strong>3. Responsibilities of Development Team</strong></p><p>The responsibilities of the development team include participation in all required events and keeping the commitments made for the short working cycle (it is called a Sprint). Such commitments are not easy to follow as the team works with the unpredictable nature of tasks that never the same as they did in the past. However, team collaboration supports resource reallocation between team members.</p><p><strong>4. Team Autonomy</strong></p><p>How the manager (the PO) keeps the team accountable? He reaches a trade-off: the team gets the full autonomy inside the Sprints while provides transparency of what they have done finally. The Product Owner may attend the daily meetings of the team (they are called Daily Stand-ups), but his role prohibits him from asking for a status on any tasks. The team strives for maturity in their Agile application, so they progress in making everything with their self-management.</p><p><strong>5. Team Reporting</strong></p><p>At the end of the Sprint, the team and Product Owner gather to the event called Sprint Demo. They check the tasks under the quality standards of the Product Owner. If some are not ready — they go back to the task list (it is called Backlog). The Product Owner does not blame the team; he explains what this task means for the success of the project. If the maturity of the team is below average, the mission of another role called the Scrum Master (SM) becomes critical. He shows for the team their general productivity and raises the discussion of feelings to fail the Sprint.</p><p><strong>6. Continuous Improvement</strong></p><p>The team and the PO discuss such failures during the event called Sprint Retrospective. Nobody receives any penalties, but team members explain each other their expectations on the matter of failed commitments. Such the way the self-management starts and team members begin to trace all the promises made. It teaches developers to be assessed by their colleagues based on quality and results. All employees that lag regularly or have a lack of collaboration could be asked to leave the team. This practice takes away the function of «bad boss» from the manager as there is no need to penalize his workers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*amFYB1A3Tt75vQT3bCvWgw.png" /></figure><h3>Communication Artefacts</h3><p>The remote way of work is always harder than co-located workplaces. The shared artifacts are the things that make such a workflow easier. The team members look on an object from different geographies and time zones and have the same vision of the situation. Here goes the effective communication.</p><p><strong>1. Productivity Charts</strong></p><p>The first thing the team should look at each day is the charts with their results in dynamic. It works as the mirror — you make a step (one sprint) and see how you move the picture.</p><p>We recommend focusing on the Team Velocity chart and BurnUp chart. The first one shows the speed of the team measured in a number of tasks or Story Points (they show task complexity). The latter one uses the team speed for predicting the date when it completes all priority tasks.</p><p><strong>2. Tasks Trackers</strong></p><p>The second key to simplifying work with a remote team is the creation of an online Scrum board. It should work on the flow of the Kanban board and contain proper functionality for task tracking, project management, and analytics.</p><p>For 2019, the top Scrum boards tools are the following:</p><ol><li><a href="https://trello.com/">Trello</a></li><li><a href="https://www.atlassian.com/software/jira">Jira</a></li><li><a href="https://www.pivotaltracker.com/">Pivotal Tracker</a></li><li><a href="https://asana.com/">Asana</a></li><li><a href="https://www.ravetree.com/">Ravetree</a></li><li><a href="https://www.zenhub.com/">ZenHub</a></li><li><a href="https://blossom.co/">Blossom</a></li></ol><p>The software you will use is not as essential as the commitment to use it systematically. You need to track 100% of tasks through it. Make the task tracker the central artifact of your rhythmical events — Sprint Planning, Daily Standup, Backlog Grooming, Sprint Review.</p><p><strong>3. Implementation</strong></p><p>The manager (Product Owner) must choose the artifacts that will be most convenient for him and Scrum Master. Each of the tools has its pros and cons, emphasis on certain aspects of the work process. Besides, they are all customizable, and there are additional modules, for example, to build analytics, visualize some metrics (i.e., Cycle time, Lead time).</p><p>The chosen artifacts become a standard for the whole product team. Be sure to present their benefits and leave no ambiguity on its use. Many freelancers and remote workers are accustomed to specific software to control the workflow, so a good manager sells them the tracker used in his company. Be sure you gave the prescribed steps for learning the system and announced the competency test.</p><h3>Streamlining Work Schedule and Communication</h3><p><strong>1. Work Rhythm</strong></p><p>When managing remote employees, it is crucial to familiarize each developer with the work rhythm. A qualified manager will discuss it during the job interview as the indispensable request of your company. Just explain that you work under Agile methodology, and you will have a set of events, which are obligatory to participate.</p><p>You may play with strict and flexible attending their remote workplaces during the day. People choosing remote work usually appreciate the chance to have a walk or gym training in their flexible schedule. You leave it for their team to self-manage.</p><p><strong>2. Control From Management</strong></p><p>The only things your Scrum Master looks at are:</p><ul><li>all events do occur rhythmically</li><li>all team members do actively contribute during events.</li></ul><p>There are plenty of free and paid utilities for online teleconferencing, so there is no need for advice on that matter. Let’s say that each event needs to be time-boxed. It is better if someone in the team will take the responsibility of connecting everyone and watching the time spent. Scrum Master is the role of observer and facilitator but is not a manager for the meetings. Most of them do belong to the development team, while the PO and SM have the service roles only.</p><p><strong>3. Written Set of Rules</strong></p><p>Besides, an essential aspect of effective communication is the introduction of messaging etiquette. This document needs to be in written form and may save much time for the remote team. It is beneficial as chats are an essential tool for collaborative work, but they do absorb much time.</p><p><strong>4. Events</strong></p><p>Working under Agile methodology suggests several main types of rhythmical events (meetings):</p><ul><li>Sprint Planning</li><li>Daily Standup</li><li>Backlog Grooming</li><li>Sprint Review</li></ul><p>It is essential to schedule the Daily Stand-Ups at the same time. Consider different timezones and be sure to take the most convenient one for all developers and the Scrum Master. Also, check that all Sprint Planning / Backlog Grooming / Sprint Review meetings are planned at the time the Product Owner available. These meetings are vital for the team to understand the vision and features requested, so spend enough time for online discussion.</p><ul><li>One-to-one. Agile does not prescribe this meeting, but it is incredibly useful. Check that PO and SM have their separate meetings with each team member monthly. It touches on almost all aspects of the work process — from the issues of the comfortable workflow to discussing prospects and new ideas that an employee can bring for general company development.</li></ul><p>It should also be emphasized that all team members have the right to discuss or demonstrate their work to the Product Owner on their meetings during the Sprint. It is wise to block some timespots in his calendar so that anyone may schedule with PO an online appointment for 15–30 min. The developers need to get the feedback as early as possible before the PO makes his final verdict on the Sprint Demo session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j8YDIxDBBac50kws3oduSQ.png" /><figcaption>Events in Agile Methodology</figcaption></figure><p><strong>5. Transparency</strong></p><p>An important aspect of cooperation is a possibility for team members and the Product Owner to know the current state of the project. It will give the chance to provide early feedback or discuss the existing barriers. The Sprint becomes ‘done’ or ‘failed’ not on the moment of Sprint Demo, but much earlier. So team members frequently contact each other and find a way to reallocate their time and wisdom.</p><p>The main requirement of transparency is that the team moves the cards with tasks through columns of the Scrum board. So anyone may check the status of each job.</p><p>Implementing all these tools and advice will make communication with the remote team to be productive almost equally to the co-located team. With time the skills of Agile leadership become more trained among managers, and the development team achieves a higher level of maturity.</p><p>Many companies turn to us after reaching a standstill or deep crisis in their project. If the IT outsourcer fails to set the right workflow, then the ‘fight the fire’ mode is inevitable. There should be a moment to stop the failure and rebuild the management and communication processes. <a href="https://www.itwd.com/streamlining-the-delivery-and-decreasing-complexity-to-manage">IT WatchDog helped in many such situations </a>either with consultancy or with taking care of the whole external development process. It depends on the client whether we will install the entire cycle of managed service or <a href="https://www.itwd.com/plug-in-team-for-stanwood">provide a plug-in team</a> for strengthening the existing core one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e19259b54ca3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ryan-sinha-for-itwd-blog/how-to-communicate-with-a-remote-team-to-minimize-the-fails-e19259b54ca3">How to Communicate With a Remote Team to Minimize the Fails</a> was originally published in <a href="https://medium.com/ryan-sinha-for-itwd-blog">Ryan Sinha for ITWD Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is It Reasonable for Startups to Do Their Software Development In-House?]]></title>
            <link>https://medium.com/ryan-sinha-for-itwd-blog/is-it-reasonable-for-startups-to-do-their-software-development-in-house-f2d83c020ac1?source=rss----dd869b18079d---4</link>
            <guid isPermaLink="false">https://medium.com/p/f2d83c020ac1</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[IT WatchDog Inc]]></dc:creator>
            <pubDate>Fri, 30 Aug 2019 17:18:58 GMT</pubDate>
            <atom:updated>2019-08-30T17:58:30.739Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gX2FpPRkhSnKbfbVsm3dQA.jpeg" /></figure><p>We at <a href="https://itwd.com/">IT WatchDog</a> love startups as they request the most sophisticated challenges for our managed service teams. The things that we discuss first are not the technologies, architecture, or project schedule. The number one point we investigate with founders is the value chain and cost management. Saying it in other words — it is the Hamlet-style question: “To be or not to be? To outsource or not to outsource?”. That is the question, so let’s dive into it.</p><h3>External Development Is not for Everyone</h3><p>First thing you may expect from me as a CEO of a managed service IT company is my pushing from in-house development to an external one. If someone sees a CEO giving advice, one always expects hidden sales. However, this time you’re mistaken. The first thing we do, we try to persuade clients from going to outsourcing or managed service development. If their business model supports in-house product cultivation or their resources are scarce — it is better to postpone this decision for a year or two.</p><p>Yes, your eyes did not mislead you. I said about external development as to be more expensive. I will render it in detail shortly. First, I will cover the whole picture of value creation in a startup. At the end of this article, we will come to the answer to the main question — is it reasonable to develop in-house.</p><h3>The Primary Focus of a Startup</h3><p>So what value does your startup provide? Is it code writing of an app or a cloud service? If so, you are the software house or development unit of a huge corporation. It is wrong to call yourself a startup if your primary objective is to produce a ton of code and to measure its quality. Are you creating some change for the customer? Some “before and after” effect? Then probably you are a startup with a business model to solve some problem.</p><p>What problem to solve? Which business model to use? Why do customers evaluate a deal to be a good or unfair one? All these questions are the orienting points for startup founders. Such answers lead to much sought-after product-market fit — and this is something in what your team is making the highest value. So this function needs to be always (always!) inside the company.</p><h3>Main Focus Keeper</h3><p>What else should always stay in-house? The function to balance development with limited resources — i.e., to designate the tasks priorities and quality of product iterations. In Agile project management, the Product Owner plays this vital role. He needs to stay inside your company. Never agree on pledges of IT outsourcers that promise that they will do your ideas in full cycle.</p><p>If someone persuades you to give the product ownership function to the vendor — he tries to steal your money. PO takes the hard decisions on what is ‘minimal’ and ‘viable’ inside the MVP formula. The external product owner will use this power to extend the budget spent.</p><h3>When Is In-house Development Reasonable?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AIZghVT1U8eI1eVJOAvYNA.png" /></figure><p>Now we studied that a startup team creates its primary value in the field (customer development, strategic marketing, sales), while the execution of coding is easily externalized. Let us assume that you managed the control of the project budget and flow. What could be the reasons to make the final decision to do your software development in-house?</p><ol><li><strong>You are on the seed stage / your resources are scarce.</strong></li></ol><p>We finally got to the point raised in the beginning. External development is always more expensive than zero. Do your IT product development by the hands of founder or founders, and you will save your capital. Many icons of the IT industry did so, including Facebook, Microsoft, Apple.</p><p>If access to venture capital is not your strongest point — focus on hunting for co-founding CTO. Persuade him to leave his job, and you will get your MVP quickly. Can’t you find a CTO? Then check if your startup is worth doing when there are no believers even in exchange for priceless equity.</p><p><strong>2. You need to launch a different concept of prototype each few days.</strong></p><p>In the early stages of a business model, the founders do many experiments. Google Ventures even created their framework called Design Sprint for streamlining such work. If you need numerous prototypes, then this is more research than development. Do it with your own hands, do it in-house. Otherwise, you will spend more time on explaining to external people than they need to do for a new idea.</p><p><strong>3. You are on the limited market or have the monopoly.</strong></p><p>We rarely face the markets with the improbable entrance of competitors, but such situations occur. If you are lucky then really you do not need to move for external development. You can swallow the whole piece and only you to decide what speed to do it with.</p><p><strong>4. If you do not use some internal expertise — you will lose it.</strong></p><p>In the Japanese philosophy of Lean (later transformed to Lean startup methodology), one of the most crying wastes is an underutilization of human capital. If your co-founders and team are IT developers, you may lose them if used for marketing and sales only. Then consider keeping in-house development for fulfilling their inner demand to benefit for your product.</p><h3>When Is In-house Development not Reasonable?</h3><p>You see that all clauses to go for in-house development are rather rare. All other situations do open the potential for boosting your growth with external development. Let’s analyze all the reasons:</p><ol><li><strong>You strive for shortening time-to-market.</strong></li></ol><p>It is not a secret that the open market can attract potential competitors. With time more players will divide the limited number of deals. Your startup can maximize revenue if it gains the loyalty of more customers. So entering the market as early as you can is the matter of startup success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ve9bGh22RdKXQIkosDhJFg.png" /></figure><p><strong>2. Your growth outpace the potential to hire.</strong></p><p>When you set your business model and gained your customers rapidly, you start thinking in another way. You have proven to be a successful visionary, and now it is time to show excellence in execution. Your reputation on the market depends on how you satisfy the expectations. Whether it is scaling the product or developing a new feature — you need to add an external plug-in team as soon a possible. You can’t miss your time for the adaptation of internal newbies or work with standalone freelancers. All you need now is a whole team on their peak of productivity.</p><p><strong>3. You measure your success by business metrics.</strong></p><p>Sometimes founders like their processes and want to be involved deeply in doing the job. Such startups become traditional businesses that do not scale. So you may use their example and measure the success by the percentage of processes your people personally fulfill. Also, you may measure your success by business metrics (i.e., the number of customers you served, the revenue). Doing so, you become to be interested in getting higher business traction for fewer resources.</p><p>External development gives you more chances for it because of higher productivity. IT vendors build a unique R&amp;D atmosphere and management structure. They can afford to attract more narrow specialists and provide their developers with a whole infrastructure to be happy and progress professionally. It is almost impossible to get the same conditions in-house, so you need to compensate for it with salary and equity.</p><p><strong>4. You have more significant challenges for the upcoming period.</strong></p><p>When the founders leave behind the construction of the first iterations of the product, they step into the next challenge. It may be the battle for getting your market share, attracting investors for going to the next round, or going to IPO. All this needs the highest engagement of founders and top people, so it is wise to free them from daily operations with in-house development.</p><p>So think again what is reflecting better your priorities — the in-house or external development. If the last then look towards managed service. This business model gives much more value to the customer than IT outsourcing. We at <a href="https://itwd.com/">IT WatchDog</a> are always happy to help with our consultancy, to provide an external plug-in team or to develop your product from a scrap.</p><p>Also, remember the main point: always keep your key business decisions in-house.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2d83c020ac1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ryan-sinha-for-itwd-blog/is-it-reasonable-for-startups-to-do-their-software-development-in-house-f2d83c020ac1">Is It Reasonable for Startups to Do Their Software Development In-House?</a> was originally published in <a href="https://medium.com/ryan-sinha-for-itwd-blog">Ryan Sinha for ITWD Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hidden Сosts of Development and How to Manage Them]]></title>
            <link>https://medium.com/ryan-sinha-for-itwd-blog/hidden-%D1%81osts-of-development-and-how-to-manage-them-baf30ebea204?source=rss----dd869b18079d---4</link>
            <guid isPermaLink="false">https://medium.com/p/baf30ebea204</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[outsourcing]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[IT WatchDog Inc]]></dc:creator>
            <pubDate>Fri, 23 Aug 2019 17:05:19 GMT</pubDate>
            <atom:updated>2019-08-26T12:52:26.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9pQ3QAdGkSx7rAiyBfypg.png" /></figure><p>Each time I speak for a startup audience on different conferences and meetups — I receive a pretty much similar bunch of questions. Today I start a new practice of publishing my Medium blog to share my expertise with colleagues that need our consultancy.</p><p>The most frequent question is on the hidden costs of IT development. We at <a href="https://itwd.com/">IT Watchdog</a> love this question as we specialize in helping with cost management. You may be surprised or not, but the law #1 says the following:</p><blockquote>There is no hidden costs of development, there are bad planning and risky vendors.</blockquote><p>Let’s research both points thoroughly.</p><p><strong>A. Bad Planning</strong></p><p>As the proverb says: “All project managers know: the first 90% of the project is not as scary as the second 90% of it”. However, if speaking seriously, planning is usually the weakest point of most of the companies making their IT development projects.</p><p>Like any skill, it may be trained to become better. Here are some tips:</p><ol><li>Check if you deal with an Agile/Scrum-trained team and the team-lead has expertise in project ownership. The era of waterfall project development is left far behind. Thus 200 pages of detailed briefing on your project do not leave any illusion that the product will be on time and budget. You may save by turning away from such a document and spend this time on prioritizing product features and giving feedback.</li><li>Prepare a detailed list of functionality you plan to get. It is not feasible to predict all possible questions of developers by writing ahead of all details. However, it is possible to give the feeling of the project scope by explaining what business purpose product needs to get fulfilled.</li><li>Use product backlog to prioritize. Work closely with your team to explain what level of functionality is just enough to stop spending resources.</li><li>Insist on putting into practice the BurnUp Chart from the first days of the project. Keep an eye on its progress. Ask your team to make a rough estimation ahead and update it frequently.</li></ol><p>Planning is not the core business of you as an IT development client. Put your focus on your customers and business functions, and empower your development team to do their best in planning consultancy. If the stakes are high — engage the vendor with managed service excellence, and professionals will care about your doubts on planning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wWO84v-gcGBLkFG_8zjvXA.png" /><figcaption>Tips for preventing hidden costs</figcaption></figure><p><strong>B. Risky Vendors</strong></p><p>Each time you start a new development project, you choose the development team. Let’s see what the options are:</p><ol><li>In-house developers</li></ol><p>You come with an idea and face some response from in-house developers. You are lucky if you meet enthusiasm, but more often there is the space for internal politics. It will influence the way the project will go on each crossroad. Moreover, it will influence your position in your company.</p><p>Both you and the development chief have the same big boss. During the course of the project (always!) the product owner needs to take the hard decision that touches developers. Be careful, as later results of these decisions may become the reasons for the eternal struggle for resources. Hopefully, your side wins, but think about the situation when the big boss will take the reasons of your opponent — you will have consequences for your career.</p><p>Moreover, even if your corporate spirit is strong and supportive, your hidden costs may lie inside the process. IT development is an intensive production process, which needs a particular culture. Usually, it differs from the one inside the business departments, so the majority of companies separate their R&amp;D units by opening them in other locations. Think about cultivating the creative atmosphere, managing the unpredictable thinking process, recognizing quality leaders, accelerating developers through their knowledge path. All these things need to keep in mind the innovative nature of this process — so leadership style needs to be appropriate.</p><p>Is it already implemented successfully in your company? Alternatively, is it wise to delegate the development to focus better on clients and business strategy? You choose from your business perspective.</p><p>2. Offshore outsourcing</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*FE4iT5lBkezjF_PnQ9IKMQ.jpeg" /><figcaption>Everybody wants to outsource</figcaption></figure><p>Let’s dive into another common choice — to outsource your development towards vendors in other geographies. This choice promises the highest economy but eats your budget with many unpredictable costs.</p><p>Let’s check all of them:</p><ul><li>Delays due to a small window of communications (your team sleeps when you come with your questions)</li><li>Cultural distance decreases understanding — so you pay for code that was written by lack of translation. So you pay for additional efforts from each side to understand what another one means. The national mentality is a big thing really, so each project has at least one such episode.</li><li>“Slave” VS “Creator” mode. When you deal with a professional, he does not take all your requests as orders to be done. He tries to bring you to the purpose you are willing to achieve. If the task from you will bring the development to the wrong road — the professional will give you the advice to think twice. Just imagine how much money you will spend if developers will switch on ‘monkey coder’ mode and will develop anything without critical re-evaluation.</li><li>Travel. Big issue or a significant turn in concept — you will need to travel to the project team to speak seeing people’s eyes.</li></ul><p>All said touches the points of diligent vendors. Because our practice shows that you may prevent overbilling only in one case — if your manager works on-site with developers. Otherwise, be prepared that your real work is less for 30–40% than you paid.</p><p>3. Nearshore outsourcing</p><p>Nowadays you may find many advertisements on nearshore development. They may promise that talented developers from Mexico or nearby countries will save your development costs by rates a slightly higher, than on the other side of the globe.</p><p>However, is it so indeed? Look at the main pain points above. The geography accounts only for travel and time zones issues. All other aspects continue to work as a ticking bomb of your costs.</p><p>4. The US managed service</p><p>The ultimate solution I found during the 20+ years of my experience is to work with vendors that satisfy the following criteria:</p><ul><li>Have their managers in the same room with the development team</li><li>Provide development as managed service (i.e., value for the client is created not only by developers but by managers as well)</li><li>It is located in the US and could be easily met by a person even weekly. All planning and feedback sessions move much more productively if conducted face to face.</li></ul><p>The development process of such quality usually comes at a price. However, the good news is that <a href="https://itwd.com/">IT Watchdog</a> found a model to keep both elements of cost control: <strong>the US presence and managing the development teams all over the world. </strong>Such balance brings the high quality and lack of hidden costs to the business model with prices close to the offshore competitors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=baf30ebea204" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ryan-sinha-for-itwd-blog/hidden-%D1%81osts-of-development-and-how-to-manage-them-baf30ebea204">Hidden Сosts of Development and How to Manage Them</a> was originally published in <a href="https://medium.com/ryan-sinha-for-itwd-blog">Ryan Sinha for ITWD Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>