Understanding Scrum Methodologies

Let’s Talk About Sprints. Grab Your Pitchforks. Sprints are central to Scrum. They're not just "a container for all other events" - they’re "the heartbeat" of the framework. Sprints are "fixed-length events of one [calendar] month or less" that "may be considered a short project." Someone recently asked me my opinion. I said I think sprints may be doing more harm than good. Yes, they offer structure. Great for new teams. Like training wheels. Or scaffolding. Yes, they make work feel organized. Great for disorganized teams. Yes, they force planning (and hopefully prioritization). That’s useful. And, yes, they’re easy to teach and learn. Nice for a quick start. But for many teams, sprints are a lousy fit for how work actually happens in their context. Hear me out... 1) False Deadlines Sprints create artificial urgency. Teams rush to "finish" by the last day, whether the work is truly done or not. That leads to cut corners, half-baked features, or tech debt and waste. 2) Broken Flow Deep, meaningful work needs uninterrupted focus. Sprints break that focus like clockwork - every week or two. Plan. Demo. Retro. Repeat. It’s a rhythm that can ironically interrupt real flow. 3) Arbitrary Timeboxing Complex work doesn’t neatly conform to 1- or 2-week chunks. So teams slice stories, fudge forecasts, or roll things over - just to maintain a cadence that ultimately doesn’t mean much. 4) Hollow Goals In theory, sprint goals guide the team. In practice, they’re often vague, forced, or written post-hoc to justify what’s already in the sprint backlog. 5) Masked Problems Velocity looks like math, but it's often a nonsense number that hides reality. Spillover. Dependencies. Gaming. A number trending up isn’t always progress. 6) Process Overhead Planning, reviews, and retros aren’t inherently bad - until they become empty rituals. Done 26 times a year, they can waste serious time and money. Why not plan when it’s needed? Retro when it matters? Demo when there’s something to share? 7) Bad for Innovation Real discovery is messy and nonlinear. Insight doesn’t arrive on a fixed interval. Sprints incentivize small, safe, and shippable over breakthrough or bold. 8) Process Theater Rituals become performance. Stand-ups drift into status meetings. Reviews turn into slide decks. Everyone’s "doing Agile," but no one’s improving. 9) Less Responsive Ironically, sprints can limit agility. When priorities shift mid-sprint, teams either break the sprint (chaos) or defer the change (delay). Continuous flow handles change better. Look, sprints aren’t evil; but they’re also not sacred. If your team is succeeding with sprints and Scrum - great. Keep doing what works. But if you’re constantly sprinting and never improving, ask why. If every sprint feels like a reset with no real progress, maybe it’s not your people, but your system. Agility is about adapting, not repeating. Don't worship the timebox. Ask yourself if your sprints are killing your flow.

90 percent of the Scrum teams I see in the real world aren't actually practicing Scrum at all. This isn't an attack on anyone, it's just an observation about reality. Most 'Scrum' Teams I meet; Don't have a Product Goal. Set either no Sprint Goal, or multiple Sprint Goals. Don't have (or barely look at) a Definition of Done. Do not have a real Product Owner whose decisions are respected. Are not self-managing. Are not cross-functional. Do not produce a usable product increment at least once per sprint. Do not demonstrate the outcome of their sprint to real stakeholders. Worst of all.. They do not use the learnings from a sprint to inform the future product direction. (and how could they, given everything else?) The reality is that most 'Scrum teams' are practicing "ZSBMD". Zombie Scrum by Management Decree. They are going through the motions of a process they don't understand, to appease people who understand it even less. We have to find a way to do better. That doesn't mean you have to do scrum 'by the book' But it does mean that you should have at least read the book before you decide there's nothing in there for you.

🚨 A Hard Truth: Sprint Goals Aren’t Optional If your Sprint doesn’t have a Sprint Goal, you don’t have a Sprint. You have a two-week task list. 75% of the teams I start out working with don’t use Sprint Goals at all, or use them poorly. 👀 I hear the same excuse again and again: "But you don’t understand, we’re different." The truth is you’re probably not so special. Not to play Scrum Police, but the Sprint Goal is not optional. Common impediments that stop teams from using Sprint Goals: ☠️ Missing a Product Goal. Without a north star, Sprint Goals have no direction. ☠️ Multiple products stuffed into one Product Backlog. ☠️ An uninformed Product Owner who hasn’t ordered the Product Backlog by cohesive PBIs. ☠️ Focus is impossible when Product Backlog items are randomly ordered. ☠️ A Product Owner who can’t say "no", who's an order taker instead of a value maximizer. ☠️ An organizational culture that prizes busyness and utilization over outcomes. Sprint Goals feel irrelevant when activity is valued more than impact. Common misuses that weaken Sprint Goals: ❌ Writing the Sprint Goal as: "Complete 12 tickets this Sprint." That’s output, not outcome. ❌ Creating multiple goals strung together with AND. If everything is important, nothing is. ❌ Goals that are too vague or not tied to business value. Empty words give no clarity or purpose. ❌ Treating the Sprint Goal as a theme or label. "UI Sprint" or "Tech Debt Sprint" is not an outcome. ❌ Reusing the same Sprint Goal Sprint after Sprint. Signals stagnation, not progress. Benefits of Sprint Goals: - Focus. Prevents the team from scattering effort across unrelated tasks. - Empiricism. Creates a meaningful way to inspect and adapt progress each Sprint. - Purpose. Provides intrinsic motivation and gives the team a shared outcome. - Alignment. Acts as a stepping stone toward the Product Goal and creates continuity across Sprints. - Cohesion. Becomes the glue that binds a group of individuals into a real Scrum Team. 🔑 What the Product Owner can do: - Ensure there is a clear Product Goal so Sprint Goals naturally flow from it - Order Product Backlog items by cohesiveness - Bring an objective for the Sprint into Sprint Planning - Engage with stakeholders and say "no" when needed to protect focus 🔑 What the Scrum Master can do - Teach the purpose and power of Sprint Goals - Facilitate Sprint Planning to ensure a single, cohesive goal is defined - Coach the Product Owner on different Product Backlog ordering techniques - Call out weak or vague Sprint Goals and coach the team toward clarity. 👉 A team not working on a Sprint Goal isn't a team - they are a just a group of individuals. What’s the worst Sprint Goal you’ve ever seen in action?

What Not to Do as a Scrum Lead (I Learned the Hard Way) 1.  Micromanaging the Team Instead of Empowering Them Acting like a project manager controlling every task and decision undermines team ownership and agility. 2. Skipping Retrospectives or Treating Them as Formalities Neglecting retrospectives or rushing through them means missing out on key learning opportunities. 3.  Allowing the Daily Stand-Up to Turn Into a Status Meeting Turning the stand-up into a reporting session to the Scrum Lead, instead of team-level collaboration, breaks Agile spirit. 4.  Not Shielding the Team from External Disruptions Letting business, clients, or operations interrupt sprint work with unplanned tasks leads to churn. 5.  Ignoring Technical Debt in Favor of New Features Prioritizing only customer-visible work can cause long-term stability and scalability issues. 6.  Failing to Communicate Agile Principles to Stakeholders Assuming everyone understands Agile leads to misaligned expectations and friction with external teams. Follow Shraddha Sahu for more insights

So many organisations fail to get benefits from Scrum not because there's anything particularly special or unique or challenging about what they do but because they fail to understand and implement the very basics of Scrum. They fall at the very first hurdle. You're not "doing Scrum" just because you're going through the motions with the artifacts and events. Those artifacts and events are designed to raise transparency on plans and processes and allow you to inspect and adapt. But without real transparency you're basically wasting your time. So many organisations... 🔻 Don't have clearly defined and well communicated goals 🔻 Fail to establish psychological safety within their teams so people can ask questions, raise issues and admit mistakes 🔻 But instead have a culture based on fear, shame and blame 🔻 Say they want openness and honest feedback but then shoot the messenger 🔻 Don't work on establishing acceptable quality standards and a common understanding of what "done" means 🔻 Impose "challenging" deadlines on teams, don't listen when they're told the deadlines are unrealistic and don't move the deadlines when the goalposts move 🔻 Don't listen when they're told that processes are inefficient or wasteful 🔻 Fail to break down barriers between teams and establish a common language and understanding 🔻 Expect their teams to have the difficult conversations without giving them the time, tools and trust to do so 🔻 Fail to seek out stakeholder feedback early and often 🔻 Don't establish clear accountabilities and communication channels I'm not saying any of this is easy. It's not. But establishing transparency so the organisation can make better decisions about what to do and how to do it is fundamental to Scrum's empirical approach. Without that transparency organisations often don't really understand their progress (or lack of progress) towards business goals and problems... until it's too late. And the worst of it is they often don't understand why they failed even after it's happened. ⚡ Of course, you could argue that transparency isn't even the first hurdle. The fundamental unit of Scrum is a small, self-managing, cross-functional team empowered to make their own decisions... and most organisations only pay lip-service to that idea. But maybe that's a post for another day! 😉

Top 5 Scrum Anti-patterns Scrum isn't just about ceremonies and sprints—it's about mindset and collaboration. But too often, teams fall into subtle traps that look agile but silently kill productivity and morale. Here are 5 common anti-patterns I’ve observed 👇 ❌ 1. ScrumMaster as Project Manager When the Scrum Master becomes a task assigner or delivery enforcer… we’ve lost servant leadership. ❌ 2. Daily Stand-ups as Status Meetings If your daily stand-up sounds like a status report to the Scrum Master, it's a red flag 🚩. The goal? Team alignment and collaboration. ❌ 3. Carrying Over Stories Sprint After Sprint Chronic rollover means poor planning or overcommitment. It’s a sign we need to reassess capacity or definition of done. ❌ 4. No Real Product Owner Engagement A silent PO = A drifting team. Lack of PO involvement creates ambiguity, confusion, and delays in value delivery. ❌ 5. "Zombie Scrum" You're following every ceremony... but delivering no real value. Metrics are up, but customers aren't happy. #ScrumMaster #AgileLeadership #AgileMindset #TeamTransformation #ScrumLife #AgileCoach #AgilePractices #ScrumTeam #AgileWaysOfWorking #LeadershipInAgile #ContinuousImprovement #HighPerformingTeams #AgileTransformation #ServantLeadership #ScrumCulture #Scrumantipatterns #Projectmanagers

You can't play chess without your queen. Yet I see teams trying to do Scrum without a Product Owner every day. "Can we just have the Scrum Master handle the backlog?" they ask. Here's what I've learned after 20+ years as an Agile practitioner: Scrum isn't just a loose collection of practices you can mix and match. Think of it like chess. You need an 8x8 board with all the pieces in their proper positions. Try playing without your rooks or bishops, and the game breaks down fast. Scrum works the same way. The Product Owner isn't just "nice to have" - they're accountable for maximizing product value. Without someone fully focused on stakeholder needs, backlog prioritization, and economic decisions, your team will drift. I get it. Sometimes you don't have a dedicated Product Owner available. Budget constraints, organizational politics, whatever the reason. But here's the thing: you don't have to do Scrum. Kanban might work better for your context. So might XP practices with lightweight planning. There are plenty of ways to be agile without forcing a framework that's missing essential pieces. The worst thing you can do is implement "Scrum-ish" and wonder why your delivery is inconsistent and stakeholders are frustrated. If you don't have all three accountabilities - Product Owner, Scrum Master, and Developers - consider other approaches first. What's your experience with incomplete Scrum teams? Have you found alternatives that worked better? #scrum #productowner #agilemethodology #scrummaster #agilecoaching

Let’s be honest. Traditional standups are a waste of time. “Yesterday I was in meetings...” “Today I’ll catch up...” “Tomorrow I hope to...” Why are we all here? That’s not a standup. It’s a calendar recap no one needs. Let’s be real: I don’t care how many calls you took or what doctor’s appointment you had. No one’s moving faster because you shared your admin log. No one’s solving problems with these useless updates. What do I care about? ✅ Are we on track? ✅ If not, why? ✅ What’s blocked? ✅ How do we fix it together? ⚠️ TPMs, PMs, Scrum Masters: Stop wasting the only time your full team might be together all day! ✅ Protect their time ✅ Escalate early ✅ Set the tone ❌ Stop burning time 🔥 Start building momentum Ask instead: - Are we on track? - What’s in our way? - What needs escalation now? - How can I help unblock you? Then: - Solve what you can in a quick team “parking lot” with remaining time. - Take deeper issues offline - Keep the team moving forward Here’s the difference: 🟥 Bad Standup: “Finished a few tickets, had some calls, going to work on more today.” 🟩 Strategic Standup: “We’re 2 days behind on X. Waiting on legal approval. Might miss delivery unless unblocked by EOD.” One is noise. The other drives action. No one needs to know you had a dentist appointment. They need to know if the delivery date just slipped, and what help you need. If you’re only recapping daily tasks, you’re just hosting standup theater. Your team deserves better. A standup should save time, not waste it. Be the one who sets the pace. Not the one who schedules a daily group stall. Leadership = Clarity under pressure. Not comfort in routine. Let this one sting. Then fix your standup. Agree? Disagree? Still running status-only standups? Comment below👇. Let’s fix the ritual, not just repeat it. ♻️ Repost to level-up your project leadership skills. 🔔 Follow Elizabeth Dworkin for more like this. #projectmanagement #projectleadership #dailystandup

5 Scrum anti-patterns that turn your agile team into a waterfall disaster (and what strong PMs do instead) You’re following Scrum. But somehow, it feels like you’re back in 2009... Chasing deadlines, Checking boxes, And managing chaos. Here’s what’s likely happening: 1. Standups = Status reports Not collaboration. Everyone talks at the board, not to each other. 2. Sprints = Mini waterfalls Work is fully planned, scoped, and rigid, with no room to adapt. 3. Velocity = Vanity metric The team’s faster… but delivering the wrong thing faster. 4. Reviews = Demos for ghosts Stakeholders skip. Or worse, show up and tune out. 5. Retros = Blame sessions Problems are discussed but never solved. Strong PMs don’t just “run Scrum.” They lead through it. ✅ They reset team habits—reminding everyone why we do what we do. ✅ They challenge bad patterns—even when it’s uncomfortable. ✅ They anchor the team to outcomes, not output. Because agility isn’t about speed—it’s about direction. Which of these anti-patterns is killing momentum on your team right now? Or did I miss one? Drop it in the comments. Follow for straight-talking insights that help IT project managers lead with impact, not just activity.

3 Mistakes Scrum Masters Make (And how to fix them before your team burns out) Even experienced Scrum teams get stuck. And they usually don't even see it happening. Here are 3 mistakes I see over and over again, even in "mature" teams: ↓ 1. Standups become status meetings    • They go around the circle.    • Each person reports.    • Nobody listens. Fix: Focus on team flow, not individual updates. Ask: “What’s blocking the team from delivering?” Instead of “What did you do yesterday?” 2. Retrospectives become repetitive    • Same issues. Same comments.    • No real improvement. Fix: • Change the format. • Bring energy. • Use themes like “Start-Stop-Continue” or “Sailboat.” • Create psychological safety, or no one speaks the truth. • Assign action items. & Follow up. Every time. Retrospectives aren’t for venting. They’re for building. 3. Scrum Master becomes the task manager    • You’re solving all the problems.    • You’re chasing people.    • You’re the bottleneck. Fix: Shift from doing to coaching. • Ask more questions. • Build ownership. Your goal? Make the team not need you. Even high-functioning teams fall into low-functioning habits. Scrum is simple, but not easy. The good news? Small changes create real momentum. What’s the #1 mistake you’ve seen in experienced teams? Drop it in the comments ↓ Follow for more Stanley #ScrumMasters #AgileCoaching #ScrumMasterMistakes #AgileMindset247