<?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 Amit Gupta on Medium]]></title>
        <description><![CDATA[Stories by Amit Gupta on Medium]]></description>
        <link>https://medium.com/@gupta25?source=rss-fe055ef952ac------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*UIcKe3lxfYaUmIDKVXYP5A.jpeg</url>
            <title>Stories by Amit Gupta on Medium</title>
            <link>https://medium.com/@gupta25?source=rss-fe055ef952ac------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:17:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gupta25/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[Leadership vs. Management: Unraveling the Distinctive Threads]]></title>
            <link>https://medium.com/@gupta25/leadership-vs-management-unraveling-the-distinctive-threads-a98022dc3c4f?source=rss-fe055ef952ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/a98022dc3c4f</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[leadership-training]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[Amit Gupta]]></dc:creator>
            <pubDate>Sat, 05 Aug 2023 19:08:31 GMT</pubDate>
            <atom:updated>2023-08-05T19:11:01.517Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oKL3do20MeAN0KCJv43qyA.jpeg" /><figcaption>Image from Unsplash</figcaption></figure><p>After a long time, I am resuming writing. With this article I am starting a series on Leadership.</p><p>So first thing first, What’s the main difference between a Leader and a Manager?</p><p><strong>Introduction</strong></p><p>In the dynamic world of business and organizational settings, two crucial roles hold the reins of success and growth: leaders and managers. Though often used interchangeably, leadership and management are distinct concepts that contribute differently to the attainment of objectives. Understanding the fundamental differences between these roles is vital for fostering effective teamwork, achieving organizational goals, and nurturing a thriving workplace culture. This article delves into the core dissimilarities between leadership and management, shedding light on their unique qualities and the role they play in an organization’s triumph.</p><p><strong>1. The Nature of Influence</strong></p><p>At its core, leadership is all about influence. Leaders inspire and motivate others through their vision, passion, and empathy. Their impact extends beyond the boundaries of authority, as they gain followership based on respect and admiration. Leadership encourages individuals to follow a shared vision, fostering a sense of purpose and commitment.</p><p>On the other hand, management primarily deals with control and coordination. Managers focus on executing tasks, organizing resources, and ensuring that day-to-day operations run smoothly. Their authority comes from their position within the organizational hierarchy, and they have the power to make decisions that align with the company’s goals.</p><p><strong>2. Focus on People vs. Processes</strong></p><p>Leadership centers on people. Effective leaders understand the strengths and weaknesses of their team members, nurturing their talents and empowering them to reach their full potential. They prioritize building relationships and creating a supportive environment where individuals can thrive.</p><p>Management, on the contrary, emphasizes processes and systems. Managers focus on efficiency, ensuring that tasks are completed on time and within budget. They coordinate resources, allocate responsibilities, and implement strategies to meet predetermined objectives.</p><p><strong>3. Visionary Outlook vs. Operational Expertise</strong></p><p>Leaders are visionaries. They possess a forward-thinking mindset, anticipating future trends and challenges. Leaders define the direction an organization should take and guide their teams toward that destination. They are not afraid to take calculated risks and challenge the status quo to drive progress.</p><p>Managers excel in operational expertise. They are masters of planning, organizing, and coordinating the intricacies of day-to-day operations. Managers work within the framework established by leaders, ensuring that resources are optimally utilized, and goals are achieved effectively and efficiently.</p><p><strong>4. Risk-Taking vs. Risk Management</strong></p><p>Leadership inherently involves risk-taking. Leaders are willing to explore uncharted territory and embrace uncertainty to achieve greatness. They encourage innovation and support calculated risk-taking by their teams, knowing that failure is sometimes a stepping stone to success.</p><p>Management, on the other hand, is more focused on risk management. Managers aim to minimize potential risks to ensure the stability and continuity of operations. They implement risk mitigation strategies and adhere to established procedures to safeguard the organization’s interests.</p><p><strong>5. Long-term Vision vs. Short-term Objectives</strong></p><p>Leaders adopt a long-term perspective. They are responsible for developing a clear and compelling vision that aligns with the organization’s mission. Leaders strive to create a legacy that extends beyond their tenure, leaving a lasting impact on the company’s culture and success.</p><p>Conversely, management operates within the framework of short-term objectives. They work diligently to achieve immediate goals and meet deadlines, maintaining stability and productivity in the present.</p><p><strong>Traits of a Leader</strong></p><p>1. Visionary: A great leader has a clear and compelling vision for the future. They can articulate this vision to their team and inspire others to work towards its realization.</p><p>2. Integrity: Leaders are honest, ethical, and lead by example. They act with integrity and earn the trust and respect of their team members.</p><p>3. Empathy: Effective leaders understand and empathize with the needs, concerns, and feelings of their team members. They are approachable and supportive, creating a positive work environment.</p><p>4. Decisiveness: Leaders must make tough decisions in a timely manner. They gather relevant information, weigh the options, and act decisively when required.</p><p>5. Communication Skills: Excellent leaders are great communicators. They can convey their ideas clearly and listen actively to others, fostering open and transparent communication within the team.</p><p>6. Emotional Intelligence: Leaders with high emotional intelligence can understand and manage their emotions and those of others. They use emotional awareness to handle interpersonal relationships effectively.</p><p>7. Adaptability: Leaders must be flexible and adaptable in a rapidly changing world. They embrace innovation and are open to new ideas and approaches.</p><p>8. Accountability: A strong leader takes responsibility for their actions and the outcomes of their decisions. They hold themselves and their team accountable for their performance.</p><p>9. Empowerment: Effective leaders empower their team members to take ownership of their work and contribute their best efforts. They delegate responsibilities and trust their team’s capabilities.</p><p>10. Resilience: Leadership often comes with challenges and setbacks. Resilient leaders bounce back from adversity, learn from failures, and maintain a positive outlook.</p><p><strong>Traits of a Manager</strong></p><p>1. Organized: Effective managers are highly organized and can manage multiple tasks, deadlines, and priorities efficiently.</p><p>2. Planning and Execution: Managers excel at strategic planning, setting objectives, and executing plans to achieve organizational goals.</p><p>3. Problem-Solving: Managers are skilled problem solvers. They analyze issues, identify root causes, and implement effective solutions.</p><p>4. Delegation: An excellent manager knows how to delegate tasks and responsibilities based on individual strengths and expertise within the team.</p><p>5. Time Management: Managers can prioritize their own and their team’s time effectively, ensuring tasks are completed efficiently.</p><p>6. Team Building: Managers are adept at building and nurturing a cohesive and high-performing team. They foster collaboration and create a sense of unity among team members.</p><p>7. Coaching and Development: Great managers invest in the growth and development of their team members. They provide constructive feedback and support their employees’ professional growth.</p><p>8. Budgeting and Resource Management: Managers handle budgets and resources responsibly, ensuring that they are allocated optimally for the organization’s benefit.</p><p>9. Conflict Resolution: Effective managers address conflicts within the team promptly and constructively, promoting a harmonious work environment.</p><p>10. Results-Oriented: Managers are focused on achieving results and meeting targets. They set clear expectations and motivate their team to deliver their best performance.</p><p><strong>Conclusion</strong></p><p>In conclusion, leadership and management are two distinct yet complementary roles within an organization. While leadership focuses on inspiring and guiding people towards a shared vision, management concentrates on efficient resource allocation and operational execution. Leaders paint the picture of the future and motivate their teams to achieve greatness, while managers ensure that the day-to-day operations run seamlessly. The traits of an excellent leader and an exceptional manager often overlap in certain areas. Both roles require strong communication, integrity, and the ability to motivate and inspire others. For an organization to thrive, it must strike a balance between effective leadership and efficient management, allowing each role to contribute its unique strengths and qualities. When harnessed harmoniously, leadership and management become powerful forces, propelling organizations toward unprecedented success.</p><p>PS: The views expressed in this article are solely mine and do not necessarily reflect the views of my organization or any of my previous employers. The content presented here is based on the my personal opinions and experiences.</p><p>The information provided in this article is for general informational purposes only. While I’ve tried to strives to ensure the accuracy of the content, they make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, or suitability of the information.</p><p>Any reliance you place on the information presented in this article is strictly at your own risk. The author will not be liable for any losses, injuries, or damages from the use of this information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a98022dc3c4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essence of Agile Software Development]]></title>
            <link>https://medium.com/vmware-end-user-computing/essence-of-agile-software-development-39ff109131bb?source=rss-fe055ef952ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/39ff109131bb</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Amit Gupta]]></dc:creator>
            <pubDate>Tue, 23 Feb 2021 21:17:48 GMT</pubDate>
            <atom:updated>2021-02-23T21:17:48.996Z</atom:updated>
            <content:encoded><![CDATA[<h3>The essence of Agile Software Development</h3><p>Doing Agile Vs Being Agile</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*srPxKzz1oqlXP0j8V09-9A.jpeg" /></figure><p>Large or small, software development organizations are embracing an agile-based model to improve quality, increase productivity, and enable faster releases to market. But what is agile development?</p><p>The agile software development methodology is focused on continuous planning, development, testing, improvements, learning, early feedback, and early delivery with enhanced collaborations. The Agile software development methodology has four core values:</p><p>1. Faster responses to changes over long-term planning<br>2. Individual/team interactions over processes/tools<br>3. Customer collaboration over contract negotiation<br>4. Working software over comprehensive documentation</p><p>Most companies have employed agile development methodology in some form or the other. Having stand-ups, creating a backlog, user stories, having sprint cycles, retrospectives and iterations are part of agile methodologies, but is it really agile?</p><p>In this article, we will discuss what it means to be truly agile and how can you make changes in an organization to be truly agile.</p><p>Attending agile training and learning about scrum, sprint cycles, backlogs, stories, and performing Agile ceremonies does not bring an agile mindset and an Agile culture. All these steps are useful and improve productivity, quality, visibility, and coordination but are not sufficient to truly be agile. This is a good beginning for the agile journey.</p><p>On the other hand, being agile is about your behavior and goals. Being agile means having a dynamic team, as well as a dynamic organization that’s capable of responding to changes quickly.</p><p>Being Agile is about who we are; it is associated with an organization’s culture, leadership, and overall mindset. It is about how we perceive ourselves, how we relate to others, how we behave, and what we value. Being Agile means asking the question “Is everyone in the team in the same page?” Does everyone on the team know what they are doing and why? Are your teams self-managed and self-motivated?</p><p>Let’s summarize the difference between Doing Agile vs Being Agile</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*FvsN9aFI1wijML23PAlHYw.png" /><figcaption>Differences between Being Agile vs Doing Agile</figcaption></figure><p>There are 12 principles of the <a href="https://agilemanifesto.org/">Agile Manifesto</a>, but as we’ve previously discussed, there is a big difference between doing and being agile. How do you take those 12 principles and make them practices, to truly be agile? Below are some points to consider to convert these principles into practice and achieve the true potential of Agile.</p><p>1. The first principle in the Agile Manifesto is that teams should aggressively pursue early and continuous delivery of working, valuable software to satisfy the customer. For commitment the team takes on, they should ask themselves the following questions to make this priority real:</p><ul><li>Does it produce value for my customer?</li><li>Can we achieve the same results in a different and faster way and what are our alternatives?</li><li>How can it be broken down to deliver value as fast as possible?</li></ul><p>These can be incorporated during the backlog grooming sessions.</p><p>2. Welcome changing requirements - even late in the development process — is the second principle. To achieve this goal of the Agile Manifesto, a team needs to develop a curiosity mindset. The right mindset comes from doing the following:</p><ul><li>Creating value for each change should be questioned. Ask the question with all stakeholders during various agile practices about the value of the change and the impact it will make.</li><li>Adopt or remove tasks from an existing plan as required to create the maximum value.</li><li>Release the software as soon as possible with the requested changes asked by the customer.</li><li>Don’t plan for the long term, plan only for the change and as much as required to make the change.</li></ul><p>3. The frequent delivery of well-performing software is your team’s goal, and while that may seem obvious, it is surprising how easy it is to make delivery secondary to other aspects of the Agile process. Keep the following in mind to focus on frequent releases:</p><ul><li>Set regular delivery dates most suited to the product with an incremental value stream.</li><li>Use automation for repetitive tasks.</li><li>Shorten the delivery cycle to maximize the value each iteration delivers.</li></ul><p>4. The fourth principle of the Agile Manifesto is that business people and developers should work together closely, on a daily basis. To achieve this, most teams have daily stand-ups that include all stakeholders. During these stand-up meetings, ensure all stakeholders discuss the achievement of the day, any roadblocks, and what team members will be doing. If the team is distributed, ensure everyone can participate through video calls and it is at a time that is suitable to all team members.</p><p>5. For the fifth principle, build projects around motivated individuals. Hire individuals who are self-motivated and gauge their attitude instead of only technical skills. For an efficient team, leaders need to take care of the followings:</p><ul><li>Define a goal, create KPIs to measure those goals without prescribing each step to achieve it.</li><li>Create an environment of psychological safety where failures are accepted and continuous learning is a part of the work culture.</li><li>Identify and appoint the right people with the right skills to the right roles.</li><li>Trust team members to do their job without micromanaging them.</li><li>Ensure leaders are catalysts that remove obstacles and do not become roadblocks.</li></ul><p>6.The sixth principle is to have face-to-face conversations. Why is it so important to have a conversation? A face-to-face conversation is natural for humans; it emphasizes the importance of collaboration and helps with bonding and the development of relationships within the team. However, in a time of a pandemic, it is not possible to have this kind of conversation. Fortunately, most have access to video conferences and/or video calls in order to have a face-to-face discussion. To foster the culture of conversation, one can do the following:</p><ul><li>Have in-person meetings as much as possible and co-locate the entire team.</li><li>If not possible due to the nature of the distributed team, ensure videos are turned on and the team has video calls.</li><li>Reduce the number of meetings, so as to not overwhelm the engineers and enable them to remain focused on core deliverables.</li><li>Avoid writing long emails and use instant messaging to have short and efficient conversations.</li></ul><p>7.The seventh principle says working software is the primary measure of progress. So, what do we mean by “working software”? It is a piece of function/module that customers can use. This principle goes along with the first principle.</p><ul><li>Ask, does it matter to the customer what we are going to deliver?</li><li>Can we deliver a minimum viable product in shorter, incremental cycles rather than a full-featured release in a longer period?</li></ul><p>8. A sustainable development cadence is a key part of the Agile process. Engineers should find a pace they can consistently maintain. This is the Agile principle most often overlooked. Agile teams focused on really Doing Agile are often buried with work and trying to stretch to meet deadlines and deliver on time. This leads to burning out and is a major reason why teams fail at the Agile methodology. To adopt this in your organization, try the following suggestions:</p><ul><li>Ensure goals are realistic; make sure that things like time for breaks, meetings, Agile ceremonies, and necessary errands are all taken into consideration.</li><li>Ensure the team understands how to size a task and correctly estimate.</li><li>Ensure expectations of goals and acceptance are balanced by managers.</li><li>Ensure teams are given a platform and resources to continue to learn.</li><li>Ensure the team takes regular breaks and do what they love to do. The organization can foster the culture of letting employees do what they love to do for a given time on a regular basis.</li></ul><p>9.The ninth principle on the list, continuous attention to technical excellence and good design enhances agility. What should we do to adopt this principle to be agile?</p><ul><li>Have regular and iterative reviews on product design during storytelling sessions, grooming, or even dedicated design discussion sessions. Don’t forget to include testing as part of these discussions.</li><li>Develop software in smaller chunks but with solid designs.</li><li>Have higher standards and lean processes within teams.</li></ul><p>Having good design and technical excellence will lead to greater adaptability. It also reduces efforts later in support.</p><p>10. “Simplicity — the art of maximizing the amount of work not done — is essential” is the tenth principle in the Agile manifesto. What does it mean? Reduce waste, have simple and lean processes and deliver value.</p><ul><li>Ask yourself what process in the entire lifecycle is not required? What process can be simplified? What new process can help improve the productivity of your employees and increase the quality of the product, for example?</li><li>Ask as a team, what is working and not working in the team during retrospective sessions and make action items from the learnings.</li></ul><p>Work towards simplifying processes and development to reduce waste.</p><p>11.The eleventh principle is the best architectures, requirements, and designs emerge from self-organizing teams.</p><ul><li>Check if the team is autonomous and capable of acting fast, without any long bureaucratic processes.</li><li>Check if the team has all the required skills to develop software end to end. An ideal team should be capable of doing the end-to-end job by setting up all infrastructure, test environments, designing, and developing the software.</li><li>Check if the right people are at the right job with the right skills.</li><li>Check if they have access to resources to reach out for external help if needed. Create a platform that can allow them to find and access sources of help.</li><li>Check if the team is focused on output and not who does what.</li></ul><p>12. We are down to the last principle of the Agile manifesto which is “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly”. How can we adopt this principle in our work?</p><ul><li>Set up regular retrospective sessions to reflect on the team&#39;s performance. Did the team reach their sprint goals? During these sessions understand and note what were the challenges and successes the team enjoyed.</li><li>Retrospective sessions should not turn into finger-pointing meetings.</li><li>Take corrective action from the challenges faced while also making sure to celebrate successes.</li><li>Ensure the team is encouraged to take corrective action, provide feedback, and adjust to continue to improve. E.g. introduce the 360-feedback loop</li></ul><p>The goal with these Agile Manifesto principles is to develop a culture, a mindset in an organization, and an individual to truly harness the potential of Agile methodology.</p><h3>Conclusion</h3><p>Being Agile is not a destination, it is a journey. Here at VMware, we are on the path to be Being Agile, we are continuously learning, improving, and delivering value to our customers. If Agile is not working with your project or team takes a step back reflect, find gaps in the Agile transformation, and take corrective steps.</p><p>I would like to extend my gratitude to Karishma Babu for providing valuable inputs and feedback on this article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39ff109131bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vmware-end-user-computing/essence-of-agile-software-development-39ff109131bb">Essence of Agile Software Development</a> was originally published in <a href="https://medium.com/vmware-end-user-computing">VMware 360</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My DevOps Journey at VMware]]></title>
            <link>https://medium.com/vmware-end-user-computing/my-devops-journey-at-vmware-57da31e410e8?source=rss-fe055ef952ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/57da31e410e8</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Amit Gupta]]></dc:creator>
            <pubDate>Wed, 12 Aug 2020 16:24:18 GMT</pubDate>
            <atom:updated>2020-09-08T23:09:58.863Z</atom:updated>
            <content:encoded><![CDATA[<p>A glimpse into the impediments experienced while starting the DevOps transformation and how we solved them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*58s9Msa-m_qUrqGTHyK-8w.jpeg" /></figure><p>Most companies are going through a DevOps transformation these days to adopt faster releases, provide better quality, increase team’s flexibility, agility and get faster feedback. VMware’s mobile products are no different. We started our transformation two years ago with these same goals in mind. This post will list the obstacles faced on our journey, as well as the solutions that kept us moving forward.</p><p>While starting with DevOps goals in mind two years back, we had some initial ingredients available to us. We had an agile process in place (it is debatable how effective this process was), operations team in place, automation in place, tools and technologies available, but none of these were working as one engine. So, we started to make changes.</p><p><strong>Rejection</strong>: Uncertainty, fear, and doubt in adopting changes is in human nature and this creates an environment of rejection. One of the most difficult tasks was to convince the team to implement new changes, transformation, and drive towards cultural shift.</p><p>To solve this, we started with constant education, process changes, and asked teams to make these changes slowly. This process has helped teams to see the value in DevOps adoption. Additionally, we were lucky to have the support of our management team. Without their support and alignment, our DevOps change would have been impossible.</p><p><strong>Feature delivery</strong>: Another learning we experienced was feature delivery. Teams were under constant pressure to deliver new features with very little time in hand. They were focused on delivery of working code but were not responsible for quality. Quality was the responsibility of a separate quality engineering (QE) team. Developers were working day and night, delivering code over and above team’s capacity but QE were still finding lots of defects.</p><p>While making the adjustments in the team processes to adopt the changes, we did not want to make a big bang shift to disrupt the new feature releases which provide value to our customers.</p><p>So, what were our options? For the first step, we reduced the team’s velocity to only 50% capacity of their regular capacity, to ensure that the time needed for a higher quality focus was available to them. Second, we provided time for teams to re-approach and change the definition of “done”, we began to focus on root cause analysis, and focused on automation to avoid similar issues to reduce future issues.</p><p><strong>Technical Debt</strong>: Technical debt is part and parcel of software development. Most teams with legacy code have some kind of technical debt and we were no different. Most of our mobile products have some amount of technical debt.</p><p>Since we slowed down our velocity to 50% of our previous capacity, we had some breathing room to take smaller chunks of technical debt as a part of planning within a team’s given velocity. Deciding to reduce our feature velocity by half is a difficult decision for any team to make. We worked very closely with product management teams to prioritize tackling technical debt and engineering improvements along with new features to ensure the success of our products in the long run.</p><p><strong>Team Structure</strong>: When we started our DevOps transformation journey, QE teams operated independently of developers. It was the responsibility of quality engineers to test the product. But this arrangement does not fit well within the DevOps structure.</p><p>Management realized this problem and changed the team structure; QE teams were merged with development teams. Everyone was focused on delivering a quality product and quality was owned by everyone in the team. QE paired with developers, reported to same managers, and engaged in quality at the beginning as the design and development started. We created DevOps-style teams. DevOps-Style teams are full featured teams, able to build, test, have infrastructure skills, and manage services. If you are a large organization like VMware, you don’t need to create skills down to bare-metal for each team and can continue to have a platform team to serve for key infrastructure and common needs across multiple projects. However, ensure each team is enabled to manage applications and services by themselves.</p><p><strong>Skills &amp; Knowledge:</strong> It was easier said than done when management changed the structure of teams to make everyone responsible for product quality. There were gaps in skills and product knowledge. E.g. Developers did not know how to create test cases; The QE team was unaware about product code to contribute in code development.</p><p>To address this problem, we started to up skill and cross skill the team; To train QE on code development and developers to think about quality, test planning, test strategy, and overall adopting quality mindset. The purpose of this was not to have QE start developing code or developers start to test full time but get the skills needed to get more familiarity with the product and code. Additionally, we wanted to have the programming expertise to start building the tools and systems needed by their teams. Knowledge sharing, pair programming, cross team skill development eased the journey of transformation.</p><p><strong>Automation</strong>: DevOps is all about early feedback in the entire SDLC lifecycle and automation plays a very important role to provide early and consistent feedback. DevOps evolution cannot be achieved without automation. When we started, automation was in place, however, it was not used effectively. Test results were ignored due to lack of trust in automation scripts, and developers were not authoring any test scripts for automation (except for a few unit tests).</p><p>What did we do? We looked back at our automation test strategy. For shifting left, we chose the tools and technology close to what developers were using, so they could write test scripts in their favorite language, IDE, and tools. This helped us in a big way, slowly developers were able to start contributing to write test scripts and quality engineers started to fix product defects. It also provided us the stability in test automation. Better design and architecture of our test frameworks made it possible that each team member was able to contribute towards quality goals.</p><p><strong>Environment</strong>: One of the bottlenecks for automation was the availability of on-demand test environments, as Workspace ONE is a very complex product and has many inter-dependencies. It was not easy for individual teams to create such environments on demand for every test run.</p><p>This is where our infrastructure team stepped in and started to work on a project to provide on-demand test environments foreach team. The entire solution is based on a self-service portal and REST APIs; it was easy for all of us to adopt and use the APIs to integrate with automation and create test environments.</p><p><strong>Cross team collaboration</strong>: As stated, Workspace ONE is a very complex product with hundreds of inter-dependencies and divided into hundreds of modules. Teams often worked in silos and were focused on their own deliverables without any consideration to sharing best practices or creating reusable code. This was not an easy problem to fix and required a cultural mind shift.</p><p>What was the solution? We formed a small team of people to start coordination among teams, align release cycles, reuse code across teams, and improve code documentation. One of the examples was recreating our test framework which was based on micro-service architecture so each team can share their own code scripts to avoid duplication. A cross platform team was formed to decouple and write reusable code which could be used across product lines.</p><h3>Conclusion:</h3><p>We were able to make many positive changes by applying the above solutions. Last year when we looked back and evaluated results for our mobile SDK, we found that we were able to release at 50% faster on iOS and 25% faster on Android. Unplanned patches, minor releases reduced by 58% on iOS and 29% on Android. We reduced our escalation counts, improved productivity, increased collaboration across teams and quality along with many other intangible benefits.</p><p>Don’t be afraid of the changes. As <em>Martin Fowler</em> once said</p><blockquote>If you’re afraid to change something, it is clearly poorly designed.</blockquote><p>Start your DevOps transformation with proper planning, ensure management is on your side and all stakeholders understand it is a journey and not a destination. Be mindful with some of the above impediments during your expedition, but enjoy and continue to learn.</p><p>I would like to extend my gratitude to <a href="https://medium.com/u/f66cf019088">William Pinner</a> in co-authoring this article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57da31e410e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vmware-end-user-computing/my-devops-journey-at-vmware-57da31e410e8">My DevOps Journey at VMware</a> was originally published in <a href="https://medium.com/vmware-end-user-computing">VMware 360</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a TLS connection with Wiremock]]></title>
            <link>https://medium.com/vmware-end-user-computing/creating-a-tls-connection-with-wiremock-e275daf72549?source=rss-fe055ef952ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/e275daf72549</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[tls]]></category>
            <category><![CDATA[wiremock]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Amit Gupta]]></dc:creator>
            <pubDate>Mon, 15 Jun 2020 23:42:18 GMT</pubDate>
            <atom:updated>2020-06-15T23:42:18.351Z</atom:updated>
            <content:encoded><![CDATA[<p>How to test with a self-signed certificate on iOS 13</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOLsnflNkZKeNLbxoy5iZw.jpeg" /></figure><p>With iOS 13, Apple has introduced more restrictive guidelines for using self-signed certificates. So, how can we make iOS 13 applications work with your own server for testing? In this post, I will walk you through an example using Wiremock to generate a self-signed certificate, and setup a secure transport layer security (TLS) connection between your application and the Wiremock server.</p><p><strong>STEP 1:</strong> First define a .cnf file with all the required details to generate a self-signed certificate.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf6354d1769dec2bc3c3a4c54323c32f/href">https://medium.com/media/cf6354d1769dec2bc3c3a4c54323c32f/href</a></iframe><p><strong>STEP 2:</strong> Once you create the .cnf file, run the following command. This command will generate a new self signed certificate from .cnf file.</p><pre><em>openssl req -config selfsigned-CA.cnf -new -x509 -out mock-selfsigned-CA.crt</em></pre><p><strong>STEP 3:</strong> Check certificate for correctness by parsing the new certificate. This command will show you the .cnf information if generated successfully.</p><pre>openssl x509 -in mock-selfsigned-CA.crt -text -noout</pre><p>Drag and drop the generated crt file to the iOS Simulator or install it via Safari on real devices, continue the installation of certificate on the simulator or the device.</p><p><strong>STEP 4:</strong> Export the certificate and follow on screen instructions to provide passwords.</p><pre><em>openssl pkcs12 -export -name servercert -in mock-selfsigned-CA.crt -inkey wiremock-selfsigned-CA.key -out myp12keystore.p12</em></pre><p><strong>STEP 5</strong>: Import the certificate to java keystore.</p><pre>keytool -importkeystore -destkeystore mykeystore.jks -srckeystore myp12keystore.p12 -srcstoretype pkcs12 -alias servercert</pre><p>Finally, drag and drop the .crt file to the simulator</p><ul><li>Go to iOS settings / general / profiles and install the newly downloaded profile.</li><li>Go to settings / general / about / scroll down to “certificate trust settings” and enable your newly certificate.</li></ul><p><strong>NOTE</strong>: At this point, if you would like to use the certificate with your own server instead of Wiremock, go ahead and update crt and key files in your server and skip STEP 6.</p><p><strong>STEP 6:</strong> Using the prepared keystore, start the Wiremock server</p><pre>java -jar wiremock-standalone-2.23.0.jar — https-port 9099 — https-keystore ./mykeystore.jks — keystore-password password</pre><p>Validate by launching the Safari browser on the simulator and accessing the local host at <a href="https://localhost:9099/">https://localhost:9099</a></p><p><strong>References:</strong></p><p><a href="http://javadoc.iaik.tugraz.at/iaik_jce/current/iaik/x509/extensions/ExtendedKeyUsage.html">http://javadoc.iaik.tugraz.at/iaik_jce/current/iaik/x509/extensions/ExtendedKeyUsage.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e275daf72549" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vmware-end-user-computing/creating-a-tls-connection-with-wiremock-e275daf72549">Creating a TLS connection with Wiremock</a> was originally published in <a href="https://medium.com/vmware-end-user-computing">VMware 360</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Log-grabber: How to get application logs while running XCUITest?]]></title>
            <link>https://medium.com/vmware-end-user-computing/log-grabber-how-to-get-application-logs-while-running-xcuitest-da068f5525dd?source=rss-fe055ef952ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/da068f5525dd</guid>
            <category><![CDATA[xcuitest]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Amit Gupta]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 19:24:25 GMT</pubDate>
            <atom:updated>2020-01-06T19:24:25.027Z</atom:updated>
            <content:encoded><![CDATA[<h3>Log-grabber: How to get iOS application logs while running XCUITest?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SdI0BRY7O2B24oJvHYR6Ug.jpeg" /></figure><p>XCUITest is a great tool to automate iOS application testing. Application UI tests run as a separate target with an additional proxy application installed on the device. Due to the iOS sandbox application architecture, it is hard for test code to get the access to the application container to retrieve the logs generated by the application.</p><p>So, what can we do to get the logs generated by the application? There could be two approaches</p><ol><li><strong>Using a log Server</strong>: In this approach, one can write lightweight log server or use any existing commercial log server available on the cloud to get and post messages from the application. Test code can then grab the log messages using REST APIs.</li><li><strong>Using a UI Element</strong>: This approach is based on creating a UI Element in the application under a conditional compiler flag and dump all required log messages into the element. Subsequently, these log messages can be retrieved and validated using XCUITests.</li></ol><p>There are certainly few advantages using a log server approach but I will discuss those in a follow-up post. In this article we are going to discuss about the second approach.</p><p>As we know, XCUITests can access the UI elements of the application under test. UI Elements act as a conduit between the test and the application. Now, by attaching a small (1x1 px) UI element in the application window, the application can start dumping all its logs statements and have it immediately accessible by the test process.</p><h3>Steps to follow</h3><h4>In the application</h4><ol><li>Add a UITextView element in the application’s UI Window so that UITextView is available across all screens of the application.</li><li>Add a class which will provide methods to append log statements in this UI Element.</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0a8b67489f995b7b77d3007c6d0ee6ad/href">https://medium.com/media/0a8b67489f995b7b77d3007c6d0ee6ad/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/15b2f58caef6bc206c21be6c5262ee39/href">https://medium.com/media/15b2f58caef6bc206c21be6c5262ee39/href</a></iframe><h4>In the XCUITests</h4><p>In XCUITest, we can get the UIElement, get the logs information and parse the information we would like to validate.</p><ol><li>Create validation methods to verify logs.</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1a19f49bfb48299edd83cbd8551dd870/href">https://medium.com/media/1a19f49bfb48299edd83cbd8551dd870/href</a></iframe><p>2. Extend XCUIApplication class to use the validation methods</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/411471cefed342ab5946ed46bf39b686/href">https://medium.com/media/411471cefed342ab5946ed46bf39b686/href</a></iframe><p>As we can see above, with very little code we can get application logs in XCUITests. You should declare all such code under a feature flag or #ifdef so logging is available only when required.</p><p>Why should we choose this approach?</p><p><strong>Advantages</strong>:</p><ol><li>Easy fast reliable</li><li>Works with simulator and real devices without any change in code or configuration.</li><li>No external dependencies.</li><li>No network connection required</li></ol><p><strong>Disadvantages</strong>:</p><ol><li>Platform dependent.</li><li>Needs additional code in application.</li><li>Logs will be lost if automation needs to kill the app.</li></ol><p>Full sample code is available at <a href="https://github.com/amitg25/loggrabber">Git Hub</a>.</p><p>Lookout for my upcoming post on Log-Server based approach. We will explore how can we build a small log-server and run locally as part of automation and GET/POST log messages from XCUITests.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da068f5525dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vmware-end-user-computing/log-grabber-how-to-get-application-logs-while-running-xcuitest-da068f5525dd">Log-grabber: How to get application logs while running XCUITest?</a> was originally published in <a href="https://medium.com/vmware-end-user-computing">VMware 360</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Docker for Android Developers]]></title>
            <link>https://medium.com/vmware-end-user-computing/docker-for-android-developers-40934818a8c8?source=rss-fe055ef952ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/40934818a8c8</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Amit Gupta]]></dc:creator>
            <pubDate>Mon, 18 Nov 2019 15:42:40 GMT</pubDate>
            <atom:updated>2019-11-18T15:42:40.248Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Beginners Guide</h4><h4>How to set up an Android build and test environment in just a few minutes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gIngIRVPlHjHASnBkjxP4w.jpeg" /></figure><p>As a mobile application developer that specializes on the Android platform for VMware’s End-User Computing team, it can sometimes be a challenge to manage all the dependencies, packages, versions. When a new employee joins the organization, it simply takes a great deal of time to understand, set up and build a test environment. Time becomes even more constrained, especially when it comes to preparing multiple machines for CI environments and then maintaining those environments.</p><p>For example, developers are concerned about maintaining:</p><ul><li>Android SDK</li><li>Java/Kotlin</li><li>Gradle</li><li>Git</li><li>Emulator and devices</li><li>Long wait time for builds in build pipeline</li><li>Reproducible build environments</li></ul><p>On the other hand, release or DevOps engineers might be more concerned about:</p><ul><li>Git</li><li>Bamboo/Jenkins</li><li>VM environments</li><li>Emulator and Devices</li><li>Keeping build pipelines functional</li></ul><p>So, how can Docker help address these issues to minimize feedback time, and increase stability?</p><h3>What is Docker and why use it for Android Application Development?</h3><p>Docker is an open source software platform for building applications based on containers — small and lightweight execution environments that make shared use of operating system kernel, but otherwise run in isolation from one another.</p><p>Docker can eliminate the need for build machine setup and maintenance. It helps speed up feedback time in both build and test phases of the application, reduces the build queue time and simplifies creating standard build and test environments.</p><p>Docker is based on client-server architecture. As you can see below, the Docker server is responsible for all the container actions. The Docker server receives commands from the Docker client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*FlFP0REH_b3Xr_6R4NmhLw.jpeg" /><figcaption>Fig 1: How does Docker work?</figcaption></figure><p>Containers are built from images, which are the basic building blocks of Docker. In this example, we are using an image from “mingc/android-build-box”. This image is built for Android SDK and is used as a template for creating a container. Each image is organized in a layered fashion. Every change in the image will be added as a layer on top of it. Using command docker pullyou can get an image from the public Docker Hub registry. But, if you decide to build your own Android SDK image then the docker buildcommand will create an image which can be pushed to the docker registry using docker push.</p><p>Docker Registry is a centralized repository of Docker images. The public-facing Docker image repository is called Docker Hub (<a href="https://hub.docker.com/">Docker Hub</a>). Your enterprise might also have a private registry in Docker Hub or internally. The Docker registry acts like Git for images, where you can build images from your development machine, commit and push to the Docker registry.</p><p>Containers are the execution environment for Docker. Containers are created from images. Starting with a base image, you can add more layers in an existing image to suit your needs. We will be building our own application on top of an existing Docker image.</p><p>Using the two steps below, you can start building your Android application using containers.</p><h3>STEP 1: Installations</h3><p>What do you need to start with Docker:</p><ul><li>Docker Desktop (Download <a href="https://www.docker.com/products/docker-desktop">HERE</a>)</li><li>A Sample Android app. (Bring your own, or use one from <a href="https://github.com/Automattic/simplenote-android">HERE</a>, This is a sample note application)</li></ul><h3>STEP 2: Building and Running</h3><p>There are many pre-existing Android SDK images on Docker Hub. For this exercise, we will be using the <a href="https://hub.docker.com/r/mingc/android-build-box">Android Build Box</a>. However, you can use any other existing Android SDK image from Docker Hub, or build your own image.</p><p>After installing Docker Desktop and navigating inside your project, run the following command in the terminal:</p><pre>docker run --rm -v `pwd`:/project mingc/android-build-box bash -c &#39;cd /project; ./gradlew build&#39;</pre><pre>docker run --rm -v `pwd`:/project mingc/android-build-box bash -c &#39;cd /project; ./gradlew test&#39;</pre><p>In this command, we are using mingc/android-build-box image, which will be downloaded from Docker Hub on the first command execution. This image contains all necessary dependencies, tools to build and test an Android application.</p><p>Finally, we can map our project to the container images, launch bash and execute two commands.</p><ol><li>cd /project to go to the project directory on the container</li><li>./gradlew test to start build and running tests of the application.</li></ol><p>NOTE: Android Build Box image does not contain Git or Gradle, but since all Android projects are built with Gradle Wrapper, Gradle will be downloaded at run time while building the application.</p><h3>Coming soon</h3><p>Look out for my upcoming posts, where I plan to cover more topics to help you run Android applications, build and test entirely on Docker, including:</p><ul><li>How to build your own Docker Android SDK image for your project</li><li>How to build and test android application in build pipeline using Docker</li><li>How to create Android Emulator and Device Lab using Docker and Run UI tests.</li></ul><h3>References:</h3><ul><li><a href="https://hub.docker.com/r/mingc/android-build-box">https://hub.docker.com/r/mingc/android-build-box</a></li><li><a href="https://opensource.com/resources/what-docker">https://opensource.com/resources/what-docker</a></li><li><a href="https://www.infoworld.com/article/3204171/what-is-docker-the-spark-for-the-container-revolution.html">https://www.infoworld.com/article/3204171/what-is-docker-the-spark-for-the-container-revolution.html</a></li><li><a href="https://github.com/Automattic/simplenote-android">https://github.com/Automattic/simplenote-android</a></li><li><a href="https://www.infoworld.com/article/3204171/what-is-docker-the-spark-for-the-container-revolution.html">Infoworld</a></li><li><a href="https://opensource.com/resources/what-docker">Opensource</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40934818a8c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vmware-end-user-computing/docker-for-android-developers-40934818a8c8">Docker for Android Developers</a> was originally published in <a href="https://medium.com/vmware-end-user-computing">VMware 360</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>