<?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 Raman Bansal on Medium]]></title>
        <description><![CDATA[Stories by Raman Bansal on Medium]]></description>
        <link>https://medium.com/@ramanbansal?source=rss-dfc8f8dc9908------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hvjgiKK9esC0HpQeM85e0Q.jpeg</url>
            <title>Stories by Raman Bansal on Medium</title>
            <link>https://medium.com/@ramanbansal?source=rss-dfc8f8dc9908------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:55:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ramanbansal/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[How Agile helped me hack “My House Move”]]></title>
            <link>https://medium.com/@ramanbansal/how-agile-helped-me-hack-my-house-move-5dbfc317a31e?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dbfc317a31e</guid>
            <category><![CDATA[lifehacks]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[moving]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Tue, 29 Apr 2025 12:03:43 GMT</pubDate>
            <atom:updated>2025-04-29T12:03:43.789Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*shvyIMP7yjIaLf-8xHAGhw.png" /><figcaption>Just an AI generated image, for context.</figcaption></figure><p>Most people approach house moves like a waterfall project — pack everything, dump it all in one day, and hope for the best. At least, that’s how I’d always done it.</p><p>However this time, I treated mine like a sprint backlog. The result? My apartment was functional on <strong>Day 1</strong>, I could find all my critical stuff without rummaging, and I didn’t burn out in the process.</p><p>Here’s how applying Agile principles made it possible — and why software folks (or atleast scrum masters) will instantly get what I mean.</p><p><strong>🚀 MVP: Moveable Viable Possession</strong></p><p>Instead of trying to “launch” my entire house in one go, I focused on delivering an MVP: a <strong>liveable setup on Day 1</strong>. What’s the smallest, simplest collection of items I needed to go live? Here’s what made the cut:</p><ul><li>Sleeping setup</li><li>Cooking setup</li><li>Wi-Fi setup</li><li>WFO readiness setup</li></ul><p>Once this MVP was up, I iterated from there. Agile 101.</p><p><strong>📝 Backlog Grooming for Real Life</strong></p><p>I created a literal backlog of items — this time, not by room, but by <em>priority and use frequency</em>. High-priority items went into Sprint 1 (Day 0–1). Low-urgency stuff was deferred to later “sprints.”</p><p><strong>The three sprints:</strong></p><ul><li><strong>Day 0</strong>: High-value assets (moved personally in my car)</li><li><strong>Day 1</strong>: High-frequency items via the <em>Porter</em> app (hired Tata Ace)</li><li><strong>Day 2</strong>: Bulk + edge-case items via traditional movers</li></ul><p>Breaking the move this way let me <strong>manage scope creep</strong>, track my velocity (a.k.a. physical and mental energy), and reduce the blast radius of mistakes.</p><p><strong>🧪 Iterative Setup, Not One-and-Done</strong></p><p>One surprising benefit of this Agile-style move was that I could <strong>settle in gradually</strong>. For example, I shifted my TV table <em>three times</em> across different rooms — just to see where it fits best plus can fulfil the purpose.</p><p>Because I wasn’t overwhelmed with everything arriving at once, I had the flexibility to test what worked. In a typical move, I would’ve been stuck with the first setup for <em>at least five days</em> — just too drained to rethink anything.</p><p>This way, I made better decisions, and the space ended up working for me — not just looking “done.”</p><p><strong>🔄 Iteration &gt; Perfection</strong></p><p>I didn’t try to get it all right on Day 1. My Agile mindset told me: just ship something functional, then iterate.</p><ul><li>I unpacked only what I needed at first</li><li>I reorganized and optimized over the week</li><li>I kept some tasks in the “backlog” for after settling in</li></ul><p>This helped me avoid the usual trap: unpacking everything too fast and cluttering up my mental and physical space.</p><p><strong>💸 Cost Distribution = Value Stream Optimization</strong></p><p>Instead of one giant truck, I used <strong>multiple delivery streams</strong> to spread cost and control quality. I ended up spending almost same (as I tipped more people because I was happy with the progress):</p><ul><li>Day 0: My own vehicle = secure transport for fragile/expensive gear</li><li>Day 1: <em>Porter</em> = flexible, short-distance hauls for quick-access items</li><li>Day 2: Packers &amp; Movers = low-touch batch processing of heavy/low-priority stuff (This attracted my lowest mind share as most vital stuff had already reached at the destination)</li></ul><p>Result: Costs were more evenly distributed, and risks were managed per stream.</p><p><strong>🔍 Retro: Was It Worth It?</strong></p><p>Overall, the benefits far outweighed the effort. Let’s run a quick retrospective:</p><p><strong>What went well:</strong></p><ul><li>Setup was complete enough on Day 1</li><li>No emergency purchases needed</li><li>Found my essentials without chaos</li></ul><p><strong>What could’ve gone better:</strong></p><ul><li>Coordination fatigue (context-switching across services)</li><li>Slightly more physical effort</li></ul><p><strong>Action items for next time:</strong></p><ul><li>Better inventory tracking with printed labels for easy recognition of content inside boxes</li><li>Buffer an extra half-day post-move for deep rest</li></ul><p><strong>🧠 Final Thought: Agile Works Outside Jira</strong></p><p>Moving your home is a high-stakes project. You have dependencies, deadlines, a budget, and a user (you) who expects a working product from day one.</p><p>Agile thinking — prioritize, iterate, adapt — turned what could have been a burnout-fest into a controlled, efficient rollout.</p><p>Whether you’re shipping code or cardboard boxes, Agile can help you move smarter and maybe, happier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dbfc317a31e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Debunking Common Myths About Agile Philosophy]]></title>
            <link>https://medium.com/@ramanbansal/debunking-common-myths-about-agile-philosophy-1d7afda7d820?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d7afda7d820</guid>
            <category><![CDATA[myths]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Tue, 08 Aug 2023 17:28:38 GMT</pubDate>
            <atom:updated>2023-08-08T17:28:38.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="https://www.monroemichigandentist.com/three-common-dental-myths-debunked/" src="https://cdn-images-1.medium.com/max/750/0*p-JSPYL_Vd0lSGaa.jpg" /></figure><p>We’ve all come across a plethora of quotes that don’t accurately capture the true essence of agile. Many of these quotes are, in fact, misconceptions. Let’s debunk some prevalent myths surrounding the agile philosophy by providing clarifications based on agile practices, the Scrum guide, and personal experience.</p><p><strong>Myth 1: Agile Means No Documentation</strong></p><p>While agile emphasizes working software over comprehensive documentation, it does not equate to “No documentation.” Agile doesn’t disregard documentation, but it encourages lightweight and pertinent documentation. In Scrum, artifacts like the Product Backlog, Sprint Backlog, and Increment serve as documentation. The goal is to have just enough documentation and NOT excessive documentation to support collaboration and maintain transparency.. The Agile Manifesto values “Working software over comprehensive documentation,” and NOT “No documentation.”</p><p><strong>Myth 2: Agile Has No Planning</strong></p><p>Agile entails continuous planning at various levels. Highest order planning occurs at the release level, where work items are discussed and estimated to create a product roadmap. Further planning takes place in iterative cycles known as Sprints. Each Sprint starts with Sprint Planning, during which the team defines upcoming sprint. Daily Scrum meeting aids daily planning based on the work taken for the delivery during sprint. Agile planning is adaptable, accommodating changes, allowing teams to respond to evolving requirements.</p><p><strong>Myth 3: Agile Means No Fixed Timeline</strong></p><p>Agile projects feature fixed-duration iterations like Sprints in Scrum, providing consistent time frames for delivering value increments. These time-boxed iterations ensure predictability while allowing flexibility to adjust priorities and accommodate changes. As compared to traditional development, Agile maintains fixed variables for time and resources, with scope varies as per the priority of the business. Which means, timelines are defined by what’s being planned for delivery and the team’s average velocity.</p><p><strong>Myth 4: Agile Doesn’t Do Upfront Analysis and Design</strong></p><p>Agile advocates ongoing analysis and design throughout projects. In Scrum, teams conduct sufficient upfront analysis and design to initiate work, refining them iteratively as insights develop during development. Teams avoid designing for the entire product initially and instead adapt as needs evolve. This approach minimizes overengineering and enhances adaptability.</p><p><strong>Myth 5: Agile Targets to Deliver Features Faster</strong></p><p>Agile enables parallel delivery, unlike the sequential nature of waterfall way of development, making it seems faster. However, agile prioritizes delivering valuable features early and frequently, not just speed. Agile focuses on delivering the right features aligned with customer needs. While its iterative approach accelerates value delivery, the emphasis remains on sustainable development pace and quality.</p><p><strong>Myth 6: Agile Is Chaotic and Unstructured</strong></p><p>Agile frameworks like Scrum, Kanban, and Extreme Programming provide structure. These frameworks define roles, events, and artifacts, fostering transparency, inspection, and adaptation. While agile embraces change, it does so within a structured framework, ensuring organization and coherence.</p><p><strong>Myth 7: Agile Allows Scope Changes Anytime</strong></p><p>Agile welcomes changing requirements but manages scope changes through defined channels. In Scrum, changes are usually incorporated at the beginning of a Sprint, and any changes during the Sprint are carefully evaluated for their impact. If deemed necessary, there may be exchange of stories, however if changes hinder the Sprint goal, cancellation might be advised. Agile seeks a balance between responsiveness and stability.</p><p><strong>Myth 8: Agile Removes the Need for Testing</strong></p><p>Agile emphasizes testing throughout development, ensuring product quality. Test cases and acceptance criteria are outlined alongside story definitions. Sprint planning covers new development and defect fixing. Continuous testing, including automated tests, occurs during the development cycle. Test Driven Development is a key agile practice, where coding follows guided tests, detecting issues early for sustained development.</p><p><strong>Myth 9: Agile Teams Can’t Provide Accurate Estimates</strong></p><p>Agile teams DO provide estimates based on current understanding of the work at hand. Estimates are NOT fixed commitments but serve as planning tools. The “Cone of Uncertainty” concept explains how estimation accuracy improves iteratively through experience and feedback loops.</p><p><strong>Myth 10: Agile Doesn’t Require Frequent Customer Involvement</strong></p><p>Agile encourages continuous customer collaboration. The Product Owner, representing the customer in Scrum, actively participates in Sprint activities. Regular customer feedback ensures alignment with expectations. Agile demands immediate integration of customer input into ongoing work, emphasizing constant involvement.</p><p><strong>Myth 11: Agile and Scrum are Interchangeable Terms</strong></p><p>Agile is the umbrella framework embodying values and principles, while Scrum is one of the various agile methodologies. Think of Agile as cars and Scrum as a sedan. Multiple agile approaches, like Lean programming and Kanban, Scrumban, Extreme programming, and several hybrid approaches exist under the same umbrella. No single methodology suits all scenarios; the choice depends on user needs, stakeholder concerns, and project specifics.</p><p><strong>Myth 12: Agile Is the Cure for All Problems</strong></p><p>Agile is NOT a silver bullet which will solve all problems related to the Software Development Lifecycle. However, when implemented in its spirit, it enhances visibility, communication, quality delivery, customer satisfaction, employee motivation, and continuous improvement.</p><p><strong>Myth 13: Agile Is Better/Worse Than Traditional Methodologies</strong></p><p>Agile’s increasing adoption doesn’t make it superior in all contexts. The methodology choice hinges on project type, environmental variables, company culture, requirement clarity, timelines, resources, and more. Waterfall suits projects with clear initial requirements where agile may be an over-fit.</p><p><strong>Myth 14: Developers Get To Do What They Like</strong></p><p>No, developers do not get to do what they “like” but what’s “needed”. Scrum Team gets to decide the sprint goal during sprint planning and the development team decides the work to be done during the sprint to meet the sprint goal. Afterall, the Sprint Backlog is a plan by and for the Developers (as per scrum guide). However, it’s a collaborative process which involves discussion and negotiation of development team — who are building the system and product owner — who requested for the system. The intent of sprint is to cull out a potentially releasable product at the end of it, hence the discussion revolves around how the sprint will be an increment to the delivered product.</p><p><strong>Myth 15: Agile Means Less Discipline</strong></p><p>Agile encourages self-organization, but this doesn’t imply chaos. Scrum processes, events and roles/ responsibilities ensure disciplined execution of tasks. Activities like maintaining backlogs, attending scrum events, task pick-up, capturing &amp; solving impediments and delivering self-inspected outcomes demand discipline.</p><p><strong>Myth 16: Daily Scrum Meeting is Same as the Status Meeting</strong></p><p>Scrum team is supposed to get together during the daily scrum meeting and quickly review the overall progress based on efforts in last 24 hours against the sprint goal and quickly gauge if team is on track or not. That is followed by status updates on current tasks are quickly picked-up along with the status check of in-flight items. Any impediment gets reported to ensure the development journey is smooth and to arrest any upcoming blockers.</p><p><strong>Myth 17: Sprint Backlog is a Commitment That must be Honoured in all Circumstances</strong></p><p>Sprint backlog is a collection of work items that need to be completed in each sprint, but there may be circumstances when it gets difficult to finish 100% of planned work. This means one need NOT to make weekends — working or FORCE team to spend long hours in office to complete the balance work. If there is a Sprint backlog remaining at the end of Sprint, then it simply means either the planning was not completely effective or there were unexpected capacity issues in the team during the sprint and both needs to be fixed up properly, to avoid recurrence. In such cases, the backlog moves back to Product backlog to be considered in future sprints based on its priority.</p><p>Overall, understanding agile’s nuances dispels these misconceptions, enabling organizations to harness its benefits effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d7afda7d820" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intro to Business Process Modelling]]></title>
            <link>https://medium.com/@ramanbansal/intro-to-business-process-modelling-2e2c7c14730c?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e2c7c14730c</guid>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Thu, 22 Jun 2023 10:15:19 GMT</pubDate>
            <atom:updated>2023-06-22T10:15:19.538Z</atom:updated>
            <content:encoded><![CDATA[<p>Process Taxonomy, is defined in a typical Business Process Modelling/Business Process Architecture tool. BPA/BPM does not just include the hierarchical description of processes, but also the related resources, rules, supporting systems, transactional information, performance measures and governance elements. These are defined in various different systems and mapped to processes at various levels in the process hierarchy.</p><p>Let’s consider our purchase process through any e-commerce portal to understand process flow. First of all, a process shall be understood, as famously said, at 30,000 feet, in the form of SIPOC. So, SIPOC of e-commerce purchase process would be :</p><ul><li><strong>S</strong>upplier: Amazon/ Flipkart/ eBay/ etc.</li><li>Input: Need for a product</li><li>Process: Search the product =&gt; Order the product =&gt; Order Payment =&gt; Order delivery =&gt; Order Feedback</li><li>Output: Ordered product</li><li>Customer: You</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*DmZXygd5IuAIOjXu78_PmA.png" /></figure><p>This 30,000 feet view will help us in defining the process at detailed level. But, how to define this detailed process flow? There are a thousand ways of representing process flows. If there is no standardized notation used to depict process flows, we could potentially face a challenge with uniformly interpreting them. Just imagine a place where everyone speaks their own language. How will anyone be able to communicate effectively with others?</p><p>In the process world, there are various internationally accepted notation standards (i.e. grammatical syntax) for defining process flows, for instance Event-driven Process Chain (EPC) diagrams, Business Process Modeling Notation (BPMN), Swim-lane Flowchart, Data Flow Diagram (DFD), Unified Modeling Language (UML) diagrams, Integrated DEFinition (IDEF), Specification and Description Language (SDL) and Decision Model and Notation (DMN). Out of these, EPC and BPMN are most widely adopted standards.</p><p>Once a standard notation is agreed upon, the next task is to gather the inputs from stakeholders and model the processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*8K64hJPppInFoeT7prSOGw.png" /></figure><p>Let’s go further, one level down, to the step level detailing. Every process flow consists of various steps which occur in a specific order. And every step needs to be detailed out against 5W1H as below:</p><ul><li><strong>Who</strong> are involve in the execution of the step (Responsible, Accountable, Consulted and Informed)?</li><li><strong>What</strong> are the KPIs/SLAs, risks involved and controls monitored against this step?</li><li><strong>Where</strong> will this step be executed (which system, location)?</li><li><strong>When</strong> should this activity happen (triggering events)?</li><li><strong>Why</strong> should this step be executed (output expected)?</li><li><strong>How</strong> exactly shall this step get executed (detailed activity)?</li></ul><p>All these details are then modelled in the BPA tool, which can give various analytics and reports to drive data driven decision-making in regards to process improvement and optimization. Process Analytics supports initiatives such as digitization, automation, faster processing, cost optimization, effort or resource optimization, etc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e2c7c14730c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intro to BUSINESS PROCESS CAPABILITY]]></title>
            <link>https://medium.com/@ramanbansal/intro-to-business-process-capability-b858d9f1a115?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/b858d9f1a115</guid>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Thu, 22 Jun 2023 10:11:19 GMT</pubDate>
            <atom:updated>2023-06-22T10:11:19.455Z</atom:updated>
            <content:encoded><![CDATA[<h3>Intro to Business Process Capability</h3><p>As organizations grow, the new talent pool needs to know about existing operations, current challenges and hidden opportunities to optimize and improve over baseline. Business process architecture helps in meeting this expectation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*wmsO1ZQVgS9kLVWdihLNmA.png" /></figure><p>Let’s understand with a simple example how Business Process Architecture is defined. Let us say our organization is like a car, where all the parts of the car work in tandem, and we are driving smoothly towards our destination. But if we have to understand how we can improve the speed of the car or its fuel efficiency, we would first need to define the capabilities of our car, and then work on the appropriate capabilities to meet our goals. Listed below are a few of the capabilities of various parts of the car, akin to various departments/functions providing specific capabilities to an organization:</p><ul><li>The engine provides power</li><li>The suspension provides maneuverability and handling</li><li>The seats provide a comfortable ride</li><li>The Air Conditioner provides clean and cool air</li></ul><p>Similarly, in the context of an organization, functions and their capabilities would be:</p><ul><li>Sales function provides the capability of selling our products and services to customers</li><li>Customer Service ensures customer satisfaction</li><li>HR function enables management of human capital</li><li>IT function provides technical capabilities</li><li>Procurement function enables purchasing from and contracting with vendors</li></ul><p>These capabilities, once defined, are then further divided into sets of process groups to deliver the end result. A capability is at a higher level, and process groups at the next level determine “How” this capability is executed. Think of using a LEGO set, to build a house, then breaking it down and building something else. A capability is the “building block”, like a LEGO brick with the ability to build the house or something else. To build something else, you may need varying numbers and sizes of LEGOs, which can also be taken apart later. The combination of a few LEGO parts to create one is called a process group and an individual piece of LEGO is a process flow, which is unique and has various facets to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*DeNxsCEvX0lYkFGAq5dhxg.png" /></figure><p>When you arrange the above set of capability, process group and process flow names, it gives rise to process architecture in a hierarchical view. This is also called the PROCESS TAXONOMY. APQC’s (American Productivity and Quality Center) Process Classification Framework is one standard taxonomy to benchmark, as it’s created through collective wisdom of participating organizations. The Process Taxonomy provides a common language for business segments and functions to communicate and define work processes comprehensively and with minimal redundancy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b858d9f1a115" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aspects of Business Process Architecture and its tool]]></title>
            <link>https://medium.com/@ramanbansal/aspects-of-business-process-architecture-and-its-tool-8272bd312260?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/8272bd312260</guid>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Thu, 22 Jun 2023 10:07:14 GMT</pubDate>
            <atom:updated>2023-06-22T10:07:14.457Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me introduce you to the basic concept of Business Process Architecture (BPA).</p><p>Imagine you want to build a beautiful house, with an intercom operated gate, weatherproof light colored walls, with a little garden outside having automated sprinklers, open terrace with an infinity swimming pool, a facade above portico for entry, a big teak wood door, huge drawing room with plush furniture and large windows, wooden spiral staircase, bedrooms with round bed, colorful lighting, luxurious and designer bathroom and what not. But how do you ensure the builder provides you exactly, what you want?</p><p>If there is one person, who can translate your vision to the exact specifications that the builder needs, it is an ARCHITECT. Why, because he is the one who defines what is constructed, how and where. An architectural plan of a building tells us which side rooms would be built, which direction would be porch and how would be our staircase and bathrooms, etc. In the absence of a proper architectural plan, the following may also happen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/336/1*kGnxubZTyHBhf7GZiKdKpw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*tn9l1Y3aEun4TekCKUkTEQ.png" /></figure><p>Business Process Architecture (BPA) is similar to the architectural plan of a building, as it is defined for better clarity on current operations and future direction of organization. Using a pen and paper to document the process architecture is the old-fashioned way. One can imagine, even relatively simplistic business models can generate files packed full of flow charts which in itself can be a mammoth task to go through and piece together and understand. Additionally, it is also a massive effort to review these process architecture documents for an entire organization and find the gap with reference to implementation. Here, a process architecture tool comes handy. A few of the benefits of using a BPA tool are:</p><ul><li>Create a common repository of process information</li><li>Manage process architecture and its elements in one visually powerful tool</li><li>Engage all kind of stakeholders on common process</li><li>Understand process interdependencies and impacts</li><li>Analyze processes, relationships and dependencies</li><li>Provide a user friendly publishing and collaboration platform</li><li>Perform effective gap analysis</li><li>Provide performance monitoring, performance management and process mining</li></ul><p>There are many process architecture tools available in market — a few examples are ARIS, MEGA, PEGA, iServer, ABACUS, PowerDesigner, SAMU, etc. These digital tools simplify the process of defining and managing the process architecture. Some of the attributes essential to tool selection are:</p><ol><li>Robustness of the tool</li><li>Ease of use</li><li>Compliance with standard notations and frameworks</li><li>Provision for a centralized repository to facilitate analysis and reporting</li><li>Ability to provide multiple views of models</li><li>Analytical ability and element traceability to generate intelligence and reports</li><li>Simulation capabilities</li><li>Flexibility and ability to customize the tool to specific business requirements</li><li>Synchronization of data with other dependent and independent systems</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8272bd312260" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Process Mapping]]></title>
            <link>https://medium.com/@ramanbansal/business-process-mapping-fa80f3fef3ec?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa80f3fef3ec</guid>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Thu, 22 Jun 2023 09:58:46 GMT</pubDate>
            <atom:updated>2023-06-22T09:58:46.347Z</atom:updated>
            <content:encoded><![CDATA[<h3>Business Process Mapping as GIS</h3><p>Let’s take a journey, back into the 1990s. Imagine yourself driving in your car without a smartphone and with no availability of Google Maps. You’re completely reliant on your own understanding and at the mercy of locals or pan-wallas to guide you in the right direction. There are countless uncertainties. You don’t know which roads are the busiest, which detour to take when you’re stuck, or what permits might be needed to enter certain areas. You’re unsure where to stop when it’s dark or when you’re running low on fuel, or worst of all, when you experience a flat tire. There’s also the risk of getting lost and wasting valuable time and resources. And of course, there’s the constant craving for a delicious vada-pav or samosa to satisfy your hungry and growling stomach.</p><p>Now let’s fast forward to the present day. Armed with Google Maps or any GPS device, those worries are a thing of the past. You have a complete view of your journey from start to finish. You know the quickest and smoothest route to your destination, where the nearest gas station is, and how to find the nearest Dominos or Burger King. How did all of this become possible? Did someone painstakingly map out every street and road, taking into account jungles and political borders?</p><p>Just as Google Maps shows you the best path, a map of your current processes can show you the optimal route to complete a task. BPM (Business Process Mapping) creates a kind of “Google Map” for business processes, which reveal the longest and busiest processes and guide you on how to navigate through them. They highlight available resources to achieve desired outcomes and provide insights on when and how different cross-functional teams collaborate to deliver value. They identify whose approval is needed for specific tasks, who is responsible for each activity, who provides their expertise, and where the buck stops. They even shed light on potential risks and offer strategies for risk mitigation.</p><p>A well-documented business process map empowers employees to make better decisions. It brings together the essential structural elements of a business, ensuring they cohesively work towards achieving set objectives. If a picture is worth a thousand words, then a well-executed process map could be worth millions (or even more) in terms of its decision-making power. It helps in improving efficiency, provide visibility, enabling decision making, standardization across organization, better communication and learning options for teams, chance of continuous improvement and effective change management.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa80f3fef3ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simply BPM]]></title>
            <link>https://medium.com/@ramanbansal/simply-bpm-cf5fedebed52?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf5fedebed52</guid>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Thu, 22 Jun 2023 09:45:41 GMT</pubDate>
            <atom:updated>2023-06-22T09:45:41.058Z</atom:updated>
            <content:encoded><![CDATA[<p>I want to offer a simple perspective on BPM without using technical jargon or going into too much detail about its components. Instead, let’s imagine a scenario where BPM can add value.</p><p>Think about your friendly neighborhood grocery shop owner. This person not only manages the finances but also handles procurement and operations due to the small scale of the business. As the shop starts doing well, the owner expands into selling vegetables, distributing local milk, and offering frozen food. Things become a bit more complicated, but manageable, with the help of an additional employee and a computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*VarrJChTghUWyA79.jpg" /><figcaption>Source — <a href="https://trak.in/tags/business/2020/04/27/7-crore-local-kirana-stores-unite-to-launch-ecommerce-app-will-this-challenge-amazon-reliance-flipkart/">https://trak.in/tags/business/2020/04/27/7-crore-local-kirana-stores-unite-to-launch-ecommerce-app-will-this-challenge-amazon-reliance-flipkart/</a></figcaption></figure><p>Despite challenges like GST and demonetization, the business continues to grow, and the shop owner decides to open a multi-location supermarket. With this expansion, the supply chain becomes more complex, accounting becomes challenging, and inventory management becomes more complicated. The owner hires a few dozen more employees and adds more computers to cope with the growth. But there’s more to the story — the shop owner recently partnered with an online grocery retailer called ‘Drofers’ for local distributions and is also launching a new White Goods store. Now, in addition to the increased operations, the owner has to deal with additional regulations, legal contracts with e-commerce partners, credit operations with banks and channel partners, and the potential integration of new technologies. To make things even more dramatic, two of the most trusted employees have switched to a competitor.</p><p>So, can the shop owner continue using the same old methods to handle everything? Is it feasible to recreate the entire system from scratch every time the business diversifies or adopts a new retail format? Can businesses rely less on individual employees? How can the owner identify the key operations that need improvement and adapt to new opportunities in a way that surprises competitors? How can new policies and rules be incorporated into the organization and ensure compliance? Can the owner make changes confidently, knowing the impact on the rest of the organization? What if they could easily transfer processes, structures, and methods from the old business to the new ones? Anything that addresses these challenges can be considered BPM.</p><p>Let’s take another example — airplanes. Since their invention, they have gone from traveling at 11 kmph to 3500 kmph. Initially, they were fully controlled by humans, but now intelligent programs have taken over, making them faster, better controlled, and safer. This is precisely what BPM aims to achieve for a business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf5fedebed52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile — An Iterative and Incremental Approach]]></title>
            <link>https://medium.com/@ramanbansal/agile-an-iterative-and-incremental-approach-1ec5bc600aa?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ec5bc600aa</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[iterative-development]]></category>
            <category><![CDATA[incremental-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Thu, 22 Jun 2023 07:33:34 GMT</pubDate>
            <atom:updated>2023-06-22T07:33:34.408Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agile — An Iterative and Incremental Approach</h3><p>Traditionally, when someone asks for any software delivery, depending upon the efficiency and effectiveness of individuals and teams, there are chances that there will be difference between expectation and reality of released product. And this difference is called as “Disappointment”. So, if we pick up one big chunk, this gap will be bigger as there is no provision for intermittent feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*Amrliohr5PUkB4epI8vQuA.png" /></figure><p>Now, let’s try to deliver the base version of these expectations and then gather customer feedback to identify the gap. Then let’s work on this gap to improve in next version/release, gather feedback again and work on that version to continually improve upon the same. This will be called as iterative delivery. This process enables teams to fine-tune and enhance the product with each iteration / release / version.</p><p>Let’s break these big set of expectations into small chunks (called releases) and now, let’s start delivering these small chunks one by one in a way that every chunk is an add-on to the previous delivery. Towards the end, the delivery is a big fat product which was sought initially. This is called incremental delivery. By delivering these small increments, teams cannot just gather feedback but showcase tangible progress to stakeholders as well.</p><p>Agile in its pure form is combination of both, iterative and incremental delivery. End-result, there is very less gap (disappointment) towards the end of delivery of last chunk of expectation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*A39WxztEzzoxi4mf9hD8vg.png" /></figure><p>Example of Iterative Development: Evolving Perfection</p><p>Think of an e-commerce website aiming to improve the user experience. The initial iteration may focus on creating a simple product listing page with only cash-on-delivery model. With iterative development, subsequent iterations add features such as search filters, personalized recommendations, and a smooth checkout process with multiple payment options. Each iteration incorporates feedback, resolves issues, and adapts to changing requirements. This iterative cycle of development allows the team to learn from user interactions, refine their approach, and continuously enhance the product’s quality and usability.</p><p>Example of Incremental Delivery: Building Success Step by Step</p><p>Let’s consider the example of a project management software. Instead of waiting for the entire system to be developed, Agile enables the team to deliver a functional project creation module within the first iteration. Subsequent iterations then add features like task assignment, progress tracking, and reporting. This iterative approach keeps stakeholders engaged, allows for early feedback, and ensures that evolving requirements are met at every stage of development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*TNhBACEApCEEPXTD3RjakA.png" /></figure><p>Conclusion : Agile methodology’s incremental and iterative approach has revolutionized the software development landscape. Through incremental delivery and iterative development, teams can deliver tangible value to stakeholders at each stage of the project. Agile empowers teams to build products that are flexible, user-centric, and constantly evolving to meet the needs of a dynamic market. Ending the article with one diagram which depicts the both development approaches in single place (Source : <a href="https://bootcamp.uxdesign.cc/incremental-vs-iterative-development-20cba10c984e)">https://bootcamp.uxdesign.cc/incremental-vs-iterative-development-20cba10c984e)</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*StzHRGQjb5AYzXQWW46KVw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ec5bc600aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Learning Curve Called SHU-HA-RI in Agile]]></title>
            <link>https://medium.com/@ramanbansal/a-learning-curve-called-shu-ha-ri-in-agile-6c4717c63323?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c4717c63323</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[shu-ha-ri]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Tue, 20 Jun 2023 04:08:06 GMT</pubDate>
            <atom:updated>2023-06-20T04:08:06.021Z</atom:updated>
            <content:encoded><![CDATA[<p>Every change brings a need to acquire new “Knowledge” and there is a way to do it. Shu Ha Ri is one of those many ways, in which one can start their learning journey. It’s a <a href="https://en.wikipedia.org/wiki/Japanese_martial_art">Japanese martial art</a> concept which describes the stages of learning as follows:</p><p>· <strong>Shu</strong>: In this stage, the learner is expected to learn fundamentals, techniques, templates, etc. Going deep into theoretical relevance is not much appreciated as energies are expected to be spent on learning and delivery of the tasks in accordance with what’s learnt.</p><p>· <strong>Ha</strong>: In this stage, the learner is expected to know the underlying principles and theories behind what they have learnt and what they have been implementing. And then, based on their learning and practice, they should start creating new by breaking from traditional practices.</p><p>· <strong>Ri</strong>: In this stage, the learner is expected to transcendent as there are no right techniques, but technique created by your own, which makes you a grandmaster. One doesn’t need to learn from others in this phase and create their own ways of doing the things. Bruce Lee is a good example, who has attained the “Ri” phase by going through Shu and Ha, and created a different style of martial art technique by name of “Jeet Kune Do”.</p><p>Chinese martial arts — Wushu, also follow 3 stage concept called Di — Ren — Tian. But you must be thinking, its enough about martial arts, how these things are related to Agile? So, let me try to explain, how to implement this concept in Agile learning. There’s a study by Gartner, which explains that agile change takes time and commitment which is approx. 3 years for full maturity. So, if we simply merge ShuHaRi with this thought, what we get is a 3-year plan of establishing Agile knowledge within organization. Let me explain these 3 years:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*6sGpgAg5EjBfMT7HYPkhHQ.png" /></figure><p>· Year 1 (Shu): Adopt the established Agile tools &amp; practices. Pick up relevant agile practice, based on the specific need of the project and simply start following that practice to the T. Initial efficiency may take a hit but that’s a given, whenever people start following a new practice.</p><p>· Year 2 (Ha): Customize the framework &amp; practices as per your organization. This is the time to modify the practices and align them with the requirements and culture of your organization, without impacting the agile principles and agile manifesto.</p><p>· Year 3 (Ri) Design your company specific Agile framework which addresses org specific complexity and needs. This is the grandmaster stage where you will create an org-specific framework which will address the unique environment and challenges in the most efficient and effective way. Spotify Agile Tribes is a perfect example of this framework created by Spotify to match their needs. Indeed, their organization structure has been aligned with their framework, so that they can deliver with agility. And we all know the success story of Spotify, which is now an undisputed king of on-demand streaming music.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c4717c63323" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Measure to improve]]></title>
            <link>https://medium.com/@ramanbansal/measure-to-improve-20fe0db116ef?source=rss-dfc8f8dc9908------2</link>
            <guid isPermaLink="false">https://medium.com/p/20fe0db116ef</guid>
            <category><![CDATA[measure-what-matters]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[measurement]]></category>
            <category><![CDATA[improvement]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Raman Bansal]]></dc:creator>
            <pubDate>Fri, 26 May 2023 09:46:35 GMT</pubDate>
            <atom:updated>2023-05-26T09:46:35.349Z</atom:updated>
            <content:encoded><![CDATA[<p>So, when you travel on highways, do you check the speed of your car whether its within prescribed range? When your kids get their report cards, do you care about the marks they get? When you buy your shoes from Flipkart, do you see whether Amazon is selling it for lesser price? When you evaluate the cars for purchase, do you check whether the performance of the car under review, is upto the mark?</p><p>In all probability, the answer to these questions would be “Yes”!! But did you know, that inadvertently, you have been using measurement systems to assess these actions. As humans, we are biased towards better performance, and the only method to assess any performance is through measures, which may be tangible or intangible. It is so hard coded into our genome that we don’t realise that we have been sub-consciously doing performance management since childhood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/0*j_rEt0Rxu6MvRSbd.jpg" /><figcaption>Source : <a href="https://www.driveronroad.com/quiz/do-you-know-your-car-dashboard-warning-lights/">Quiz: How Well Do You Know Your Car Dashboard Warning Lights? (driveronroad.com)</a></figcaption></figure><p>A car’s dashboard is another example of a measurement system, since it reflects the health of the car in a single view. Following are the various indicators and warnings as shown on a car’s dashboard:</p><ul><li>Speedometer shows speed of the car</li><li>Odometer shows the distance travelled by the car</li><li>Tachometer shows the RPM of the wheels</li><li>Coolant temperature gauge tells the temperature of the engine</li><li>Fuel gauge shows whether sufficient fuel is there in car or it needs refuelling and there is a warning indicator as well, because its vital component for continuous movement of car</li><li>Various lamp and indicator shows that high beam light is ON, which turn signal is ON, whether car is on cruise control, any door is open, low battery warning, seat belt reminder, immobilizer ignition key warning, tyre pressure warning, etc.</li></ul><p>While the car’s dashboard will ensure that we are informed about what’s wrong with the car, it’s the driver’s and mechanic’s responsibility to keep it up-to-date and take action accordingly, otherwise car may breakdown on its way and not reach its destination.</p><p>Lets connect the dots in the context of an enterprise. An enterprise is nothing but a legal entity engaged in the business of providing goods or services to consumers, working for profit or social welfare. During the provision of services and goods, there would be some vital measures which will indicate the health of various factors for the business. When these health indicators are measured as part of measurement dashboards, it’s responsibility of management and employees to take action according to the signs and warnings to make the organisation reach its desired goals. However, the challenging prerequisite is that relevant set of measures and indicators are identified and measured.</p><p>Grace Hopper, a pioneer of computer programming in America, once said that “One accurate measurement is worth a thousand expert opinions”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20fe0db116ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>