{"id":29993,"date":"2026-08-11T13:16:55","date_gmt":"2026-08-11T13:16:55","guid":{"rendered":"https:\/\/www.tekrevol.com\/blogs\/?p=29993"},"modified":"2026-08-11T13:16:55","modified_gmt":"2026-08-11T13:16:55","slug":"lean-software-development","status":"publish","type":"post","link":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/","title":{"rendered":"Lean Software Development: Principles &#038; How to Run It"},"content":{"rendered":"    <div class=\"blog_summry_box\">\n        <button class=\"title active\" type=\"button\" data-bs-toggle=\"collapse\" data-bs-target=\"#collapseExample1\"\n            role=\"button\" aria-expanded=\"true\" aria-controls=\"collapseExample1\">\n            <h3>Key Takeaways:<\/h3>\n            <svg width=\"15\" height=\"9\" viewBox=\"0 0 15 9\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                <path d=\"M0.492188 1.47021L7.51675 7.38191L14.4383 1.47021\" stroke=\"black\" stroke-linecap=\"round\" \/>\n            <\/svg>\n        <\/button>\n\n\n                <ul class=\"nomargin collapse show\" id=\"collapseExample1\">\n            <li><\/li><li>Lean software development treats anything that doesn&#8217;t add value for the customer as waste worth removing.<\/li><li>The Poppendiecks published two versions of the seven principles, and most write-ups quietly mix them together.<\/li><li>Seven wastes are named in the software version, not eight the eighth comes from manufacturing.<\/li><li>Lean isn&#8217;t an alternative to Agile; it&#8217;s a way of thinking you run inside it.<\/li><li>Cycle time, work in progress, and flow efficiency tell you whether lean is actually working.<\/li><li>Lean fails when leadership wants the vocabulary without giving teams authority to stop bad work.<\/li>        <\/ul>\n            <\/div>\n    \n<p>Your team is fully booked. Everyone has something assigned, nobody looks idle, and the release date has moved twice anyway. That&#8217;s rarely a speed problem. It&#8217;s a queue problem: work sitting still in between the people touching it.<\/p>\n<p>Lean software development is a way of running delivery built around exactly that observation. It treats anything that doesn&#8217;t add value for the customer as waste, then removes it,\u00a0 starting with the waiting. Mary and Tom Poppendieck adapted it from the Toyota Production System in 2003, giving software seven principles and seven named wastes.<\/p>\n<p>This guide covers both published versions of the lean principles. Then the seven wastes, the process, the benefits worth expecting, how lean sits against Agile, when lean is and isn&#8217;t the right call, and the metrics that tell you whether any of it is working.<\/p>\n<h1>What Is Lean Software Development?<\/h1>\n<p>Lean software development applies Toyota Production System thinking to building software. It treats anything that doesn&#8217;t add customer value as waste, then removes it systematically. Mary and Tom Poppendieck published it in 2003 as a set of principles rather than a process.<\/p>\n<p>That last part matters, because lean gives you no standup, no board, no ceremony, and no role called Lean Master. It&#8217;s a lens you point at your delivery pipeline, which is why the best <a href=\"https:\/\/www.tekrevol.com\/custom-software-development\">software development company<\/a> almost always runs it inside something else; usually Kanban, occasionally Scrum.<\/p>\n<h3>Lean Delivery is Not Lean Startup<\/h3>\n<p>These get confused constantly, and they answer different questions.<\/p>\n<p>The lean approach asks: <i>are we building this efficiently?<\/i> It optimises the delivery system: flow, waste, cycle time, quality. It assumes you roughly know what to build.<\/p>\n<p>Lean Startup, Eric Ries&#8217;s 2011 book, asks: <i>should we be building this at all?<\/i> Its remedy is an experiment, not a value stream map. If you&#8217;re validating a product idea rather than fixing delivery, that&#8217;s the<a href=\"https:\/\/www.tekrevol.com\/lean-startup-plan\"> lean startup<\/a> end of things.<\/p>\n<p>Both descend from lean manufacturing, and neither is a substitute for the other.<\/p>\n    <div class=\"new-single-blog-cta\"\n        style=\"background-image: url('https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/05\/new-temp-cta-back.webp');\">\n        <div class=\"new-single-blog-cta-content\">\n            <h2 class=\"cta-heading\">\n                Delivery Slower Than It Should Be?                <span class=\"highlight\"><\/span>\n            <\/h2>\n            <p class=\"cta-desc\">\n                Send us your process, and we&#039;ll show you where the work is actually sitting.            <\/p>\n            <a href=\"javascript:void(0);\" data-bs-toggle=\"modal\"\n                data-bs-target=\"#single_modalpopup\" class=\"cta-button text-decoration-none\">\n                Schedule Your Free Consultation            <\/a>\n        <\/div>\n    <\/div>\n    \n<h2>What Are the 7 Principles of Lean Software Development?<\/h2>\n<p>The Poppendiecks published seven principles in 2003 and revised the wording and order in 2006. Both lists are legitimate.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-29998 size-full\" src=\"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1.webp\" alt=\"Lean Principle\" width=\"2250\" height=\"1145\" srcset=\"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1.webp 2250w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1-300x153.webp 300w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1-1024x521.webp 1024w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1-768x391.webp 768w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1-1536x782.webp 1536w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1-2048x1042.webp 2048w\" sizes=\"auto, (max-width: 2250px) 100vw, 2250px\" \/><\/p>\n<p>Here is what each book actually says, taken from the published chapter listings.<\/p>\n<table class=\"newtable-layout\">\n<tbody>\n<tr style=\"background-color: #ffa500;\">\n<td>2003 \u2014 <i>Lean Software Development: An Agile Toolkit<\/i><\/td>\n<td>2006 \u2014 <i>Implementing Lean Software Development<\/i><\/td>\n<\/tr>\n<tr>\n<td>Eliminate Waste<\/td>\n<td>Eliminate Waste<\/td>\n<\/tr>\n<tr>\n<td>Amplify Learning<\/td>\n<td>Build Quality In<\/td>\n<\/tr>\n<tr>\n<td>Decide as Late as Possible<\/td>\n<td>Create Knowledge<\/td>\n<\/tr>\n<tr>\n<td>Deliver as Fast as Possible<\/td>\n<td>Defer Commitment<\/td>\n<\/tr>\n<tr>\n<td>Empower the Team<\/td>\n<td>Deliver Fast<\/td>\n<\/tr>\n<tr>\n<td>Build Integrity In<\/td>\n<td>Respect People<\/td>\n<\/tr>\n<tr>\n<td>See the Whole<\/td>\n<td>Optimize the Whole<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>What each principle actually asks of you<\/h3>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Eliminate waste:<\/strong> Find work that doesn&#8217;t help the customer and stop doing it. The seven named wastes below are the checklist.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Amplify learning \/create knowledge<\/strong>: Software development is a learning process, not a manufacturing one. Short cycles, working code in front of users, and decisions recorded so nobody relearns them next quarter.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Decide as late as possible \/ defer commitment<\/strong>. Keep options open until the cost of waiting exceeds the cost of being wrong.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Deliver as fast as possible \/ deliver fast.<\/strong> Speed isn&#8217;t the goal, feedback is. You can&#8217;t learn from something you haven&#8217;t shipped.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Empower the team\/respect people<\/strong>. The people doing the work decide how the work gets done.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Build integrity in\/build quality in.<\/strong> Alongside testing and refactoring, the 2003 version covers <i>perceived<\/i> integrity, meaning the system feels coherent to users, and <i>conceptual<\/i> integrity, meaning its parts fit together. The 2006 renaming narrows it toward quality built in continuously rather than inspected at the end.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>See the whole \/ optimize the whole.<\/strong> Optimise end to end, not department by department. A design team hitting every deadline while releases sit in a queue isn&#8217;t a win.<\/li>\n<\/ol>\n<h2>What Are the 7 Wastes of Lean Software Development?<\/h2>\n<p>In the 2003 version, they are partially done work, extra features, relearning, handoffs, task switching, delays, and defects. The Poppendiecks mapped each to a manufacturing waste, then renamed three and reassigned two others in 2006.<\/p>\n<table class=\"newtable-layout\">\n<tbody>\n<tr style=\"background-color: #ffa500;\">\n<td>Manufacturing waste<\/td>\n<td>Software waste (2003)<\/td>\n<td>Renamed (2006)<\/td>\n<\/tr>\n<tr>\n<td>In-process inventory<\/td>\n<td>Partially done work<\/td>\n<td>Partially done work<\/td>\n<\/tr>\n<tr>\n<td>Over-production<\/td>\n<td>Extra features<\/td>\n<td>Extra features<\/td>\n<\/tr>\n<tr>\n<td>Extra processing<\/td>\n<td>Extra processes<\/td>\n<td>Relearning<\/td>\n<\/tr>\n<tr>\n<td>Transportation<\/td>\n<td>Task switching<\/td>\n<td>Handoffs<\/td>\n<\/tr>\n<tr>\n<td>Motion<\/td>\n<td>Motion<\/td>\n<td>Task switching<\/td>\n<\/tr>\n<tr>\n<td>Waiting<\/td>\n<td>Waiting<\/td>\n<td>Delays<\/td>\n<\/tr>\n<tr>\n<td>Defects<\/td>\n<td>Defects<\/td>\n<td>Defects<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>What each one looks like on a real project, using the 2006 names with the 2003 equivalent in brackets:<\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Partially done work:<\/strong> code written but not merged, features built but not released, a branch nobody&#8217;s touched in three weeks. It carries risk and delivers nothing.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Extra features:<\/strong> anything built because someone might want it. Every unused feature costs you again at every future change.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Relearning (2003: extra processes):<\/strong> a decision made in March, undocumented, re-argued in September. Also every time a developer rediscovers how a subsystem works.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Handoffs (2003: task switching):<\/strong> each transfer between people loses the unwritten context. Three handoffs and the original intent is gone.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Task switching (2003: motion):<\/strong> a developer on three projects isn&#8217;t giving each a third. Context reload costs real time on every switch.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Delays (2003: waiting):<\/strong> waiting for an approval, an environment, a decision, a review. On most projects we map, this is the biggest single block of elapsed time.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Defects:<\/strong> the cost isn&#8217;t the fix, it&#8217;s the interruption and the rework of everything built on top of the bug.<\/li>\n<\/ul>\n    <div class=\"callout\">\n        <span class=\"cl\"><\/span>\n        <div class=\"callout-content\">\n            The eighth waste is real and worth caring about. Under-using your engineers&#8217; judgement is genuinely wasteful, and it&#8217;s the same idea as &#8220;respect people.&#8221; It just isn&#8217;t part of the Poppendieck framework. If you cite eight, cite them to lean manufacturing.        <\/div>\n    <\/div>\n    \n<h2>Benefits of Lean Software Development<\/h2>\n<p>The real lean software development benefits are shorter cycle times, fewer defects reaching production, less money spent on features nobody uses, and a delivery process you can actually see. They come from removing waiting, not from working faster.<\/p>\n<p>Worth separating what lean gives you from why it gives it to you, because the mechanism is what tells you whether you&#8217;ll get it.<\/p>\n<table class=\"newtable-layout\">\n<tbody>\n<tr style=\"background-color: #ffa500;\">\n<td>Benefit<\/td>\n<td>What actually causes it<\/td>\n<td>How you&#8217;d know<\/td>\n<\/tr>\n<tr>\n<td>Faster delivery<\/td>\n<td>Lower work in progress, shorter queues<\/td>\n<td>Cycle time falls while throughput holds<\/td>\n<\/tr>\n<tr>\n<td>Lower cost<\/td>\n<td>Fewer features built speculatively<\/td>\n<td>Backlog shrinks without complaints<\/td>\n<\/tr>\n<tr>\n<td>Fewer defects<\/td>\n<td>Quality built in continuously, not inspected at the end<\/td>\n<td>Change failure rate drops<\/td>\n<\/tr>\n<tr>\n<td>Better decisions<\/td>\n<td>Commitments deferred until evidence exists<\/td>\n<td>Fewer reversals mid-build<\/td>\n<\/tr>\n<tr>\n<td>Less rework<\/td>\n<td>Fewer handoffs, so less context lost<\/td>\n<td>Fewer &#8220;that&#8217;s not what we meant&#8221; moments<\/td>\n<\/tr>\n<tr>\n<td>Visible delivery<\/td>\n<td>Work on a board with limits and ageing<\/td>\n<td>You can name today&#8217;s blocker without asking<\/td>\n<\/tr>\n<tr>\n<td>Happier teams<\/td>\n<td>Authority to stop bad work<\/td>\n<td>Retention, and fewer heroic weekends<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>One benefit that gets undersold:<\/strong> lean makes bad news arrive early. Short cycles and small batches mean a wrong assumption surfaces in week two rather than month five, which is the cheapest possible time to find it.<\/p>\n    <div class=\"callout\">\n        <span class=\"cl\"><\/span>\n        <div class=\"callout-content\">\n            That&#8217;s the pattern behind Stop Vaping Challenge. Behaviour change can&#8217;t be specified accurately upfront, so the tracking, streaks and leaderboard shipped small and got refined against how people actually used them. The app reports a 65% success rate in its first six months, an outcome you reach by learning from real usage.        <\/div>\n    <\/div>\n    \n<h2>Lean vs Agile: What&#8217;s the Actual Difference?<\/h2>\n<p>Lean is the older, broader philosophy, and the Poppendieck approach is a style of Agile rather than a rival to it. Martin Fowler put it plainly in 2008: &#8220;You don&#8217;t do agile <i>or<\/i> lean; you do agile <i>and<\/i> lean.&#8221;<\/p>\n<p>The chronology settles most of the argument. Toyota&#8217;s system predates the Agile Manifesto by roughly fifty years. But the Poppendiecks&#8217; 2003 book is subtitled <i>An Agile Toolkit<\/i>, shipped in an Agile book series, and carries forewords by two Agile Manifesto signatories.<\/p>\n<table class=\"newtable-layout\">\n<tbody>\n<tr style=\"background-color: #ffa500;\">\n<td><\/td>\n<td>Lean<\/td>\n<td>Agile<\/td>\n<\/tr>\n<tr>\n<td>Origin<\/td>\n<td>Toyota Production System, adapted 2003<\/td>\n<td>Agile Manifesto, 2001<\/td>\n<\/tr>\n<tr>\n<td>Optimises for<\/td>\n<td>End-to-end flow of value<\/td>\n<td>Responsiveness to change<\/td>\n<\/tr>\n<tr>\n<td>Unit of analysis<\/td>\n<td>The whole value stream, including work outside the team<\/td>\n<td>The team and its iteration<\/td>\n<\/tr>\n<tr>\n<td>Gives you<\/td>\n<td>Principles and thinking tools<\/td>\n<td>Values, plus frameworks like Scrum and XP<\/td>\n<\/tr>\n<tr>\n<td>Core question<\/td>\n<td>Where is work sitting still?<\/td>\n<td>Are we building the right thing this sprint?<\/td>\n<\/tr>\n<tr>\n<td>Typical practice<\/td>\n<td>Value stream mapping, WIP limits, pull systems<\/td>\n<td>Sprints, standups, retrospectives, backlogs<\/td>\n<\/tr>\n<tr>\n<td>Ceremonies<\/td>\n<td>None of its own<\/td>\n<td>Several, depending on framework<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>The practical difference:<\/strong> Agile improves what happens inside a team&#8217;s iteration. Lean pushes you to look at everything on either side of it. That&#8217;s why lean work tends to cross departments while Agile work usually doesn&#8217;t. We cover the full landscape in software development methodologies.<\/p>\n<h2>When Should You Go For Lean Software Development?<\/h2>\n<h2><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-29999 size-full\" src=\"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-3.webp\" alt=\"Go lean , think twice\" width=\"2250\" height=\"1145\" srcset=\"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-3.webp 2250w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-3-300x153.webp 300w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-3-1024x521.webp 1024w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-3-768x391.webp 768w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-3-1536x782.webp 1536w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-3-2048x1042.webp 2048w\" sizes=\"auto, (max-width: 2250px) 100vw, 2250px\" \/><\/h2>\n<p>Choose lean when work waits more than it moves, when scope keeps growing, or when handoffs are losing context. Skip it when your contract fixes scope upfront, when compliance mandates documentation lean would call waste, or when your team is too small to have queues.<\/p>\n<table class=\"newtable-layout\">\n<tbody>\n<tr style=\"background-color: #ffa500;\">\n<td>Go lean when<\/td>\n<td>Think twice when<\/td>\n<\/tr>\n<tr>\n<td>Delivery feels slow despite everyone being busy<\/td>\n<td>Scope and price are both fixed in the contract<\/td>\n<\/tr>\n<tr>\n<td>Work sits in review, QA or approval queues<\/td>\n<td>You&#8217;re in medical, aviation or automotive, where required documentation isn&#8217;t optional<\/td>\n<\/tr>\n<tr>\n<td>The backlog grows faster than it clears<\/td>\n<td>The team is three people; you don&#8217;t have enough queueing to analyse<\/td>\n<\/tr>\n<tr>\n<td>Features ship that nobody uses<\/td>\n<td>Leadership won&#8217;t devolve decisions to the team<\/td>\n<\/tr>\n<tr>\n<td>Multiple teams hand work between them<\/td>\n<td>The product is a one-off with no second release<\/td>\n<\/tr>\n<tr>\n<td>You&#8217;re running Kanban already<\/td>\n<td>You need a prescriptive framework with defined roles<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Two of those deserve expanding, because they&#8217;re the ones that sink lean adoptions.<\/p>\n<p><strong>Fixed-scope, fixed-price contracts:<\/strong> &#8220;Decide as late as possible&#8221; and a signed scope document fight each other, and the contract wins. Worth checking against your custom software development terms before you commit to either.<\/p>\n<p><strong>Organisations that won&#8217;t devolve decisions:<\/strong> If a developer can&#8217;t halt work they know is wrong, you have the vocabulary of lean and none of the mechanism. It&#8217;s the hardest condition to meet and the one that decides whether the rest holds.<\/p>\n    <div class=\"new-single-blog-cta\"\n        style=\"background-image: url('https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/05\/new-temp-cta-back.webp');\">\n        <div class=\"new-single-blog-cta-content\">\n            <h2 class=\"cta-heading\">\n                Building with a Fixed-Scope Contract?                <span class=\"highlight\"><\/span>\n            <\/h2>\n            <p class=\"cta-desc\">\n                Tell us the terms and we&#039;ll show you which lean practices survive them.            <\/p>\n            <a href=\"javascript:void(0);\" data-bs-toggle=\"modal\"\n                data-bs-target=\"#single_modalpopup\" class=\"cta-button text-decoration-none\">\n                Consult Our Strategy Team            <\/a>\n        <\/div>\n    <\/div>\n    \n<h2>What Is the Lean Software Development Process?<\/h2>\n<p>The process runs five steps borrowed from Womack and Jones: identify value, map the value stream, create flow, establish pull, then pursue perfection. Applied to software, that means defining done from the customer&#8217;s side and attacking whatever makes work wait.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-29997 size-full\" src=\"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2.webp\" alt=\"Lean Software development porcess\" width=\"2250\" height=\"1145\" srcset=\"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2.webp 2250w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-300x153.webp 300w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1024x521.webp 1024w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-768x391.webp 768w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-1536x782.webp 1536w, https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/image-2-2048x1042.webp 2048w\" sizes=\"auto, (max-width: 2250px) 100vw, 2250px\" \/><\/p>\n<p>Those five come from <i>Lean Thinking<\/i> (1996), not from the Poppendieck books. The seven principles tell you what to believe; these five tell you what to do on Monday.<\/p>\n<h3>1. Identify Value<\/h3>\n<p>Define value from the customer&#8217;s side, not the delivery team&#8217;s. A feature isn&#8217;t valuable because it was on the roadmap. Write down what the user can now do that they couldn&#8217;t before.<\/p>\n<h3>2. Map the Value Stream<\/h3>\n<p>Follow one real feature from request to production. Write down every step, every handoff, and how long each waited. Most teams we do this with are surprised by how little of the elapsed time was anyone working.<\/p>\n<h3>3. Create Flow<\/h3>\n<p>Remove whatever makes work stop. Usually that&#8217;s a review bottleneck, an environment queue, or an approval sitting with one person. Attack the longest wait, not the longest task.<\/p>\n<h3>4. Establish Pull<\/h3>\n<p>Work gets started when there&#8217;s capacity to finish it, not when it arrives. In practice that&#8217;s a work-in-progress limit. Pick a number below what you&#8217;re carrying now and hold it. It feels wrong for a fortnight, then cycle time starts dropping.<\/p>\n<h3>5. Pursue Perfection<\/h3>\n<p>Re-map, re-measure, repeat. Lean isn&#8217;t a project with an end date; it&#8217;s a habit of looking at your own pipeline.<\/p>\n    <div class=\"callout\">\n        <span class=\"cl\"><\/span>\n        <div class=\"callout-content\">\n            Steps three and four are where our <a href=\"https:\/\/www.tekrevol.com\/case-studies\/alhussaini\">Al Hussaini<\/a> rebuild earned its keep. Rather than one launch, the work ran as assess, strategise, rebuild, then extend. Each stage shipped something usable before the next started, so 40+ physical retail outlets came onto the platform in waves instead of all at once on a single risky date.        <\/div>\n    <\/div>\n    \n<h2>Does AI-Assisted Coding Help or Hurt Lean Delivery?<\/h2>\n<p>Both, and which one depends on your review capacity. AI generates code faster than teams can review, test, and release it, so it can remove the waste of writing while multiplying partially done work, rework, and queues downstream.<\/p>\n<p>Generation speed isn&#8217;t the constraint on most delivery pipelines, but review, testing, and the release window are. Speeding up the one step that wasn&#8217;t the bottleneck is a textbook local optimisation, which is exactly what &#8220;see the whole&#8221; warns against.<\/p>\n<p>DORA&#8217;s 2025 research found AI adoption had a positive relationship with delivery throughput and a negative with delivery stability.<\/p>\n<p>Three lean-consistent ways to use it:<\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Attack relearning.<\/strong> AI is genuinely good at explaining unfamiliar code, which is one of the seven wastes.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Watch your WIP.<\/strong> If everyone&#8217;s generating more, cap open work harder, not looser.<\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><strong>Measure flow efficiency before and after.<\/strong> If cycle time didn&#8217;t move, the speed went into the queue rather than to the customer.<\/li>\n<\/ul>\n<h2>How TekRevol Runs Lean Software Development<\/h2>\n<p>We apply lean software development methodology to change your outcome: scope discipline, small releases, and short queues, and we&#8217;re upfront about the parts a fixed-price contract makes impossible. The contract shape decides how lean a project can be, and we settle that before the estimate.<\/p>\n<p>Three things specific to running lean with an outside team.<\/p>\n<p>The Poppendiecks give contracts their own thinking tool. A signed, fixed scope makes &#8220;decide as late as possible&#8221; a breach of contract rather than good practice. So we scope a firm outcome with a flexible feature set, which lets late learning change what gets built instead of triggering a change order.<\/p>\n<p>In discovery, we mark what ships now, what waits for evidence, and what we&#8217;d argue against, with the reasoning written down so the decision doesn&#8217;t get relearned in month four.<\/p>\n<p>You also get flow numbers rather than a velocity chart: cycle time, work in progress, and where items are actually waiting. If your work is sitting in review or blocked on an approval from your side, you&#8217;ll see that. So will you when the queue is ours.<\/p>\n    <div class=\"new-single-blog-cta\"\n        style=\"background-image: url('https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/05\/new-temp-cta-back.webp');\">\n        <div class=\"new-single-blog-cta-content\">\n            <h2 class=\"cta-heading\">\n                Want Your Delivery Queues Measured?                <span class=\"highlight\"><\/span>\n            <\/h2>\n            <p class=\"cta-desc\">\n                Send us your last three releases, and we&#039;ll map where the time actually went.            <\/p>\n            <a href=\"javascript:void(0);\" data-bs-toggle=\"modal\"\n                data-bs-target=\"#single_modalpopup\" class=\"cta-button text-decoration-none\">\n                Consult Our Experts            <\/a>\n        <\/div>\n    <\/div>\n    \n","protected":false},"excerpt":{"rendered":"<p>Your team is fully booked. Everyone has something assigned, nobody looks idle, and the release date has moved twice anyway. That&#8217;s rarely a speed problem. It&#8217;s a queue problem: work sitting still in between the people touching it. Lean software&#8230;<\/p>\n","protected":false},"author":223,"featured_media":30057,"comment_status":"closed","ping_status":"open","sticky":false,"template":"single-post.php","format":"standard","meta":{"footnotes":""},"categories":[907],"tags":[],"class_list":["post-29993","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-app-development"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v24.3 (Yoast SEO v27.7) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Lean Software Development: Principles &amp; Process Explained<\/title>\n<meta name=\"description\" content=\"Lean software development guide explaining the 7 principles, wastes, process, benefits, agile vs lean difference, when to use it, and the metrics.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Lean Software Development: Principles &amp; How to Run It\" \/>\n<meta property=\"og:description\" content=\"Lean software development guide explaining the 7 principles, wastes, process, benefits, agile vs lean difference, when to use it, and the metrics.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/\" \/>\n<meta property=\"og:site_name\" content=\"TekRevol\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/TekRevolOfficial\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-11T13:16:55+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/Lean-Software-Development.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1728\" \/>\n\t<meta property=\"og:image:height\" content=\"910\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Adeel Sabzali\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@tekrevol\" \/>\n<meta name=\"twitter:site\" content=\"@tekrevol\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Adeel Sabzali\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"TechArticle\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/\"},\"author\":{\"name\":\"Adeel Sabzali\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#\\\/schema\\\/person\\\/fc122464d707debf43ee4c855f342de1\"},\"headline\":\"Lean Software Development: Principles &#038; How to Run It\",\"datePublished\":\"2026-08-11T13:16:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/\"},\"wordCount\":2531,\"publisher\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2026\\\/08\\\/Lean-Software-Development.webp\",\"articleSection\":[\"App Development\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/\",\"url\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/\",\"name\":\"Lean Software Development: Principles & Process Explained\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2026\\\/08\\\/Lean-Software-Development.webp\",\"datePublished\":\"2026-08-11T13:16:55+00:00\",\"description\":\"Lean software development guide explaining the 7 principles, wastes, process, benefits, agile vs lean difference, when to use it, and the metrics.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/#primaryimage\",\"url\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2026\\\/08\\\/Lean-Software-Development.webp\",\"contentUrl\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2026\\\/08\\\/Lean-Software-Development.webp\",\"width\":1728,\"height\":910,\"caption\":\"Lean Software Development\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/lean-software-development\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Lean Software Development: Principles &#038; How to Run It\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#website\",\"url\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/\",\"name\":\"TekRevol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#organization\",\"name\":\"TekRevol\",\"url\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2023\\\/11\\\/logo-1.png\",\"contentUrl\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2023\\\/11\\\/logo-1.png\",\"width\":200,\"height\":200,\"caption\":\"TekRevol\"},\"image\":{\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/TekRevolOfficial\\\/\",\"https:\\\/\\\/x.com\\\/tekrevol\",\"https:\\\/\\\/www.instagram.com\\\/tekrevol\\\/\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UCuweDx9zWc2ket4n4QLUbNQ\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/#\\\/schema\\\/person\\\/fc122464d707debf43ee4c855f342de1\",\"name\":\"Adeel Sabzali\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2025\\\/03\\\/unnamed-1-150x150.jpg\",\"url\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2025\\\/03\\\/unnamed-1-150x150.jpg\",\"contentUrl\":\"https:\\\/\\\/d3r5yd0374231.cloudfront.net\\\/images-tek\\\/uploads\\\/2025\\\/03\\\/unnamed-1-150x150.jpg\",\"caption\":\"Adeel Sabzali\"},\"description\":\"Adeel Sabzali is a Senior Full Stack Developer and Team Lead at Tekrevol with over 9 years of experience building high-performance web and mobile solutions. He specializes in Node.js, Laravel, React.js, and React Native, with strong expertise in cloud infrastructure and scalable architecture. A trusted technical leader, Adeel mentors development teams and delivers projects with precision and purpose.\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/adeel-sabzali\\\/\"],\"jobTitle\":\"Senior Full Stack Developer\",\"url\":\"https:\\\/\\\/www.tekrevol.com\\\/blogs\\\/author\\\/adeel\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Lean Software Development: Principles & Process Explained","description":"Lean software development guide explaining the 7 principles, wastes, process, benefits, agile vs lean difference, when to use it, and the metrics.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/","og_locale":"en_US","og_type":"article","og_title":"Lean Software Development: Principles & How to Run It","og_description":"Lean software development guide explaining the 7 principles, wastes, process, benefits, agile vs lean difference, when to use it, and the metrics.","og_url":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/","og_site_name":"TekRevol","article_publisher":"https:\/\/www.facebook.com\/TekRevolOfficial\/","article_published_time":"2026-08-11T13:16:55+00:00","og_image":[{"width":1728,"height":910,"url":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/Lean-Software-Development.webp","type":"image\/webp"}],"author":"Adeel Sabzali","twitter_card":"summary_large_image","twitter_creator":"@tekrevol","twitter_site":"@tekrevol","twitter_misc":{"Written by":"Adeel Sabzali","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"TechArticle","@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/#article","isPartOf":{"@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/"},"author":{"name":"Adeel Sabzali","@id":"https:\/\/www.tekrevol.com\/blogs\/#\/schema\/person\/fc122464d707debf43ee4c855f342de1"},"headline":"Lean Software Development: Principles &#038; How to Run It","datePublished":"2026-08-11T13:16:55+00:00","mainEntityOfPage":{"@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/"},"wordCount":2531,"publisher":{"@id":"https:\/\/www.tekrevol.com\/blogs\/#organization"},"image":{"@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/#primaryimage"},"thumbnailUrl":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/Lean-Software-Development.webp","articleSection":["App Development"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/","url":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/","name":"Lean Software Development: Principles & Process Explained","isPartOf":{"@id":"https:\/\/www.tekrevol.com\/blogs\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/#primaryimage"},"image":{"@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/#primaryimage"},"thumbnailUrl":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/Lean-Software-Development.webp","datePublished":"2026-08-11T13:16:55+00:00","description":"Lean software development guide explaining the 7 principles, wastes, process, benefits, agile vs lean difference, when to use it, and the metrics.","breadcrumb":{"@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/#primaryimage","url":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/Lean-Software-Development.webp","contentUrl":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2026\/08\/Lean-Software-Development.webp","width":1728,"height":910,"caption":"Lean Software Development"},{"@type":"BreadcrumbList","@id":"https:\/\/www.tekrevol.com\/blogs\/lean-software-development\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.tekrevol.com\/blogs\/"},{"@type":"ListItem","position":2,"name":"Lean Software Development: Principles &#038; How to Run It"}]},{"@type":"WebSite","@id":"https:\/\/www.tekrevol.com\/blogs\/#website","url":"https:\/\/www.tekrevol.com\/blogs\/","name":"TekRevol","description":"","publisher":{"@id":"https:\/\/www.tekrevol.com\/blogs\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.tekrevol.com\/blogs\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.tekrevol.com\/blogs\/#organization","name":"TekRevol","url":"https:\/\/www.tekrevol.com\/blogs\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.tekrevol.com\/blogs\/#\/schema\/logo\/image\/","url":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2023\/11\/logo-1.png","contentUrl":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2023\/11\/logo-1.png","width":200,"height":200,"caption":"TekRevol"},"image":{"@id":"https:\/\/www.tekrevol.com\/blogs\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/TekRevolOfficial\/","https:\/\/x.com\/tekrevol","https:\/\/www.instagram.com\/tekrevol\/","https:\/\/www.youtube.com\/channel\/UCuweDx9zWc2ket4n4QLUbNQ"]},{"@type":"Person","@id":"https:\/\/www.tekrevol.com\/blogs\/#\/schema\/person\/fc122464d707debf43ee4c855f342de1","name":"Adeel Sabzali","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2025\/03\/unnamed-1-150x150.jpg","url":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2025\/03\/unnamed-1-150x150.jpg","contentUrl":"https:\/\/d3r5yd0374231.cloudfront.net\/images-tek\/uploads\/2025\/03\/unnamed-1-150x150.jpg","caption":"Adeel Sabzali"},"description":"Adeel Sabzali is a Senior Full Stack Developer and Team Lead at Tekrevol with over 9 years of experience building high-performance web and mobile solutions. He specializes in Node.js, Laravel, React.js, and React Native, with strong expertise in cloud infrastructure and scalable architecture. A trusted technical leader, Adeel mentors development teams and delivers projects with precision and purpose.","sameAs":["https:\/\/www.linkedin.com\/in\/adeel-sabzali\/"],"jobTitle":"Senior Full Stack Developer","url":"https:\/\/www.tekrevol.com\/blogs\/author\/adeel\/"}]}},"_links":{"self":[{"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/posts\/29993","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/users\/223"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/comments?post=29993"}],"version-history":[{"count":7,"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/posts\/29993\/revisions"}],"predecessor-version":[{"id":30055,"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/posts\/29993\/revisions\/30055"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/media\/30057"}],"wp:attachment":[{"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/media?parent=29993"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/categories?post=29993"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tekrevol.com\/blogs\/wp-json\/wp\/v2\/tags?post=29993"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}