<?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 Himanshu Gahlot on Medium]]></title>
        <description><![CDATA[Stories by Himanshu Gahlot on Medium]]></description>
        <link>https://medium.com/@hgahlot?source=rss-7c93e2332fdf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CX-E8ak8e0nmCEkHBkKFhg.jpeg</url>
            <title>Stories by Himanshu Gahlot on Medium</title>
            <link>https://medium.com/@hgahlot?source=rss-7c93e2332fdf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:05:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hgahlot/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[Sturish Launches Two New Growth Tools for eCommerce Sellers]]></title>
            <link>https://blog.storepath.ai/sturish-launches-two-new-growth-tools-for-ecommerce-sellers-a05c04f3ffa3?source=rss-7c93e2332fdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/a05c04f3ffa3</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[amazon-fba]]></category>
            <category><![CDATA[walmart-seo]]></category>
            <category><![CDATA[sturish]]></category>
            <category><![CDATA[selling-on-amazon]]></category>
            <dc:creator><![CDATA[Himanshu Gahlot]]></dc:creator>
            <pubDate>Thu, 01 Apr 2021 21:57:14 GMT</pubDate>
            <atom:updated>2021-04-01T21:58:16.625Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*eRNXJ76nJW96qWCKKlYbag.png" /></figure><p>At <a href="http://www.sturish.com/">Sturish</a> we are making eCommerce easy and accessible for everyone. We make global sales seamless by using data driven tools to optimize how products are advertised and listed across marketplaces — and handle all associated shipping, logistics, taxes, and compliance. Customers use a single dashboard to easily and clearly access sales data and market insights.</p><p>Today, we are excited to share that we are launching two new tools to make it significantly easier for eCommerce sellers to optimize their product listings on both Amazon and Walmart.</p><p>They are:<br>1. The Sturish Keyword Research Tool<br>2. The Sturish Listing Validator Tool</p><p>The Sturish Keyword Research Tool takes a seed word and then gives the user a ranked list of the keywords to use when writing the product listing copy in order to improve products’ ranking and discoverability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YJCj5XIeY6TbSJ_MUU7gw.png" /><figcaption>Sturish’s Keyword Research Tool showing keyword suggestions for an input keyword</figcaption></figure><p>The Sturish Listing Validator Tool takes the live listing and assigns a quality score to the product copy and then recommends optimization opportunities to improve it on both Amazon and Walmart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cb6H8pn6Th5bwJ6H59_U3A.png" /><figcaption>Sturish’s Listing Validator Tool showing suggestions to optimize a product listing</figcaption></figure><p>These tools were built by our team of ex-Amazon engineers who understand the nuances of the Amazon search engine and how to best navigate and optimize for it.</p><h3>Get Started</h3><p>These tools are free and easy to use. Please go to <a href="http://www.sturish.com/">www.sturish.com</a> and click on the “Sign Up for Free” button.</p><p>Need help or have a question? We are at: <a href="/service/mailto:support@sturish.com">support@sturish.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a05c04f3ffa3" width="1" height="1" alt=""><hr><p><a href="https://blog.storepath.ai/sturish-launches-two-new-growth-tools-for-ecommerce-sellers-a05c04f3ffa3">Sturish Launches Two New Growth Tools for eCommerce Sellers</a> was originally published in <a href="https://blog.storepath.ai/">StorePath</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productive Meeting Etiquettes]]></title>
            <link>https://hgahlot.medium.com/productive-meeting-etiquettes-c282e250e22f?source=rss-7c93e2332fdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c282e250e22f</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Himanshu Gahlot]]></dc:creator>
            <pubDate>Fri, 24 Jul 2020 04:11:51 GMT</pubDate>
            <atom:updated>2020-07-25T14:47:23.883Z</atom:updated>
            <content:encoded><![CDATA[<h3>Follow These Etiquettes for Productive Meetings</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y8AMTOJn90quC_CK" /><figcaption>Photo by <a href="https://unsplash.com/@dylandgillis?utm_source=medium&amp;utm_medium=referral">Dylan Gillis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When it comes to scheduling meetings, I am a firm believer in <a href="http://www.paulgraham.com/makersschedule.html">Maker’s schedule vs Manager’s schedule</a>. In his essay, Paul Graham touches upon the topic of <em>optimizing the number of meetings.</em> In this article, I would like to talk about another related aspect of meetings, i.e. how to <em>optimize the meetings themselves</em> by establishing good meeting etiquettes.</p><p>I believe that the preferred way of communication should be asynchronous and meetings should be avoided as much as possible. A single 30 min meeting with 5 attendees takes up a combined total of 2.5 hours. However, most of the time, a similar discussion could happen by collaborating on a document asynchronously. If a discussion requires a meeting at all, it should be kept light and short. A meeting lasting more than an hour should be a rare occurrence, if at all. Following good meeting etiquettes would ensure that meetings are as efficient as possible. Here are a few things that could help in making meetings short and productive.</p><ol><li>The meeting organizer should ensure that the <strong>meeting invite has the right amount of information</strong> required for attendees to be productive. This includes a descriptive title (“Quick Sync” works only for informal meetings), explicitly marking attendees as required or optional (so attendees come prepared and in the right state of mind), including information about the conference call (ideally a URL link and not a meeting id, so attendees don’t have to figure out where to put the meeting id in), the meeting background/agenda/goal, and any other notes or resources that the attendees need access before attending the meeting. Ensure that all resources linked in the meeting invite have the right access permissions so attendees don’t give up after clicking the link once and then come unprepared to the meeting.</li><li>The meeting organizer should <strong>start the meeting on time</strong>. Attendees should feel free to cancel the meeting if the organizer doesn’t show up after 10 minutes into the meeting.</li><li>All <strong>attendees should show up on time</strong> so the meeting can end on time. Meetings should start within 3 minutes of the scheduled start time.</li><li>A <strong>note-taker</strong> should be assigned explicitly. Most of the time, the organizer becomes the note-taker but there is no rule around it. The note-taker should try to capture the main points of the discussion as well as the next steps with <strong>specific</strong> owners (more on this later).</li><li>The meeting organizer should be responsible for <strong>following the agenda of the meeting</strong>. They should also bring the meeting back on track if attendees get into tangential discussions. It is alright to say, “<em>Let’s take this discussion offline</em>”.</li><li>Each meeting should ideally <strong>end with the organizer summarizing the decisions and the next steps</strong>. Each next step or action item should have an explicit owner to ensure accountability. More often than not, action items remain undone because everyone agrees that they should happen but no individual is directly responsible for them (i.e. the <a href="https://medium.com/@mmamet/directly-responsible-individuals-f5009f465da4">concept of DRI</a>). E.g., a team may agree in a meeting that they need to improve communication with stakeholders but unless someone is assigned the responsibility to make it happen, most team members would not hold themselves accountable for it. <a href="https://en.wikipedia.org/wiki/Diffusion_of_responsibility">If everyone owns the task, no one owns the task</a>.</li><li>The <strong>notes from the meeting should either be published on a public forum (wiki or internal documents) or emailed to attendees post-meeting</strong>, so any unfinished discussion items can be followed-up offline and everyone has clarity about the next steps. Circulating meetings notes also helps those meeting participants who couldn’t attend the meeting in getting on the same page with everyone else.</li><li>If the meeting requires discussing a document, <strong>it’s best to allocate some time (e.g. 15 mins) at the beginning of the meeting to allow all attendees to read the document and provide feedback on the document itself</strong>. Post-reading, the organizer (or meeting leader) should address the most important feedback items (to use the time efficiently) and leave the rest for offline discussion. This ensures that all attendees are given a fair chance to understand the discussion topic as well as provide their feedback. This way the discussion is not biased based upon the loudest voice in the room.</li></ol><p>Keeping meetings short essentially means making them more efficient. This would only work when everyone is following the same basic meeting etiquettes. A single non-compliant person can easily derail meetings, making them inefficient and longer. We need to avoid this pitfall and ensure that everyone is aligned on the meeting etiquette.</p><p>Thanks for reading. I hope these tips help you out in organizing more productive meetings. Feedback is welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c282e250e22f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Light-Weight Scrum in JIRA]]></title>
            <link>https://medium.com/swlh/light-weight-scrum-in-jira-b077ce5eb2a9?source=rss-7c93e2332fdf------2</link>
            <guid isPermaLink="false">https://medium.com/p/b077ce5eb2a9</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[sprint]]></category>
            <dc:creator><![CDATA[Himanshu Gahlot]]></dc:creator>
            <pubDate>Wed, 22 Jul 2020 21:01:38 GMT</pubDate>
            <atom:updated>2020-07-24T07:06:45.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zE5f3Zi76yl74qBS" /><figcaption>Photo by <a href="https://unsplash.com/@gautamlakum?utm_source=medium&amp;utm_medium=referral">Gautam Lakum</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>During my tenure at Amazon, the teams I was leading used to follow a very effective scrum process. It was made possible by an internal tool called SIM, which was integrated with various other internal tools, enabling a seamless project management experience. When I joined Lambda School, one of my main tasks was to set up an effective project management process for my teams. We decided to go with scrum and I started figuring out a good way to set up JIRA similar to how I had been using SIM at Amazon to reap the benefits of my learnings. I started with a <em>light-weight</em> implementation of the scrum process to avoid a steep learning curve for the team. In this article, I will describe how my teams are using JIRA to conduct a light-weight scrum process which some of you may find useful. It is possible to manage projects in JIRA differently than what I have outlined here, including <a href="https://www.atlassian.com/agile/tutorials/how-to-do-scrum-with-jira-software">the official JIRA scrum guide</a>, but the process described here has worked well for our teams so far.</p><h3>JIRA Organization</h3><p>Issues in JIRA should be organized in a way that makes it easier for us to manage our incoming requests and eventually run scrum meetings smoothly. We used to have a single backlog for all of the Engineering teams containing 100s of tasks. Such a huge backlog is difficult to manage, so we divided our backlog into different focus areas (or teams) and each focus area was made responsible for managing their backlog.</p><h3>Representation of Teams</h3><p>One of the simplest <strong>representations of a team in JIRA is a JIRA Project. </strong>We used the <a href="https://confluence.atlassian.com/adminjiracloud/discover-jira-cloud-products-776636162.html">Classic Scrum project</a> with the “Scrum” template since we found it to be better in terms of organization than a NextGen project (e.g. Classic projects display all Epics in a left pane, making it easier to glance through their backlog in the right pane).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8yB8WGWq1zo6yA0XOTwrdQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*bpJt9RwXJmFU9js5AgPKsA.png" /><figcaption>A team is represented as a Classic JIRA project with the Scrum template</figcaption></figure><p>Within each project, different <strong>internal initiatives or projects were represented as Epics</strong>. We created 2 Epics for special purposes, viz., New Requests and Ad Hoc, and as many other Epics as we need for other well-defined projects. Here is a brief description of these Epics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pG5lvdimABE2LVxEOWYAZw.png" /><figcaption>List of Epics in a JIRA project (which corresponds to a team)</figcaption></figure><ul><li><strong>New Requests</strong>: This Epic served as the bucket for all new business requests filed by <em>anyone</em> across the company. These requests are groomed weekly and transferred to either the Ad Hoc Epic or one of the other project-related Epics.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDq1BWjIzsYEMjR9vIClZA.png" /><figcaption>The New Requests Epic with tasks that are yet to be groomed</figcaption></figure><ul><li><strong>Project-related Epics</strong>: For each well-defined project with a known deliverable, we created an Epic. Each project Epic tracked all the milestones and tasks for that project. Stories from these Epics are kept in a prioritized order in the backlog and the top ones are moved to the upcoming sprint weekly.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCjRl33Z41aC6Wniw9pPDg.png" /><figcaption>A project related Epic with all backlog items</figcaption></figure><ul><li><strong>Ad Hoc</strong>: This Epic contains all the orphan Stories which do not belong to any well-defined project Epic. This Epic is also meant for housing any high-priority ad-hoc requests that come in while a sprint is in progress. There is a good chance of this Epic becoming a dumping ground for the majority of our Stories, hence, we are quite disciplined in ensuring that we are adding only those Stories to this Epic which do not reasonably belong to one of the other projects (or are not bugs, in which case they will be prioritized through our oncall process).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eyvyzOF93pLKMSrClQ21RQ.png" /><figcaption>The Ad Hoc project with tasks injected mid-sprint and not belonging to any particular project</figcaption></figure><p><strong>Q. What qualifies as a well-defined project and warrants an Epic?<br></strong>It is usually futile to create an Epic for a project where the end is not in sight. These Epics lurk around in your JIRA Epic view forever without getting done. It is best to divide long-running projects into smaller manageable launches and create Epics for them to ensure that Epics are being closed. E.g. a project involving the launch of a new data model can be divided into (1) creating the new data model, and (2) migrating X service to use the new data model, and so on.</p><p><strong>Q. How to prioritize incoming bugs while the sprint is underway?</strong><br>Apart from a JIRA project to manage Sprints for teams, each team also has a JIRA project (<a href="https://confluence.atlassian.com/adminjiracloud/discover-jira-cloud-products-776636162.html">with Bug tracking template</a>) to house bugs and issues that need to be handled by the <a href="https://www.pagerduty.com/resources/learn/call-rotations-schedules/">oncall</a>. We call this project “Oncall”. This project is not part of the scrum process and does not have a Scrum or Kanban board. Any issue (bug) that needs immediate attention is filed as a Bug in the Oncall project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*5OuVvRXBzCfhTJyDI8mvSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UeZvrK5F4FKx74L9oLeuTg.png" /><figcaption>Our Oncall project is a Classic project in JIRA with a “Bug tracking” template</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1ByfYgDYU3bhu-RDS7Y9w.png" /><figcaption>The Oncall project has no board. It just has a list of bugs in the order of priority.</figcaption></figure><h3>Scrum Meetings</h3><p>For the scrum process to be successful, it has to be accompanied by the right set of meetings to enforce discipline. <strong>All of my teams have 1 week-long sprint because our priorities change very frequently and we need to move faster</strong>. All of our scrum related meetings are scheduled between the time window of 9 am<strong> to 2 pm PST / PDT</strong> since this is the only overlapping time window across various office locations in the US. We keep 2 stand-ups, 1 backlog grooming, and 1 sprint planning meeting (with sprint retrospective) per week. Here is how the meetings are scheduled on one of my teams:</p><p><strong>Tuesday</strong> 9 am — 9:15 am — Stand-up<br><strong>Thursday</strong> 9 am — 9:15 am — Stand-up<br><strong>Thursday</strong> 1 pm — 2 pm — Backlog grooming<br><strong>Friday</strong> 11 am — 12 pm — Sprint planning with a sprint retrospective</p><p>Here are the details of what we cover in each of these meetings.</p><h3>Stand-up</h3><p><strong>Attendees</strong></p><p>All team members, including the PM</p><p><strong>Agenda</strong></p><ol><li>Slack based daily update of sprint tasks.</li><li>Each member takes &lt; 2mins to talk about their assigned tasks, calls out blockers, and asks for help.</li><li>Call out risks to timelines.</li></ol><h3>Backlog Grooming</h3><p><strong>Attendees</strong></p><ol><li>Product Manager</li><li>Engineering Manager</li><li>Few Tech Leads (optional)</li></ol><p><strong>Agenda</strong></p><ol><li>Go through the incoming requests in the ‘New Requests’ Epic. Transfer tasks from this Epic to either another project Epic (including the Ad Hoc Epic), in the right position based upon its priority, or to the “Oncall” Project.</li><li>Ensure that the individual project Epics’ tasks are correctly ranked.</li><li>Note down any other high priority tasks that need to go into the next sprint.</li></ol><h3>Sprint Planning</h3><p><strong>Attendees</strong></p><ol><li>Product Manager (optional)</li><li>Engineering Manager</li><li>Engineers</li></ol><p><strong>Agenda</strong></p><ol><li>List down every team member and their bandwidth for the next sprint, in the number of days (e.g. available for 7 out of 8 days).</li><li>Assign 0 points to the oncall, since they will only work on bugs, which will not be assigned any points.</li><li>Create the next week’s sprint.</li><li>Closeout the previous sprint by moving incomplete tasks from the previous sprint to the next sprint and marking the remaining tasks as done.</li><li>Move tasks to the sprint, assigning the right tasks to the right engineer (reasonably) based upon their bandwidth, current project, and any other factors.</li><li>Finally, decide what deliverables from the recently concluded sprint are candidates for the sprint demo session.</li></ol><p><strong>Please note that since we follow a light-weight scrum process, we do not keep track of sprint velocity or estimate tasks using planning poker.</strong> We will introduce these aspects of scrum if we feel the need for them in the future.</p><h3>Sprint Retrospective</h3><p><strong>Attendees</strong></p><p>All participants of the ‘Sprint Planning’ meeting.</p><p><strong>Agenda</strong></p><ol><li>Use a retrospective tool (we use <a href="https://www.retrospect.team/">https://www.retrospect.team/</a>), to conduct sprint retrospective.</li><li>Write down “what went well”, “what can be improved”, and “action items”.</li><li>Have a healthy discussion on what was entered in the tool.</li></ol><h3>Conclusion</h3><p>I was able to figure out how to use JIRA to conduct scrum the same way I used to conduct scrum using Amazon’s internal tools. However, given the size and stage of my current company, I did not enforce a heavy-handed scrum process on the team. We have started light and will continue to tweak our process as we move along.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b077ce5eb2a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/light-weight-scrum-in-jira-b077ce5eb2a9">Light-Weight Scrum in JIRA</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>