Implementing Agile Methodologies for Teams

It’s been 23 years since the Agile Manifesto was written and honestly, it’s been looking dated for a while now. For example, can anyone really still argue that working software is the primary measurement of progress anymore? So, for funsies, I asked ChatGPT to write a new manifesto, based on everything the industry has learned since the publication and honestly… it’s not perfect, but it’s pretty good for only 1 prompt. **Modern Agile Manifesto 2024:** **Values:** 1. **Outcomes Over Outputs** **(Focus on delivering value and impact rather than just shipping features)** 2. **Collaboration Over Silos** **(Empower cross-functional teams and diverse perspectives rather than isolated expertise)** 3. **Adaptability Over Rigidity** **(Embrace continuous learning and evolution rather than strict adherence to plans)** 4. **Sustainability Over Burnout** **(Prioritise well-being, work-life balance, and sustainable pace rather than pushing for short-term gains)** **Principles:** 1. **Deliver Value Continuously:** Deliver small, valuable increments frequently to keep feedback loops short and drive continuous improvement. 2. **Customer-Centric Design:** Engage customers and stakeholders throughout the process to ensure the product meets real needs. 3. **Build Resilient and Adaptable Systems:** Design software and processes that are resilient to change and adaptable to evolving requirements. 4. **Foster a Learning Culture:** Encourage continuous learning, experimentation, and improvement within teams and organisations. 5. **Empower Teams:** Give teams the autonomy to make decisions, encouraging ownership and accountability. 6. **Promote Diversity and Inclusion:** Recognise and leverage diverse perspectives to enhance creativity and problem-solving. 7. **Transparency and Trust:** Cultivate a culture of openness, where information is shared freely and trust is built through transparency. 8. **Simplify and Focus:** Strive for simplicity in design and execution, focusing on what truly matters and avoiding unnecessary complexity. 9. **Prioritise Sustainable Work Practices:** Balance delivering value with maintaining a sustainable pace to ensure long-term productivity and well-being. 10. **Measure What Matters:** Use meaningful metrics that reflect progress towards desired outcomes rather than vanity metrics. 11. **Adapt to Feedback:** Actively seek out and adapt to feedback from customers, stakeholders, and team members to continuously improve. 12. **Lead with Empathy:** Practice empathetic leadership, understanding and addressing the needs and challenges of the team and customers.

Scrum as a Service: When Agile Teams Become Ticket Processors Scrum as a Service is when Agile teams are execution units, taking orders instead of owning value delivery. They don’t solve problems; or shaping the product, they just code and close Jira issues. It’s what happens when companies adopt Scrum mechanically but keep traditional thinking and control structures intact. Symptoms of Scrum as a Service 1) No Product Ownership The PO is a backlog manager, not a decision-maker. Teams can’t challenge priorities. The backlog is a job assignment queue. Sprint Planning is a scheduling exercise, not a conversation about functional or technical trade-offs. 2) No Cross-Discipline Collaboration UX, DevOps, and Security exist outside the team, creating slow handoffs. Developers get fully fleshed-out requirements, not problems to solve. Agile teams are ticket processors, not value creators. 3) Nothing Changes Daily Scrums become status meetings for managers. Retros don’t lead to improvements, just performance reviews. Teams are judged by team outputs like velocity, not business outcomes. How This Happens 1) No Organizational Change Leadership keeps command and control, just renaming old roles. 2) Waterfall Thinking Teams have fixed scope and deadlines, no room for continuous discovery or progressive elaboration. 3) POs as Middlemen, Not Leaders POs relay stakeholder demands instead of shaping product strategy. 4) SMs are Managers. Not Coaches SMs push teams to move faster rather than helping them achieve a sustainable pace. How to Fix It 1) Give Teams Ownership Let teams define and prioritize their backlog. Facilitate direct feedback loops with users, not just stakeholder requests. Make POs strategic leaders, not order-takers. 2) Tear Down Silos Embed UX, DevOps, QA, and Security into the Scrum team. Stop treating devs as coders for hire. Make them coequal partners in product thinking. 3) Shift to Outcome Metrics Stop measuring success by velocity, throughput, or tickets. Track customer impact, retention, usability, and product adoption. Ask: Are we solving problems or just releasing code? 4) Decentralize Decision-Making Replace top-down roadmaps with team-driven prioritization. Let teams influence scope, trade-offs, and release planning. Encourage teams to experiment and innovate. 5) Foster Continuous Improvement Make retros actionable. Give teams time for technical excellence, like refactoring, automation, and innovation. Shift from feature delivery to sustainable, high-quality product development. From Execution Teams to Product Teams Scrum teams should be value creators, not feature factories. Agile is meant to empower teams, not turn them into Jira clerks. If teams can’t challenge priorities, shape solutions, adjust processes, or innovate, then you don’t have Agile. You have Scrum as a Service. Does your organization trust teams to own the product? If not, Scrum isn’t the problem. Your structure is.

A group of people isn't a team. Until they have trust. After 25 years of working with leaders, I've learned this: Trust isn't a given.  It's earned. Slowly.  Methodically. With each interaction.  With every hard choice. Some leaders get there intuitively.  The best ones build it intentionally. Here's their blueprint: PILLAR 1: CHARACTER TRUST (Integrity) Without integrity, nothing else matters. • Do what you say you'll do • Take radical ownership of mistakes • Be honest even when it's uncomfortable • Make decisions based on principles, not politics PILLAR 2: CAPABILITY TRUST (Competence) Respect follows competence. • Demonstrate you know what you're talking about • Choose problems that advance the mission • Make good decisions under pressure • Deliver results, not just stories PILLAR 3: CONSISTENCY TRUST (Reliability) Consistency compounds momentum. • Build reliable patterns your team can count on • Follow through on commitments repeatedly • Codify your reliability with systems • React calmly under stress PILLAR 4: CONNECTION TRUST (Relatability) People follow leaders they feel connected to. • Care about their success, not just their output • Understand what motivates each team member • Be confident enough to be humble • Invest genuinely in your people The sequence matters: Try to be relatable before you're reliable?  You'll seem fake. Try to show competence before integrity?  You'll seem dangerous. Build the foundation first. Trust is harder to build than to break.  But this is what makes it so valuable. When you have it, everything else becomes possible. • Ambitious goals • Difficult conversations • Teams that exceed expectations Most leaders try to drive performance before they deliver trust. Don't be most leaders. ♻️ Share this if you think your team could be more trusting. 🔔 Follow Dave Kline for more practical leadership insights.

"𝘞𝘩𝘦𝘯 𝘺𝘰𝘶 𝘱𝘶𝘴𝘩, 𝘸𝘦 𝘱𝘶𝘴𝘩 𝘣𝘢𝘤𝘬 𝘩𝘢𝘳𝘥𝘦𝘳." It’s an unspoken agreement in workplaces everywhere. Are you unknowingly igniting resistance instead of sparking change? 𝗧𝗵𝗲 𝗛𝗶𝗱𝗱𝗲𝗻 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗣𝘂𝘀𝗵𝗶𝗻𝗴 𝗧𝗼𝗼 𝗛𝗮𝗿𝗱
 At City Hospital (a pseudonym used to protect confidentiality), the CEO, “Juliette Garnier” (also a pseudonym), believed decisive action would save the day. Faced with a funding crisis, she enforced a 10% budget cut across departments. Her intent? Keep the hospital afloat. The result? Chaos. Her leadership team froze in silence, employees raged in the corridors, and nurses threatened a strike over unsafe working conditions. Garnier had unknowingly stepped into what I call The 𝙋𝙪𝙨𝙝 𝘽𝙖𝙘𝙠 𝙋𝙖𝙩𝙩𝙚𝙧𝙣: * 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝘃𝗲𝘀 = 𝗘𝗻𝗳𝗼𝗿𝗰𝗲𝗿𝘀 * 𝗘𝗺𝗽𝗹𝗼𝘆𝗲𝗲𝘀 = 𝗥𝗲𝘀𝗶𝘀𝘁𝗼𝗿𝘀 The harder you push, the harder people push back. 𝗪𝗵𝗮𝘁 𝗦𝗼𝗺𝗲 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 𝗠𝗶𝘀𝘀 𝗔𝗯𝗼𝘂𝘁 𝗥𝗲𝘀𝗶𝘀𝘁𝗮𝗻𝗰𝗲
 Resistance isn’t about rejecting change. It’s about rejecting the way change is imposed. When people feel ignored, undervalued, or strong-armed, their silence or anger signals mistrust and resentment. The more forceful the push, the stronger the resistance grows. 𝗕𝗿𝗲𝗮𝗸𝗶𝗻𝗴 𝘁𝗵𝗲 𝗣𝗮𝘁𝘁𝗲𝗿𝗻
 Garnier recognised the pattern and shifted her approach. Instead of enforcing change, she invited her team to co-create solutions. Within weeks, the same employees who had resisted her became her strongest allies, crafting a plan that cut costs without compromising care. The strike was called off, and trust was restored. 𝗧𝗵𝗲 𝗟𝗲𝘀𝘀𝗼𝗻 𝗳𝗼𝗿 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 
Leaders who force change light fires that burn bridges. Those who nudge—inviting collaboration and listening deeply—build lasting trust and sustainable results. Are you lighting fires or building bridges? Would love to hear your views: What strategies have worked for you to overcome resistance and inspire collaboration? 📚 For a systemic lens to creating lasting change, explore the ideas in my book, 𝙏𝙝𝙚 𝙃𝙞𝙫𝙚 𝙈𝙞𝙣𝙙 𝙖𝙩 𝙒𝙤𝙧𝙠.

We've spent years pushing for the concept of "better together", advocating for the importance of alignment across sales, product, and success. However, it's time to stop talking about "better together"; we all understand and get it. Let's do, "Together. Better." Especially today, when speed is essential and demanded in everything we do. Speed is seductive. It feels like progress. It looks like momentum. But without alignment, speed just creates motion sickness (OK, so maybe I'm still recovering from thinking about altitude sickness after a week in Peru). You get busy teams chasing goals that are aligned at the 30,000-foot level, but aren't aligned in where the work actually happens. There are unspoken and competing agendas. And fleeting and shallow wins that celebrate individual victories but not company wins. In the end, we're all left with mounting frustration that no one can quite name, but everyone feels. This is one of the hardest balancing acts in leadership: How do we move fast without breaking trust, clarity, or direction? How do we actually do "together, better?" The answer is not to slow down. It is to align more intentionally. More often. And more visibly. Alignment is not a kickoff slide or a mission statement. It is a discipline. A muscle. A shared drumbeat that keeps people running together, not just running. Because without alignment, speed scales confusion. With alignment, speed scales outcomes. My thoughts on three ways to lead with both speed and alignment: 🔹 Communicate decisions out loud. Assume nothing. Clarity compounds when leaders speak directly and often about what is changing and why. I've lost track of the number of times I thought something was communicated clearly, but realized I had been working on a concept for months and had only communicated it to the team for a few days. 🔹 Cascade purpose, not just tasks. When people understand the “why,” they can act faster and smarter without waiting for permission. Prioritize perspective over permission, which means sharing openly, broadly, and consistently enough context to create the perspective that lets people closest to the work make confident, bold, and faster decisions. 🔹 Check for drift. Build in rhythm to realign. Fast-moving teams need regular calibration. Without it, small gaps become big ones. At DISQO, our cross-departmental, recurring meetings are focused on ensuring continued alignment and providing colleagues with the opportunity to understand changes and collaborate on solving gaps together. Are you ready for "Together. Better?" #CreateTheFuture #LeadershipInAction #StrategicAlignment #HighVelocityTeams #LeadWithClarity #ExecutionExcellence #FutureOfLeadership #TeamPerformance #GTMLeadership #CultureOfExecution #ScaleWithPurpose #CustomerSuccessLeadership

My latest newsletter on resilience seems to have struck a chord. The volume and breadth of messages I’ve received have surprised me. They came from CEOs and from people early in their careers, all describing the same struggle to stay steady under relentless pressure and growing uncertainty. In the piece, I argue that resilience as the ability to “bounce back” belongs to a world where pressure comes in episodes. Today, it compounds. Resilience in this moment is the capacity to remain anchored while the pressure accumulates. To stay present without becoming numb, to listen without rushing to judgment, and to hold moral lines even when compromise feels easier. When leaders are depleted, distracted, or permanently reactive, they don’t stop acting. They stop seeing clearly. And when clarity fades, so does the ability to choose deliberately under pressure, especially when the easiest decision is not the right one. That is why resilience can no longer be treated as a private coping strategy. It has become critical leadership infrastructure. At its heart resilience is not about retreating from the world. It is about remaining sufficiently intact to meet it as it is. It allows leaders to remain attentive to what is happening, honest about what is changing, and firm about what must not. In a period of rapid change and continuous pressure, that may be among the most consequential responsibilities leadership carries.

Beyond our ability to weather storms, developing conflict resilience is about redefining how we navigate through them. Over my career, I’ve seen how clinging to outdated models of conflict management stifles organizational growth. While scenario planning remains a professional cornerstone, true resilience demands agility: The courage to pivot frameworks when they no longer serve our people or purpose. Senior leaders are responsible for anchoring their teams, shielding them from distractions that dilute momentum while driving human-centric strategies that pre-empt volatility. This means refusing to overpromise, resolving tensions with urgency, and embedding radical transparency into every dialogue. Equally critical is consistently communicating what’s next. Clarifying how the organization plans to refocus, reallocate, or reinvent goes a long way in building team trust. The goal isn’t to avoid conflict. It’s to build teams that don’t fear it. Teams don’t need perfection. They need clarity, consistency, and the confidence that their leaders see conflict not as a disruption, but as a catalyst for evolution. #Leadership #ConflictResilience #HumanCentric #PeopleFirst #TeamBuilding

How I manage stakeholders as a Project Manager without saying "no" Stakeholder management is one of the most underestimated skills in project delivery. And one of the trickiest parts is pushback. I’ve seen it time and time again: "Can we add this feature last minute?" "Can we deliver sooner?" "Can we skip UAT? "😅 Saying a direct “no” might feel assertive, but in many corporate environments, especially in matrixed organisations, it’s not always productive. It can cause friction, defensiveness, and damage relationships you need to maintain. So here is how I manage stakeholders without actually saying “no”: ✅ I reframe Instead of saying, "No, that’s out of scope," I say: "Let’s revisit the priorities and see where this fits in. If we bring this in, what are we okay to move out?” ✅ I ask questions Often people just want to feel heard. Instead of shutting down ideas, I ask: "What’s the driver behind this request?" "What would success look like if we included it?" This either de-escalates the urgency or helps me build a case for change. ✅ I make trade-offs visible I use timelines and impact visuals. "We can do that - here’s what happens if we do." Let the facts speak. Most reasonable stakeholders respond well to transparent data. ✅ I bring them into the process When stakeholders feel involved, they’re more likely to accept decisions, even tough ones. This approach helped me deliver projects on time while maintaining trust across business, tech, and delivery teams. Of course, sometimes you have to say “no”, but in most cases, it’s not what you say, it’s how you say it. Do you also navigate difficult stakeholder requests without being the “bad cop”? What strategies work for you? 👇

What if the pushback you’re getting is actually your team’s way of asking to be part of the process? I had such case recently with a team leader: “Susanna, my team resists everything I decide. I spend more time defending than leading.” So I asked him: “Do you involve them early in the process?” He paused. “Well, I usually let them know once the direction is clear.” So I joined one of his meetings. He walked in with a polished plan, laid out the logic, and wrapped it with: “Any quick comments before we move on?” Silence. Then came the emails. The 1:1s. The offhand comments. The real feedback but it was too late to shape anything. That’s when I introduced him to the concept of Status Threat. 🧠 When people feel excluded from decisions that affect their work, they don’t always say it directly. Instead, they resist in quieter ways like questioning, withdrawing, or slowing things down. Not because they’re stubborn. But because being left out sends a clear signal: “Your expertise isn’t needed.” “Your input doesn’t matter.” That’s not just a workflow issue - it’s a psychological safety issue. And when people don’t feel safe or seen, trust breaks down. And when trust breaks down, so does performance. We made a simple change: ✅ Before finalizing any decision, the leader created a 10-minute “challenge space” with a clear structure for input. ✅ He began framing ideas as drafts, not directives. ✅ He started explicitly naming the value of each person’s expertise, making team members feel recognized and included. What actually changed? The team didn’t become more agreeable. But they became more engaged. Because the pushback was never about the plan. It was about their place in it. P.S.: Have you ever mistaken a team's resistance for negativity only to realize later it was a call to be heard?