Understanding Agile Methodologies in Tech

Since I’m already burying Change Management today, make some room for Agile… 😄 Agile is dead. There, I said it. Once a brilliant workaround for rigid bureaucracies and inflexible leadership, Agile allowed teams to collaborate quickly and effectively. But somewhere along the way, it got lost. Here’s why I believe Agile failed: 1️⃣ It became a checklist. What started as a mindset turned into a rigid process. Standups, sprints, and backlogs became meaningless rituals, with teams focusing on going through the motions instead of embracing Agile’s core values. 2️⃣ Scaling without culture. Organizations scaled Agile frameworks like SAFe without addressing cultural issues, creating more bureaucracy instead of the flexibility Agile was meant to foster. 3️⃣ Speed over value. Teams rushed to deliver “something” quickly, but often it wasn’t what mattered. Activity replaced impact, and Agile became busywork. 4️⃣ Leadership resistance. Agile demands trust and autonomy, but many managers aren’t ready to give up control. Without their buy-in, teams struggled to make it work. 5️⃣ Consulting overkill. Consultants saw the business and turned Agile into a product, overselling it as a miracle cure and a sort of also failing Change Management, which it isn't. 6️⃣ Ignoring the human factor. Agile pushed teams to deliver at breakneck speed without addressing well-being or trust. Burnout followed, and engagement plummeted. The lesson? Agile didn’t fail on its own—it was sabotaged by poor leadership, misinterpretation, and an obsession with process over people. True change begins with something simpler than Agile or any framework: authentic leadership asks employees the one question that really matters: “How are you?” It’s time to leave behind miracle tools and focus on the mindsets and cultures that create lasting #transformation.

“Yesterday I worked on X. Today I’ll work on Y. No blockers.” Translation: “We’re filling airtime, not moving work forward.” If this sounds like your daily standup, you don’t have a delivery team. You have a synchronized reporting ritual. 🛑 Status updates belong in your tools. 🚀 Standups are for removing friction — fast. Your job as a leader isn’t to quiz people on what they did. It’s to surface blockers, enable flow, and keep focus sharp. Here’s what real standup follow-ups sound like: “...and we deployed, but no one’s using it. Kill it?” “...ran into unexpected complexity. I’m rewriting a smaller slice. Is that okay?” “...got stuck. Pairing helped, but now we’re both late. Abort or adapt?” Those are the conversations that change the work. Want better standups? 🔥 Ban status updates. 🔥 Focus on friction. 🔥 Lead for momentum. What’s one blocker you cleared in a standup that saved your week? P.S. In case you're wondering what to do when there's no blockers: You can skip the standup.

I’ve been working as a contractual Program/Project Manager on complex projects for the past 7 years, most of which followed Agile methodologies. While the Software Development Life Cycle (SDLC) is designed to reduce risk, poor implementation can have the opposite effect. If not executed properly, it significantly increases the risk of project failure. Here’s a quick ranking of critical failure points that commonly derail software projects: 🔴 1. Unclear or Changing Requirements Poorly defined needs or constant scope changes break alignment early and often. ✅ Fix: Involve stakeholders early, use user stories and clarify DoD (definition of done), and validate frequently; another advice: make sure to define change request in the initial contract with the client. 🔴 2. Inadequate Planning & Estimation Unrealistic timelines or budgets create pressure that leads to shortcuts and burnout. ✅ Fix: Buffer for unknowns, involve tech leads in estimation. 🟠 3. Ineffective Communication Team silos and misalignment cause costly rework and delays. ✅ Fix: Daily stand-ups, shared documentation, clear ownership. The tech team needs to understand the functional requirement to be able to implement it technically. 🟠 4. Weak Design & Architecture Hasty or shortsighted technical decisions lead to rework and scalability issues. ✅ Fix: Involving a software architect who could support drafting the best scalable architecture choices within the available projects needs, constraints and budget 🟠 5. Insufficient Testing & QA Testing cut short = bugs in production, bad UX, security holes. ✅ Fix: Invest in a QA strategy to identify tests to be run by type of release, and automate critical time-consuming tests 🟡 6. Lack of Stakeholder Involvement Software built in isolation rarely meets business goals. ✅ Fix: Demo regularly (ideally after each milestone), build feedback into the cycle. 🟡 7. Poor Change & Config Management Inconsistent environments and chaotic updates derail progress. ✅ Fix: Version control, CI/CD, and clear change protocols. 🟡 8. Inadequate Risk Management Unexpected issues become blockers when risks aren't flagged early. ✅ Fix: Ongoing risk logs, contingency planning. 🟢 9. Neglecting Post-Launch Support No plan for support = user churn and poor adoption. ✅ Fix: Monitor performance, address issues fast. 🟢 10. Lack of DevOps & Automation Manual processes delay releases and increase error rates. ✅ Fix: Embrace CI/CD and infrastructure-as-code. Strong software isn’t just about great code—it’s about clarity, communication, and continuous feedback. A strong Project Manager implements the right processes and follows each step methodically to spot weak links early and address them proactively. And when issues do arise (as they often do), they stay calm, communicate transparently, and ensure all stakeholders remain aligned throughout the journey. #SoftwareDevelopment #SDLC #TechLeadership #ProjectManagement #Agile #DevOps #ProductDelivery

𝗔𝗴𝗶𝗹𝗲 𝗱𝗶𝗱 𝗻𝗼𝘁 𝘀𝘁𝗮𝗹𝗹 𝗮𝘁 𝘁𝗲𝗮𝗺 𝗹𝗲𝘃𝗲𝗹. 𝗜𝘁 𝗿𝗲𝗮𝗰𝗵𝗲𝗱 𝗮 𝗹𝗶𝗺𝗶𝘁 𝗮𝘁 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽. Recently, I joined a panel on the 𝗠𝗮𝗻𝗶𝗳𝗲𝘀𝘁𝗼 𝗳𝗼𝗿 𝗘𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗔𝗴𝗶𝗹𝗶𝘁𝘆 alongside Lenka Pincot PMP, PfMP, PMI-ACP, PMI-PBA, Heidi Musser, and Jon Ward. The focus was not on frameworks or scaling models, but on how organisations actually make decisions, set priorities, and deliver value. I’ve written a new article: 𝗘𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗔𝗴𝗶𝗹𝗶𝘁𝘆 𝗜𝘀 𝗡𝗼𝘁 𝗮 𝗧𝗲𝗮𝗺 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 — 𝗜𝘁’𝘀 𝗮 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗢𝗻𝗲 One question shaped the discussion. Why does progress stall once Agile moves beyond teams? Teams have improved. Delivery has improved. Yet many organisations still struggle to translate that into consistent outcomes. The issue is not the capability inside teams. It is how the organisation is run around them. Agile never redesigned decision-making, funding, or prioritisation at the leadership level. Many organisations scaled team practices without changing those elements. Teams are pushed to move faster, while decisions stay slow and priorities remain unclear. That creates activity without a consistent impact. The shift in conversation is telling. Leaders are no longer asking about Scrum or ceremonies. They are asking about value, speed, and risk. That is where the real constraint sits. From a CIO perspective, the pattern is familiar. Too many priorities, slow decision-making, limited visibility into outcomes, and misalignment among teams, funding, and strategy. These are structural issues, not delivery ones. The unit of change is no longer the team. It is the organisation. Leadership behaviour, decision-making, and how value flows all need to evolve together. AI is making this visible. Faster execution exposes slow decisions and misalignment very quickly. That is increasing pressure on leadership to fix the system, not just the symptoms. The article goes deeper into what this means in practice and what leaders can do differently starting Monday morning. Link: https://lnkd.in/eBcRqjAH Where do you see the biggest constraint today, teams or leadership systems? #EnterpriseAgility #Leadership #CIO #CTO #BusinessAgility #Transformation #AI #OperatingModel

Most sprint planning meetings fail for one reason: They focus on tasks… not clarity. Here’s how high-performing Agile teams actually run Sprint Planning 👇 Agile Sprint Planning (Step-by-Step) 1. Define Sprint Goal • Product Owner explains business goal • Align on why this sprint matters 👉 Without a clear goal, sprint becomes a task list 2. Review Product Backlog • Focus on top priority items • Clarify requirements 👉 If stories are unclear, stop here and fix them 3. Capacity Planning • Check team availability • Understand realistic workload 👉 Overcommitment kills sprint success 4. Select User Stories • Pick stories based on priority + capacity 👉 Not everything important fits in one sprint 5. Break into Tasks • Divide stories into small actionable tasks 👉 Smaller tasks = better tracking + fewer surprises 6. Estimate Effort • Use story points • Align as a team 👉 Estimation is about shared understanding, not accuracy 7. Discuss Dependencies & Risks • Identify blockers early • Align on external dependencies 👉 Risks ignored in planning become issues in execution 8. Sprint Commitment • Team commits to delivery 👉 Commitment should be realistic, not optimistic 9. Sprint Starts • Development begins • Daily standups drive progress Business Analyst Role (Critical but underrated) • Clarify requirements • Bridge business and tech • Answer real-time questions • Ensure everyone has the same understanding 👉 Clarity in planning = speed in execution Golden Insight Sprint Planning is not about filling capacity. It’s about creating confidence in delivery. Business Analyst Perspective If your sprint keeps slipping… Don’t blame execution. Fix your planning. What’s the biggest challenge you face during sprint planning?

Real Sprint Planning: How Scrum Masters Actually Calculate Capacity, Velocity & Estimation — The Kiran Way People often talk theory… but let’s look at a real scenario Scrum Masters handle every sprint. Here’s a practical example from a 2-week sprint (10 working days) with 10 team members 👇 🧠 1️⃣ Step 1: Calculate Real Capacity (Hours) Total possible hours 10 members × 8 hrs × 10 days = 800 hrs Subtract leaves • Member A → 2 days off = 16 hrs • Member B → 3 days off = 24 hrs Leaves total = 40 hrs Subtract buffers • Tech Debt = 10% of remaining hours • Meetings / Support = 10% (760 × 20% = 152 hrs) 🔹 Real usable capacity 800 – 40 – 152 = 608 hrs This is the actual energy your team has for the sprint. 📈 2️⃣ Step 2: Connect Capacity With Velocity Last 3 sprints delivered: • 38 SP • 42 SP • 40 SP Average Velocity = 40 Story Points With ~600 hrs usable, this matches perfectly with your expected 40 SP commitment. 🧩 3️⃣ Step 3: Add Work Based on Estimation Now: • Bring refined backlog • Select stories supporting the Sprint Goal • Stop when you reach ~40 SP or ~608 hrs This is how you avoid overloading the sprint. 🔥 Kiran Way Summary ✔ Capacity = actual hours available ✔ Velocity = actual delivery capability ✔ Estimation = actual effort required When you match these three, sprint planning becomes predictable, calm, and value-focused — not a guessing game. 👉 How does your team calculate Sprint Capacity — hours, points, or both? #Agile #Scrum #ScrumMaster #SprintPlanning #Velocity #CapacityPlanning #AgileCoach #ProjectManagement #DeliveryExcellence #Estimation #AgileMindset #ContinuousImprovement

Daily standups are NOT status meetings. Your team hates standups because you're doing them wrong. I've seen this in 47 out of 50 teams I've coached: → The Scrum Master asks, "What did you do yesterday?" → Everyone reports to the SM like it's a performance review → The meeting drags on for 30 minutes → Nobody listens to anyone else Here's what actually works: ☑ Team members talk TO each other, not to you ☑ Focus on blockers and collaboration, not updates ☑ Keep it under 15 minutes (set a timer) ☑ Stand in a circle so everyone can see everyone in physical meetings. If it's onlineee Zoom/google meet will keep everyone in a room (Keeping the camera ONNN should be must in that case... to see each other in the meeting.) The standup is for the TEAM to synchronise. Not for YOU to track progress, That's what Jira is for. with 3 questions in Stand-up: “What’s blocking me?” “What can I help with?” “Are we on track to deliver value?” Tip: Next stand-up, start with: 👉 “Who needs help right now?” You’ll instantly shift from status to synergy. 90 Seconds for an individual member in the team. The stand-up went from 15 minutes of noise → 8 minutes of clarity. PS: If your standup takes more than 15 minutes, you're doing project management, not Scrum. ♻️ Repost and share if your team needs to see this.

There's a sad phenomenon I've observed in so many organisations: they proudly declare themselves agile, yet somehow end up running waterfall in disguise. The gap between management expectations and engineering reality keeps widening, and I've been trying to understand why. It often starts innocently enough. Leadership embraces agile terminology but struggles to let go of traditional command structures. They want the benefits of agility (speed, innovation, adaptability) whilst maintaining the comfort of detailed roadmaps and fixed deadlines. Meanwhile, engineering teams start with genuine enthusiasm for agile practices, only to find themselves executing predetermined plans with little room for iteration or learning. The disconnect grows gradually. Management asks for commitment to specific features months in advance. Engineering agrees, hoping to maintain some flexibility. When changes inevitably arise or estimates prove wrong, trust erodes on both sides. Management sees a team that can't deliver on promises. Engineering sees leadership that doesn't understand the realities of software development. What fascinates me is how both sides retreat to their comfort zones when stressed. Management tightens control, demanding more detailed plans and status reports. Engineering becomes defensive, feeling reduced to order takers rather than problem solvers. The resentment builds quietly but steadily. The tragedy is that both sides want the same thing: successful products delivered efficiently. But without genuine understanding and trust, the gap becomes a chasm. Management wonders why their "agile" teams can't seem to deliver reliably. Engineering wonders why they're doing waterfall with extra meetings. Breaking this cycle requires courage from both sides. Leadership needs to truly embrace uncertainty and empower teams. Engineering needs to communicate challenges early and often. Most importantly, both need to acknowledge that real agility isn't about following a methodology; it's about creating an environment where adaptation and learning are valued over rigid adherence to plans. When what flows down the organisational hierarchy is orders rather than intent, this divide will never truly heal. Until leaders share the 'why' and trust teams with the 'how', we're just playing agile theatre. #agile theatre #agilesoftwaredevelopment is not #waterfall in disguise #softwaredevelopment #softwareengineering #leadership #softwaremanagement

At ZoomInfo, I stopped running weekly C-suite meetings. Like most enterprise orgs, they were failing in obvious ways and so we replaced them with something else... A daily 1-hour meeting with my full exec team. Weekly exec meetings can fail in several predictable ways: - Problems had 6–7 days to grow before anyone talks about them - They become political - execs pre-align in side conversations, then show up “aligned”. They’d say things like “I’ve already talked to James about this…” as a way to avoid the proper back and forth new initiatives deserve. - The meeting itself becomes this performative theatre of head nodding By the time issues showed up, they were harder and more expensive to fix. So we tried something new. Our daily standup has hard rules: Same execs, every weekday, anyone can add a topic to the agenda, no slides and DEFINITELY no pre-alignment. And we got rid of all standing 1:1s between execs. If our CMO and our CRO had a topic that had to be discussed, the daily standup was where to do it. (If you were executing on an initiative together that meeting was fine to continue) And we only cover four things: 1) What are the metrics on the key initiatives we are running? 2) What’s blocked right now? 3) What decision actually needs to be made? 4) What’s coming down the pipe that requires cross-functional coordination - no surprises? My favorite part about this is our weekly standup would fill about 30 minutes - and we’d be out of topics. Now, every 1 hour, daily meeting goes the full hour, every time. And it became the end of "getting up to speed", “we’ll take that offline” or “Oh my goodness, I didn’t know that was happening?!?” at ZoomInfo! After that, a couple of things happened almost immediately: First, issues showed up earlier - you can’t hide for a week when you’re checking in every day. Second, accountability became clearer. If inputs didn’t change and progress didn’t happen fast - and everyone could see who was responsible. Third, everyone had context for everything that was happening - every important decision was front and center for everyone to see and be a part of. If you've got other ideas for improving communication in large orgs, I'm listening.

The Real Reason Agile is silently "Dying" in Most Companies Everyone talks about Agile transformation. Thousands of hours spent. Millions spent on certifications. Scrum boards. Standups. "Agile coaches." Jira everywhere. And yet... Nothing really changed. Because we adopted the process, but not the "Mindset". Renamed meetings to "Daily Standup" — but kept micromanaging. Introduced sprints — but still demanded scope changes every mid-sprint. Wrote user stories — but still treated developers like order takers. Hired Agile coaches — but didn't empower teams to actually own decisions. Result - Engineers see Agile as a process overhead instead of a framework to innovate & fail-fast. Agile was never about ceremonies or tools. It was about trust, autonomy, and outcomes over outputs. The truth? Most companies didn't fail to adopt Agile. They rebranded Waterfall and kept marching. Agile didn't fail. We failed Agile. It's not dead. It’s just waiting for the companies brave enough to actually use it. #Agile #Leadership #ProductDevelopment #MindsetMatters #Transformation