<?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 Vaibhav Bansal on Medium]]></title>
        <description><![CDATA[Stories by Vaibhav Bansal on Medium]]></description>
        <link>https://medium.com/@vaibhav-bansal?source=rss-aa531df32176------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2Difu2DVTEJ-gyHvAHD-JA.jpeg</url>
            <title>Stories by Vaibhav Bansal on Medium</title>
            <link>https://medium.com/@vaibhav-bansal?source=rss-aa531df32176------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:11:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vaibhav-bansal/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[Baking pizzas, the agile way]]></title>
            <link>https://vaibhav-bansal.medium.com/baking-pizzas-the-agile-way-63937b3edc8e?source=rss-aa531df32176------2</link>
            <guid isPermaLink="false">https://medium.com/p/63937b3edc8e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[sprint]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Vaibhav Bansal]]></dc:creator>
            <pubDate>Wed, 03 Jul 2024 13:08:09 GMT</pubDate>
            <atom:updated>2026-02-06T08:59:45.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Manifesto for Agile Software Development" src="https://cdn-images-1.medium.com/max/943/1*QOHG-Babc1W0Fzzqco_rqQ.png" /></figure><blockquote><em>“Agile is an attitude, not a technique with boundaries. An attitude has no boundaries, so we wouldn’t ask ‘can I use agile here’, but rather ‘how would I act in the agile way here?’ or ‘how agile can we be, here?’” — Alistair Cockburn (One of the initiators and co-signer of the </em><a href="https://agilemanifesto.org/principles.html"><em>Agile Manifesto</em></a><em>)</em></blockquote><h3>Common Vocabulary 🗣️</h3><p>At <strong>Pizza Org</strong>, working in a cross-functional, agile team means different people working on different projects with different context. To work together successfully, we need a common vocabulary that conveys context keeping the scope of work intact.</p><figure><img alt="Walter White from Breaking Bad speaking “I’m the Danger” in different languages" src="https://cdn-images-1.medium.com/max/739/1*E9QtV0XlmWhmDEuh07ajNA.jpeg" /></figure><p>Below is the vocabulary we follow at <strong>Pizza Org</strong>.</p><ol><li><strong>Product</strong>: The macro, the whole pizza with the box. It is what we sell/pitch to the the end-user. For e.g., WhatsApp, or LinkedIn, etc.</li><li><strong>Module</strong>: Part of the product, a slice. Multiple slices together make the pizza. For e.g., For WhatsApp, modules would be Chats, Payments, Calls, Communities, User Profile, etc.</li><li><strong>Feature</strong>: Feature is a sub-part of the product, the layers of cheese, the base and the sauce, and the toppings on the slice. Features together make a module. For e.g., for Chats, features would be Texts, Media, Live location, Polls, Disappearing messages, Search, Export, etc.</li><li><strong>Story</strong>: Story is a recipe to bake delicious pizzas, a requirements break-down of the feature. Completing stories is how we complete features. For e.g., for Texts, the different stories would be Send text message, Receive text message, Preview Links, etc.</li><li><strong>Task</strong>: Tasks are all the things you will have to do to cook a recipe, this includes boiling water, preparing the dough, cutting the veggies, etc. For e.g., Send text message will have tasks like Encrypt message, Send message, Mark as delivered, etc.</li><li><strong>Sprint</strong>: A sprint is a two week cycle, Monday to next Friday. We work on stories during a sprint.</li></ol><h3>Methodology 🔄</h3><h4>1. Backlog 💡</h4><p>Backlog is a repository of ideas. Ideas about tasty, mouth-watering pizzas that no-one has baked or even thought of before. Whenever we come across such ideas, we safe keep it in backlog. When the right time arrives, we groom the idea into Story (recipe) for the team to cook.</p><h4>2. Story-board 📋</h4><p>The story-board contains all the recipes that we are cooking, plus the ones in line to cook. A feature can have multiple stories, but a story can never span across multiple features.</p><p><strong>Story Writing</strong><br>A story (recipe) is where we employ actors and put down actions that the actor should be able to do or not do, effectively jotting down requirements. Writing well defined stories gives a proper idea of the entailing work.</p><blockquote>Good stories always have a strong actor or a protagonist, just like Bollywood movies. Stories broadly capture Actors’ requirements to perform particular actions.</blockquote><p>For example, let’s take an example from the WhatsApp, “Texts” feature of the “Chats” module. This feature can have stories like</p><ul><li>Send text message</li><li>Receive text message</li></ul><p>Let’s define the above stories.</p><p><strong>1. Send text message</strong>: In this story, we have defined actions for two actors: Sender, System/Server</p><p><strong>Sender should be able to</strong></p><ul><li>type a message</li><li>format message like bold, italic, strikethrough</li><li>send a message and see time</li></ul><p><strong>System should be able to</strong></p><ul><li>encrypt message on client and save on server</li><li>deliver encrypted message to receiver</li><li>update time sent of message</li></ul><p><strong>2. Receive text message</strong>: In this story, we have defined actions for two actors: Receiver, System/Server</p><p><strong>Receiver should be able to</strong></p><ul><li>receive a message and notifications</li><li>open the message and time when message was sent</li></ul><p><strong>System should be able to</strong></p><ul><li>decrypt message on client and notify receiver</li><li>update state Delivered/Seen of message along with time</li></ul><blockquote>The System/Server actor should have actions that are event based or time based, that don’t need an intervention from the user.</blockquote><p>Stories (recipes) should always have meaningful titles. “Send text message” is a good example because it</p><ul><li><strong>is action oriented — </strong>The user should be able to send messages to other users</li><li><strong>reflects the scope of work</strong> — Encrypting the message and sending the message to receiver via server</li><li><strong>aligns with business objective</strong> — The users should be able to chat and communicate with other users</li></ul><p><strong>What are complexity points?<br></strong>After we have defined a story (recipe), we also define its complexity. The range of complexity points is a Fibonacci series: 1, 2, 3, 5, 8, 13. The complexity points are also known as story points.</p><p><strong>How do we decide the complexity? By asking a couple of questions.</strong></p><ul><li>Is this a recipe that we as a team have cooked multiple times?</li><li>Does this need some ingredients that we have never heard of?</li><li>Can this be cooked in a sprint?</li><li>What is the impact? Will customers fall in love with our newly cooked pizza and rate our restaurant 5 stars?</li></ul><p>For e.g., a story where we have to write APIs, DAOs and procedures, code frontend, and implement store pattern can be easily an 5 or 8-pointer story based on the scope of work.</p><blockquote>Use a 5 pointer story for reference while estimating complexity for a new story.</blockquote><p><strong>Complexity and time<br></strong>The complexity indicates story difficulty, not the time needed. Complexity considers both difficulty and problem impact, below are a few examples.</p><ul><li>A Formula 1 pit stop is a fantastic example of high complexity (1000) but short time. F1 teams use specific procedures and training to quickly refuel the car, change tires, and sometimes even replace engines in just a few seconds. This is something that might take regular mechanics several weeks to accomplish.</li><li>For instance, defining containers and reference data on a content management system might be 2 pointer story but could take days or more based on data volume.</li><li>A problem like choosing an email marketing tool might be 100 points but could take 10–15 days (if you are lucky and you find a tool like ListMonk).</li></ul><p>However, that being said, in many cases you’d find the complexity to be associated with time. For example, a recipe where you have to write a micro-service including APIs, DAOs and procedures, frontend, and implement store pattern. We cook such recipes all the time, hence we have a decent understanding of complexity to time relation.</p><p>Below is the complexity-time relation we follow at Pizza Org.</p><ul><li>1 point — 1 day</li><li>2 points — 2 days</li><li>3 points — 2 days</li><li>5 points — 4 days</li><li>8 points — 7 days</li><li>13 points — 10 days</li></ul><h4>3. Running sprints 🏃🏼</h4><p>During a 2 week sprint, the teams work on baking delicious pizzas as per the recipes written in the sprint planning.</p><figure><img alt="Walter White talking with Mike" src="https://cdn-images-1.medium.com/max/400/1*ZkQnawchzE93lP-QQEx5gw.gif" /></figure><p><strong>Sprint planning<br></strong>Sprint planning is the process of writing recipes to cook for the current sprint. The first day of the sprint is dedicated to grooming and writing well-defined recipes for the team to cook. Any and all unknowns should be eliminated during the sprint planning. Two important things to take care of:</p><ol><li>We should be able to cook a 13 pointer recipe in a sprint of 2 weeks. If we realize it cannot be completed in a sprint, we breakdown the story (recipe).</li><li>If there is a recipe that has unknowns or is not groomed, that recipe shall not be lined up for baking.</li></ol><p><strong>Daily standups<br></strong>As a team cooking recipes together, we need to communicate internally on what recipe we are working, what’s the progress and if any ingredients are missing or rotten, blocking us from cooking our recipes. We connect daily morning and share our updates in the <a href="https://www.atlassian.com/agile/scrum/standups">daily standups</a>.</p><blockquote><strong>No Story, No Status:</strong> Each and everyone must give their status using a story card.</blockquote><p>Agenda for each morning standup is simple</p><ol><li>what did you work on yesterday</li><li>what are you planning to work on today</li><li>are there any blockers</li></ol><blockquote><strong>Missing daily standups</strong> is like leaving your pizza unattended in the oven, either it will stay raw or get burnt to a crisp.</blockquote><p><strong>Cooking recipes<br></strong>Following agile methodology is of no use if we are not able to cook our recipes within the 2 week sprint. However, the question arises, when do we know that a recipe is cooked completely.</p><p>Below is how we determine the lifecycle of a recipe basis the progress.</p><ul><li>Not started — Stories that are yet to be picked up in a sprint</li><li>In progress — Stories that are being worked upon, in the current sprint</li><li>Needs review — Stories that have been coded but functional/design/code review is pending</li><li>On hold — Stories that were picked up in a sprint, but paused in between</li><li>Completed — We mark a story as completed<br>- when they are coded completely<br>- deployed to Dev via CI/CD pipeline<br>- gone through functional testing<br>- the code is reviewed<br>- the code is design-reviewed</li></ul><h4>4. Sprint demos 📺</h4><p>A sprint is a two week period, starting from Monday and ending on the Friday of the second week. On these Fridays, everyone gathers and demo what they have cooked. This is called as Sprint demo. We demo what we have cooked, whether it’s the tastiest recipe ever or a half-cooked recipe. The goal of the sprint demos is to see progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*1M9ddmkCUabA8TX_VFLIeQ.png" /></figure><p><strong>Velocity</strong><br>Velocity is the number of complexity points (story points) a team member completes in a sprint on average. Velocity is simply the number of total completed story points divided by the number of sprints a team member has participated in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*EO_6gPxmtRi_Hzc7ErVj9g.gif" /></figure><p><strong>Now, what do we achieve by gauging velocity?<br></strong>Velocity allows us to plan our sprints better and understand how we are progressing as a team. If we see that Cook A has a velocity of 15 while Cook B has velocity 21, the Sprint Master can assign the recipes to the cooks accordingly. Velocity on a cook level also flags outliers who are performing extremely well or cooks who need some support and push to bake their recipes.</p><h3>Managing debt 🛑</h3><p>A story is considered debt if it is not completed at the end of a sprint. Now, everyone loves leftover pizzas but half-baked recipes are spill overs (debt) which we would like to quickly cook and get done with. The ideal case is where we have no debt and we enjoy the recipes we cooked in the same sprint.</p><figure><img alt="Pizza delivery guy asking for the payment" src="https://cdn-images-1.medium.com/max/400/1*4oZswTSTvf6t98iZl_fdww.gif" /></figure><h4>Types of debt ❓</h4><p>Incomplete stories can have different impact as per the complexity and the progress made. Below are the two types of debts.</p><ul><li>Minor debt<br>- Definition: Cooking is complete but code/design/FA review (taste-test) is pending.<br>- Risk: Can pile up very quickly leading to major delays in cooking new recipes</li><li>Major debt<br>- Definition: Cooking is incomplete and the recipe is not ready for taste-testing<br>- Risk: Pushbacks our timelines for delivering delicious pizzas</li></ul><h4>Overcoming debt 📈</h4><p>While we aim to remain debt-free, if any debt arises, here’s how we plan to overcome it.</p><p><strong>Minor debt</strong></p><ul><li>These stories can be picked up as secondary stories in the new sprint</li><li>We primarily cook new recipes and squeeze in the debt from previous sprint for completion</li></ul><p><strong>Major debt</strong></p><ul><li>Till the stories falling in the major debt category are completed, we cannot pick up new recipes</li><li>We pick up these as primary stories and push for completion so we can cook new recipes</li></ul><blockquote>All debt should be cleared in a maximum of 2 sprints.</blockquote><h3>Ground rules 📏</h3><ol><li>We write well-defined stories</li><li>We update stories regularly</li><li>We run our standups using story-boards</li><li>We never go into a standup without an updated story</li><li>We finish stories within a sprint</li><li>We conduct Sprint demos on the second Friday of every sprint</li><li>We mark a story as complete once it passes through required reviews and testing (i.e., functional review, code review, design review)</li></ol><p>Developers need to get their code reviewed by fellow developers while stories are actively worked upon. If too many stories have piled up in “Needs Review” status, developers can devote the Friday’s second half (first week of the sprint) for code reviews.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63937b3edc8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is GST e-Invoicing?]]></title>
            <link>https://medium.com/blog-by-sandbox/e-invoice-a-stride-towards-ease-of-doing-business-and-tax-automation-2a65e87fa023?source=rss-aa531df32176------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a65e87fa023</guid>
            <category><![CDATA[taxes]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[gst]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[einvoice]]></category>
            <dc:creator><![CDATA[Vaibhav Bansal]]></dc:creator>
            <pubDate>Mon, 17 Jul 2023 14:48:37 GMT</pubDate>
            <atom:updated>2024-07-03T13:29:02.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="GST e-Invoicing: Towards $5 Trillion" src="https://cdn-images-1.medium.com/max/1024/1*rM8a45NIZCQgpYj1BfKsNw.png" /></figure><h3>What is an invoice?</h3><p>An invoice records the seller and buyer tax details, the items sold, their quantity and unit price, and the grand total with tax.</p><p>Now imagine the sheer amount of invoices created monthly across India. According to a Bloomberg report in 2017, more than 350 crore invoices are created on a monthly basis by 80 lakh businesses across India¹. This translates to reporting these sales invoices and filing GST Returns. This brings in operational, and compliance overheads as well as gruelling manhours going into filing and reconciliation of issues like non-reporting, under-reporting and over-reporting. The compliance overheads that come with running a business are also one of the reasons that many businesses avoid registering for GST.</p><h3>e-Invoice, the game-changer</h3><p>On 1st Oct 2020, the GST Department introduced the e-Invoicing system to businesses, implemented in a phased manner based on the annual turnover. e-Invoice system is applicable to B2B sales, where B2B stands for registered business (supplier) to registered business (buyer). The goal is to better the ease of doing business in India by handling the overheads of reporting, reconciliation and filing.</p><h4>How is it game-changing?</h4><p>e-Invoice is like a normal sales invoice, the only difference is that now there is a standard structure that needs to be followed for generating invoices through an Invoice Registration Portal (IRP). Under the e-Invoicing system, an identification number called Invoice Registration Number (IRN) will be issued against every invoice by the IRP.</p><p>The clever thing is that all e-Invoices generated will port to the GST Portal after 2 days and the GSTR will already have B2B sales data. Businesses now only need to report B2C and other types of invoices to GSTN. Not just this, there are other benefits like</p><ul><li>No need for manual data entry for filing GSTR-1</li><li>Reduction in processing costs and disputes</li><li>Eliminates the huge gap and overheads involved in data reconciliation under GST</li><li>Interoperability as e-Invoices created on one software can be read by other tools</li><li>Relevant invoice details would be auto-filled in the various GST returns, which is especially helpful for generating part-A of E-Way bills</li><li>Improving overall business efficiency</li></ul><h4>End-goal and benefits to the India Inc</h4><p>The e-Invoice system is a move not only to improve business efficiency but to also curb tax evasion. By mandating sales invoice reporting as per applicability, the data is seeded to the IRPs which then port the data to the GST Portal. With GST-registered businesses in 2023 nearing 1.4 crores, the GST gross revenue is also growing. April 2023 clocked the highest-ever GST revenue collection of 1.87 Lakh Crores². The e-Invoice system adds much necessary oil, stability and trackability to the GST engine.</p><h3>e-Invoice Applicability</h3><p>e-Invoice system was launched with the mandate applicable only to businesses having turnover of more than 500 crores. At the end of the first launch month itself (31st Oct 2020), <strong>close to 5 crore e-Invoices</strong> were generated³.</p><p>As the e-Invoice system enters into its 6th phase, businesses having turnover over 5 crores will be liable to generate e-Invoices for all B2B sales. This is applicable from 1st August 2023⁴. If a business has an annual aggregate turnover of over Rs. 5 crore in any previous financial year from 2017–18, it will be mandatory for them to generate e-Invoices.</p><figure><img alt="Phase-wise rollout of e-Invoicing in India" src="https://cdn-images-1.medium.com/max/1024/1*UmatntUANQPi1gqKoOr7BQ.png" /><figcaption>Phase-wise rollout of e-Invoicing in India</figcaption></figure><p>It would be 3 years from the introduction to the e-Invoice system on 1st Oct 2023. And the turnover applicability has gradually decreased during this period. This is to bring all businesses on board the e-Invoice system in a planned manner instead of a brute-force manner. This gives businesses time to prepare and automate their GST as well as e-Invoicing workflow as per the compliance requirements laid down by the GST Department.</p><h3>How does Sandbox fit in the scenario?</h3><p><a href="https://sandbox.co.in/">Sandbox</a> is a SaaS-based API platform that enables businesses to automate end-to-end tax compliances. Businesses can plug Sandbox API into their existing workflows and/or ERP Accounting tools for automating <a href="https://developer.sandbox.co.in/docs/e-invoice-api-guide">GST e-Invoicing</a> as well as <a href="https://developer.sandbox.co.in/docs/gst-taxpayer-api-guide">GST Return</a> filing and reconciliation.</p><h4>e-Invoice generation using API</h4><figure><img alt="Steps to automate e-Invoicing using API" src="https://cdn-images-1.medium.com/max/1024/1*757o-iUg87gD1nwUW-wMSA.png" /><figcaption>Automate e-Invoicing using API</figcaption></figure><h4>Why Sandbox</h4><ul><li>In-depth and rich APIs, compliant with the latest government guidelines</li><li>Developed by developers, for developers</li><li>Reliable REST-like API with 99.99% uptime</li><li>Exciting, up-to-date API docs</li><li>No setup and annual maintenance fees</li></ul><p>If you are looking to automate tax compliance, you can get started with a <a href="https://dashboard.sandbox.co.in/#/start-trial">Free Trial</a> or drop a note on the Sandbox <a href="https://sandbox.co.in/contact-sales/">contact page</a>!</p><p><strong>References</strong></p><p>¹The Economic Times. 2017. “3.5 Billion Invoices Every Month! All about the Technology That GST Will Bank on from July,” May 30, 2017. <a href="https://economictimes.indiatimes.com/news/economy/policy/3-5-billion-invoices-every-month-all-about-the-technology-that-gst-will-bank-on-from-july/articleshow/58907708.cms">https://economictimes.indiatimes.com/news/economy/policy/3-5-billion-invoices-every-month-all-about-the-technology-that-gst-will-bank-on-from-july/articleshow/58907708.cms</a>.</p><p>²‘GST System Statistics | Goods and Services Tax Council’. n.d. Accessed 9 July 2023. <a href="https://gstcouncil.gov.in/gst-system-statistics">https://gstcouncil.gov.in/gst-system-statistics</a>.</p><p>³“E-Invoice — A Path Breaking Initiative Completes One Month on 31st October.” n.d. Accessed July 6, 2023. <a href="https://www.pib.gov.in/Pressreleaseshare.aspx?PRID=1669430">https://www.pib.gov.in/Pressreleaseshare.aspx?PRID=1669430</a>.</p><p>⁴“Central Board of Indirect Taxes &amp; Customs Circular for E-Invoice Phase 6.” n.d. Accessed July 6, 2023. <a href="https://taxinformation.cbic.gov.in/view-pdf/1009732/ENG/Notifications">https://taxinformation.cbic.gov.in/view-pdf/1009732/ENG/Notifications</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a65e87fa023" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-by-sandbox/e-invoice-a-stride-towards-ease-of-doing-business-and-tax-automation-2a65e87fa023">What is GST e-Invoicing?</a> was originally published in <a href="https://medium.com/blog-by-sandbox">Blog by Sandbox</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>