<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Stack 83</title><link>https://www.stack83.com/blog/</link><description>Recent content in Blog on Stack 83</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.stack83.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>A Year of Agents, Measured in the Git Log</title><link>https://www.stack83.com/blog/a-year-of-agents-in-the-git-log/</link><pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/a-year-of-agents-in-the-git-log/</guid><description>&lt;p&gt;Everyone who builds with coding agents has an opinion about how much they help. I had one too. Then I realised the answer was sitting in my git history, and that it would be more useful to count than to guess.&lt;/p&gt;&#10;&lt;p&gt;So I counted. Every repository I touched in 2026, from the &lt;a href="https://www.stack83.com/blog/building-koppa-laravel-flutter-kubernetes/"&gt;Koppa&lt;/a&gt; platform down to a one-page marketing site. This post is what the log says, including the parts I would rather it didn&amp;rsquo;t.&lt;/p&gt;</description></item><item><title>Recursive Self-Improvement: The Loop That Improves Itself</title><link>https://www.stack83.com/blog/recursive-self-improvement/</link><pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/recursive-self-improvement/</guid><description>&lt;p&gt;Most improvement is linear. You fix a bug, the product is slightly better, and tomorrow you fix the next one at the same speed.&lt;/p&gt;&#10;&lt;p&gt;Recursive self-improvement is different. It is improvement that &lt;strong&gt;makes the next round of improvement faster&lt;/strong&gt;. The system doesn&amp;rsquo;t just get better. It gets better at getting better.&lt;/p&gt;&#10;&lt;p&gt;That idea has a dramatic version, which hasn&amp;rsquo;t happened, and a modest version, which is quietly happening on my laptop and in every good engineering team I&amp;rsquo;ve worked with. This post is about both, and about what the modest one means if you own a product.&lt;/p&gt;</description></item><item><title>Feedback Loops: Keep Them Short and Fast</title><link>https://www.stack83.com/blog/feedback-loops-short-and-fast/</link><pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/feedback-loops-short-and-fast/</guid><description>&lt;h2 id="the-loop-is-the-product-process"&gt;The loop is the product process&lt;/h2&gt;&#10;&lt;p&gt;Every decision a team makes is a guess. The feedback loop is what turns that guess into knowledge: you do something, reality answers, you adjust.&lt;/p&gt;&#10;&lt;p&gt;The only variable that really matters is &lt;strong&gt;how long that answer takes&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;A team with a two-hour loop and a team with a two-month loop are not doing the same job at different speeds. They are playing different games. One of them corrects course twenty times before the other hears anything back.&lt;/p&gt;</description></item><item><title>Building Koppa: Laravel, Flutter and Kubernetes at Scale</title><link>https://www.stack83.com/blog/building-koppa-laravel-flutter-kubernetes/</link><pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/building-koppa-laravel-flutter-kubernetes/</guid><description>&lt;p&gt;Most of what I write here is about product. This one is about the code.&lt;/p&gt;&#10;&lt;p&gt;I founded &lt;a href="https://www.stack83.com/projects/gokoppa/"&gt;Koppa&lt;/a&gt; in 2018 to build fantasy sports games — Fantasy Football and Fantasy Cycling, plus white-label versions for clients who want their own branded pool. It has since signed up &lt;strong&gt;more than 150,000 registered users across 15+ countries&lt;/strong&gt;. I designed the architecture, wrote most of the code, and I still operate it.&lt;/p&gt;&#10;&lt;p&gt;That last part matters. Running your own software for years is the fastest way to find out which of your architectural opinions were correct and which were just fashionable. Here&amp;rsquo;s the honest version.&lt;/p&gt;</description></item><item><title>You Already Understand How AI Thinks</title><link>https://www.stack83.com/blog/probabilities-ai-and-everyday-decisions/</link><pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/probabilities-ai-and-everyday-decisions/</guid><description>&lt;h2 id="youve-been-doing-this-your-whole-life"&gt;You&amp;rsquo;ve been doing this your whole life&lt;/h2&gt;&#10;&lt;p&gt;Think back to high school maths. Probability. The chance something happens. A coin flip: 50/50. Rolling a six: 1 in 6. Drawing a red card: half the deck.&lt;/p&gt;&#10;&lt;p&gt;It felt abstract at the time. Something you calculated for exams and then forgot.&lt;/p&gt;&#10;&lt;p&gt;Except you didn&amp;rsquo;t forget it. You just stopped calling it probability.&lt;/p&gt;&#10;&lt;p&gt;Every day, dozens of times a day, you make decisions based on likelihood:&lt;/p&gt;</description></item><item><title>Vibe Coding</title><link>https://www.stack83.com/blog/vibe-coding/</link><pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/vibe-coding/</guid><description>&lt;p&gt;There&amp;rsquo;s a specific feeling that&amp;rsquo;s hard to describe. You open your editor, you have a rough idea, and then — almost without thinking — something starts to take shape. You&amp;rsquo;re not grinding through syntax or fighting documentation. You&amp;rsquo;re just&amp;hellip; building. Brewing. Flowing.&lt;/p&gt;&#10;&lt;p&gt;That&amp;rsquo;s vibe coding. And I am completely hooked.&lt;/p&gt;&#10;&lt;h2 id="what-even-is-vibe-coding"&gt;What even is vibe coding?&lt;/h2&gt;&#10;&lt;p&gt;The term gets thrown around loosely, but at its core, vibe coding is what happens when AI handles the mechanical friction of programming — and you get to stay in the idea space. You describe what you want, you react to what appears, you steer, you refine. It&amp;rsquo;s less like writing code and more like having a conversation with a very capable collaborator who never gets tired and never judges your ideas.&lt;/p&gt;</description></item><item><title>Signal-to-Noise Ratio for Product Managers</title><link>https://www.stack83.com/blog/signal-to-noise-ratio-for-product-managers/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/signal-to-noise-ratio-for-product-managers/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;Product managers operate in an environment saturated with information. Every day brings new feature requests, stakeholder opinions, analytics dashboards, and customer feedback. Some of it is valuable. Much of it is distraction.&lt;/p&gt;&#10;&lt;p&gt;The engineering concept of signal-to-noise ratio (SNR) offers a useful metaphor: the relationship between meaningful information (signal) and irrelevant or distracting input (noise). For product owners and managers, success depends on consistently increasing this ratio — amplifying what matters and filtering out what does not.&lt;/p&gt;</description></item><item><title>AI and AGI</title><link>https://www.stack83.com/blog/ai-and-agi/</link><pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/ai-and-agi/</guid><description>&lt;h2 id="ai-powerful-but-narrow"&gt;AI: powerful, but narrow&lt;/h2&gt;&#10;&lt;p&gt;Artificial Intelligence (AI) has quietly become part of our everyday lives. From recommendation engines on Netflix and Spotify to spam filters, chatbots, image recognition, and fraud detection — most modern software products rely on some form of AI.&lt;/p&gt;&#10;&lt;p&gt;However, almost all AI we use today is &lt;strong&gt;narrow AI&lt;/strong&gt; (also called &lt;em&gt;weak AI&lt;/em&gt;). These systems are trained to perform &lt;strong&gt;one specific task&lt;/strong&gt; extremely well:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;A model that recognizes faces cannot translate text.&lt;/li&gt;&#10;&lt;li&gt;A chess engine cannot drive a car.&lt;/li&gt;&#10;&lt;li&gt;A large language model can generate text but does not truly &lt;em&gt;understand&lt;/em&gt; the world.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Narrow AI excels because it is optimized, data-driven, and constrained. This makes it incredibly valuable for businesses — but also fundamentally limited.&lt;/p&gt;</description></item><item><title>Table-Top Definition — The Driver’s License for Feature Teams</title><link>https://www.stack83.com/blog/tabletop-definition-drivers-license/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/tabletop-definition-drivers-license/</guid><description>&lt;p&gt;Modern DevOps and cloud organizations increasingly push toward &lt;strong&gt;full end-to-end product ownership&lt;/strong&gt;. Teams build it, deploy it, observe it, secure it, and run it.&lt;/p&gt;&#10;&lt;p&gt;But there’s a recurring problem:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Everyone claims they’re ready — until the first incident happens.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;Tools alone don’t guarantee readiness.&lt;br&gt;&#10;Training alone doesn’t create capability.&lt;br&gt;&#10;Autonomy without guardrails doesn’t scale.&lt;/p&gt;&#10;&lt;p&gt;That’s where the concept of a &lt;strong&gt;Table-Top Definition&lt;/strong&gt; comes in — a structured, practical way to define what “ready” truly means before a team becomes accountable for production environments.&lt;/p&gt;</description></item><item><title>RTFM First. Then Ask.</title><link>https://www.stack83.com/blog/rtfm-first-then-ask/</link><pubDate>Mon, 03 Nov 2025 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/rtfm-first-then-ask/</guid><description>&lt;h2 id="-rtfm-first-then-come-to-me"&gt;🤦‍♂️ RTFM First. &lt;em&gt;Then&lt;/em&gt; Come to Me.&lt;/h2&gt;&#10;&lt;p&gt;There’s a sacred ritual in technology teams — ancient, powerful, and ignored daily:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;RTFM.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;Polite version: &lt;em&gt;Read The Friendly Manual.&lt;/em&gt;&lt;br&gt;&#10;Real version: you already know.&lt;/p&gt;&#10;&lt;p&gt;It isn’t rude.&lt;br&gt;&#10;It’s &lt;strong&gt;self-defense&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;h3 id="-the-corporate-reality"&gt;🧠 The Corporate Reality&lt;/h3&gt;&#10;&lt;p&gt;Every tech org has two types of people:&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Group A:&lt;/strong&gt;&lt;br&gt;&#10;Reads docs, checks logs, Googles, tests things, sometimes cries quietly but &lt;em&gt;figures it out.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Group B:&lt;/strong&gt;&lt;br&gt;&#10;Sends messages like:&lt;/p&gt;</description></item><item><title>MCP Servers: What They Are and Why Organisations Need Them</title><link>https://www.stack83.com/blog/mcp-servers-what-they-are-and-why-organisations-need-them/</link><pubDate>Thu, 02 Oct 2025 08:23:20 +0000</pubDate><guid>https://www.stack83.com/blog/mcp-servers-what-they-are-and-why-organisations-need-them/</guid><description>&lt;h2 id="what-is-an-mcp-server"&gt;What is an MCP server?&lt;/h2&gt;&#10;&lt;p&gt;“MCP” stands for &lt;strong&gt;Model Context Protocol&lt;/strong&gt; — an open standard introduced in late 2024 to unify how AI systems (especially large language models, or LLMs) interface with external tools, systems, and data sources.&lt;/p&gt;&#10;&lt;p&gt;An &lt;strong&gt;MCP server&lt;/strong&gt; acts as a bridge. It exposes capabilities (like database queries, file storage, API calls, or domain-specific logic) in a standardized way so AI agents (the clients) can call them consistently and securely.&lt;/p&gt;</description></item><item><title>Network Model Layers: OSI vs TCP/IP Explained</title><link>https://www.stack83.com/blog/network-model-layers/</link><pubDate>Fri, 15 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/network-model-layers/</guid><description>&lt;p&gt;In networking, &lt;strong&gt;layered models&lt;/strong&gt; provide a structured way to understand how data moves from one device to another. Two models dominate this space: the &lt;strong&gt;OSI model&lt;/strong&gt; and the &lt;strong&gt;TCP/IP model&lt;/strong&gt;.&lt;br&gt;&#10;In this post, we’ll break them down, compare their layers, and show how they apply to modern IT and DevOps workflows.&lt;/p&gt;&#10;&lt;h2 id="why-network-model-layers-matter"&gt;Why Network Model Layers Matter&lt;/h2&gt;&#10;&lt;p&gt;When communication is split into layers, it’s easier to:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Design&lt;/strong&gt; networks with modular components&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Diagnose&lt;/strong&gt; issues by isolating them to a specific layer&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Ensure&lt;/strong&gt; interoperability between systems and vendors&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="the-osi-model-7-layers"&gt;The OSI Model (7 Layers)&lt;/h2&gt;&#10;&lt;p&gt;The &lt;strong&gt;Open Systems Interconnection&lt;/strong&gt; model is conceptual and consists of:&lt;/p&gt;</description></item><item><title>RTO vs RPO: The Difference Every CTO Must Understand</title><link>https://www.stack83.com/blog/rto-vs-rpo-the-difference-every-cto-must-understand/</link><pubDate>Fri, 18 Jul 2025 20:12:45 +0000</pubDate><guid>https://www.stack83.com/blog/rto-vs-rpo-the-difference-every-cto-must-understand/</guid><description>&lt;h2 id="rto-vs-rpo-the-difference-every-cto-must-understand"&gt;RTO vs RPO: The Difference Every CTO Must Understand&lt;/h2&gt;&#10;&lt;p&gt;When disaster strikes—whether it&amp;rsquo;s a system crash, a cyberattack, or a cloud outage—&lt;strong&gt;how fast can you recover&lt;/strong&gt;, and &lt;strong&gt;how much data are you willing to lose&lt;/strong&gt;?&lt;/p&gt;&#10;&lt;p&gt;These questions are answered by two key metrics in disaster recovery planning: &lt;strong&gt;RTO&lt;/strong&gt; (Recovery Time Objective) and &lt;strong&gt;RPO&lt;/strong&gt; (Recovery Point Objective). They&amp;rsquo;re often misunderstood, but aligning your business and technical teams around these definitions is essential for building resilient systems.&lt;/p&gt;</description></item><item><title>ClickOps: What It Is, Why It Happens, and How to Move Beyond It</title><link>https://www.stack83.com/blog/clickops-what-it-is-why-it-happens-and-how-to-move-beyond-it/</link><pubDate>Thu, 03 Jul 2025 08:23:20 +0000</pubDate><guid>https://www.stack83.com/blog/clickops-what-it-is-why-it-happens-and-how-to-move-beyond-it/</guid><description>&lt;p&gt;&lt;strong&gt;ClickOps&lt;/strong&gt; is a term that’s gained traction in the DevOps and cloud engineering world. It refers to managing infrastructure or services by clicking through a graphical user interface (GUI), rather than defining resources using code (Infrastructure as Code, or IaC). While ClickOps can be useful in certain situations, it often comes with risks that teams should understand — and plan to mitigate.&lt;/p&gt;&#10;&lt;p&gt;In this article, we’ll break down what ClickOps means, why it happens, and how to evolve toward more maintainable, scalable practices.&lt;/p&gt;</description></item><item><title>MVP vs MLP vs MMP: What's the Difference and When to Use Each?</title><link>https://www.stack83.com/blog/mvp-mlp-mmp/</link><pubDate>Thu, 24 Apr 2025 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/mvp-mlp-mmp/</guid><description>&lt;p&gt;If you&amp;rsquo;re building products, chances are you&amp;rsquo;ve come across the terms MVP, MLP, and MMP. These acronyms are often confused, but each serves a unique purpose in the product lifecycle. In this article, we’ll break down what each one means, how they differ, and when to use them.&lt;/p&gt;&#10;&lt;h2 id="what-is-an-mvp-minimum-viable-product"&gt;What is an MVP (Minimum Viable Product)?&lt;/h2&gt;&#10;&lt;p&gt;An MVP is the most basic version of a product that can still deliver value to users. The goal is to get something functional into the hands of real users as fast as possible to learn from their behavior and feedback.&lt;/p&gt;</description></item><item><title>The Best Steve Jobs Quotes</title><link>https://www.stack83.com/blog/best-steve-jobs-quotes-for-creators/</link><pubDate>Wed, 16 Apr 2025 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/best-steve-jobs-quotes-for-creators/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;Steve Jobs didn’t just build beautiful products — he shaped the way we think about creativity, quality, and leadership. His words, like his work, were minimalist but powerful. For creators, builders, and product-minded professionals, his quotes are more than inspirational—they’re practical principles.&lt;/p&gt;&#10;&lt;p&gt;Below is a curated selection of Steve Jobs quotes that continue to guide how I think, design, and build at &lt;a href="https://www.stack83.com/"&gt;Stack83&lt;/a&gt;. These aren’t just words—they’re philosophies in motion.&lt;/p&gt;</description></item><item><title>Understanding Prompt Engineering</title><link>https://www.stack83.com/blog/understanding-prompt-engineering/</link><pubDate>Tue, 03 Dec 2024 14:44:20 +0000</pubDate><guid>https://www.stack83.com/blog/understanding-prompt-engineering/</guid><description>&lt;p&gt;In the ever-evolving field of artificial intelligence, few concepts have gained as much attention as &lt;strong&gt;prompt engineering&lt;/strong&gt;. But what exactly is prompt engineering, and why is it being hailed as a critical skill in the AI era? Inspired by &lt;a href="https://www.mckinsey.com/featured-insights/mckinsey-explainers/what-is-prompt-engineering"&gt;McKinsey&amp;rsquo;s explainer&lt;/a&gt;, let’s break it down.&lt;/p&gt;&#10;&lt;h2 id="what-is-prompt-engineering"&gt;What Is Prompt Engineering?&lt;/h2&gt;&#10;&lt;p&gt;At its core, &lt;strong&gt;prompt engineering&lt;/strong&gt; is the process of designing inputs—called prompts—to achieve desired outputs from generative AI systems like GPT-4. These systems work by interpreting and responding to the text input they are given. The better your prompt, the more useful and accurate the response.&lt;/p&gt;</description></item><item><title>CI/CD Pipelines for Agile Teams</title><link>https://www.stack83.com/blog/ci-cd-pipelines-for-agile-teams/</link><pubDate>Thu, 21 Nov 2024 20:46:46 +0000</pubDate><guid>https://www.stack83.com/blog/ci-cd-pipelines-for-agile-teams/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;Continuous Integration (CI) and Continuous Deployment (CD) are key practices in modern software development. They automate code integration, testing, and deployment, enabling faster and more reliable releases. These practices align perfectly with Agile methodologies, which emphasize delivering value incrementally and adapting to feedback.&lt;/p&gt;&#10;&lt;p&gt;In this article, we&amp;rsquo;ll explore how Agile teams can implement CI/CD pipelines to streamline their workflows, improve collaboration, and enhance software quality.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="what-is-cicd"&gt;What is CI/CD?&lt;/h2&gt;&#10;&lt;h3 id="continuous-integration-ci"&gt;Continuous Integration (CI)&lt;/h3&gt;&#10;&lt;p&gt;CI involves automatically integrating code changes into a shared repository multiple times a day. This practice ensures that the codebase remains stable and minimizes integration conflicts.&lt;/p&gt;</description></item><item><title>Platform Engineer Explained</title><link>https://www.stack83.com/blog/platform-engineer-explained/</link><pubDate>Wed, 23 Oct 2024 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/platform-engineer-explained/</guid><description>&lt;p&gt;In today’s fast-evolving software development landscape, the role of a Platform Engineer has become increasingly crucial. Companies are shifting toward cloud-native architectures, microservices, and DevOps practices, all of which demand new ways to build and manage infrastructure. This is where the Platform Engineer steps in, providing the backbone that enables development teams to focus on delivering business value. But what exactly does a Platform Engineer do, and why is their role so pivotal?&lt;/p&gt;</description></item><item><title>The Importance of DevOps for Modern Organizations</title><link>https://www.stack83.com/blog/the-importance-of-devops-for-modern-organizations/</link><pubDate>Mon, 15 Jul 2024 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/the-importance-of-devops-for-modern-organizations/</guid><description>&lt;p&gt;In today&amp;rsquo;s fast-paced digital landscape, staying competitive requires businesses to adopt innovative practices that streamline operations and enhance productivity. One such practice is DevOps, a set of practices that combines software development (Dev) and IT operations (Ops). This approach aims to shorten the development lifecycle and provide continuous delivery with high software quality. As a freelance product owner with a passion for DevOps, I have witnessed firsthand how these practices can transform an organization&amp;rsquo;s efficiency and success. Here&amp;rsquo;s why DevOps is crucial for modern organizations.&lt;/p&gt;</description></item><item><title>Why Scrum Matters for Your Company</title><link>https://www.stack83.com/blog/why-scrum-matters-for-your-company/</link><pubDate>Tue, 14 Nov 2023 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/why-scrum-matters-for-your-company/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;In the ever-evolving landscape of business and project management, companies are constantly on the lookout for strategies and methodologies that can help them achieve greater efficiency, higher quality, and improved collaboration. One such methodology that has gained immense popularity in recent years is Scrum. In this article, we will delve into why Scrum makes a significant difference for a company, and how implementing Scrum principles can lead to transformative changes in your organization.&lt;/p&gt;</description></item><item><title>Mastering the Art of Cloud Migration</title><link>https://www.stack83.com/blog/mastering-the-art-of-cloud-migration/</link><pubDate>Fri, 25 Aug 2023 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/mastering-the-art-of-cloud-migration/</guid><description>&lt;p&gt;Migrating to the cloud is more than just a tech trend; it&amp;rsquo;s a business imperative. With a myriad of benefits such as scalability, cost-efficiency, and access to specialized services, cloud environments like AWS, Azure, and GCP offer compelling options. In this article, we&amp;rsquo;ll explore comprehensive migration strategies that are applicable to any cloud provider.&lt;/p&gt;&#10;&lt;h2 id="why-migrate-to-the-cloud"&gt;Why Migrate to the Cloud?&lt;/h2&gt;&#10;&lt;p&gt;Before taking the plunge, it&amp;rsquo;s essential to define your objectives. Are you looking for scalability, cost-efficiency, or access to specialized cloud services? A &lt;a href="https://www.gartner.com/"&gt;study by Gartner&lt;/a&gt; suggests that businesses are increasingly moving to the cloud for reasons ranging from cost savings to increased agility.&lt;/p&gt;</description></item><item><title>Stakeholder Management</title><link>https://www.stack83.com/blog/stakeholder-management/</link><pubDate>Wed, 19 Jul 2023 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/stakeholder-management/</guid><description>&lt;p&gt;Stakeholder management is a crucial aspect of any project or business initiative. It involves identifying, understanding, communicating, and effectively collaborating with all stakeholders who can influence the success of a project. Managing these stakeholders requires a thoughtful approach and skillful communication to foster mutual understanding and engagement. In this blog article, we will share valuable tips and experiences to help you effectively communicate with and manage stakeholders to achieve sustainable success.&lt;/p&gt;</description></item><item><title>Product Owner Basics</title><link>https://www.stack83.com/blog/product-owner-basics/</link><pubDate>Wed, 10 May 2023 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/product-owner-basics/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;The role of a Product Owner is vital in Agile software development, serving as a critical link between the development team, stakeholders, and customers. In this blog post, we&amp;rsquo;ll explore the basics of the Product Owner role, its responsibilities, and how it fits within an Agile team.&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;What is a Product Owner?&lt;/strong&gt; A Product Owner (PO) is a key member of an Agile team, responsible for defining, prioritizing, and validating the product&amp;rsquo;s requirements. The PO serves as the voice of the customer and ensures that the development team delivers the right features and functionalities to meet the user&amp;rsquo;s needs. They work closely with stakeholders and the development team to maximize the product&amp;rsquo;s value and achieve the desired outcome.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Responsibilities of a Product Owner&lt;/strong&gt;: The Product Owner&amp;rsquo;s responsibilities can be broadly divided into four categories:&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;a. &lt;strong&gt;Defining and Refining the Product Vision&lt;/strong&gt;: The PO is responsible for crafting a clear and compelling vision for the product, ensuring that it aligns with the overall organizational goals. This vision serves as a guide for the entire Agile team, helping them understand the product&amp;rsquo;s purpose and direction.&lt;/p&gt;</description></item><item><title>Product Backlog Prioritization</title><link>https://www.stack83.com/blog/product-backlog-prioritization/</link><pubDate>Sat, 11 Mar 2023 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/product-backlog-prioritization/</guid><description>&lt;p&gt;Product backlog prioritization is a crucial aspect of agile software development. It involves the process of identifying and ordering the most important product features or requirements based on the value they provide to the business and the customer. Prioritizing the backlog is essential to ensure that the development team is working on the most important and valuable items first. In this article, we will discuss some of the most popular product backlog prioritization techniques used in agile development.&lt;/p&gt;</description></item><item><title>The Agile Manifesto</title><link>https://www.stack83.com/blog/the-agile-manifesto/</link><pubDate>Tue, 05 Oct 2021 00:00:00 +0000</pubDate><guid>https://www.stack83.com/blog/the-agile-manifesto/</guid><description>&lt;p&gt;The &lt;a href="https://agilemanifesto.org/"&gt;Agile Manifesto&lt;/a&gt; is one of the things I believe in and apply on a daily basis working as a freelance product manager. The Agile Manifesto was published nearly 20 years ago and was created by 17 software developers who came together during a ski trip while discussing the problems of the software industry coming up with solutions. Hence, the Agile Manifesto was born.&lt;/p&gt;&#10;&lt;h2 id="but-what-is-it"&gt;But, what is it?&lt;/h2&gt;&#10;&lt;p&gt;The Agile Manifesto represents four agile values and twelve principles for agile software development.&lt;/p&gt;</description></item></channel></rss>