#EffectiveScrum
Start a conversation around new products ideas is hard, with all of the noise surrounding #GenAI

I look forward to the #GenAI bubble bursting.

#EffectiveScrum #LeaningInPublic
October 8, 2025 at 2:13 PM

- Commitment is based on velocity vs. understanding the product backlog items.
- Stakeholders trying to override Product Owner Priorities

## Technical Debt
- Not taking into account the Drag Effect of Technical Debt

8 of 10 #EffectiveScrum
January 22, 2025 at 3:13 PM
Since Kanban requires more self-discipline than Scrum to do well, a team that didn't try to solve their problems before the switch is unlikely to solve them when they jump to Kanban.

4 of 9 #EffectiveScrum
January 7, 2025 at 5:28 PM
Hint: Generative AI is the current supply of magic beans).

So, what factors lead to Sprint Hangover?
- Too Much Work in Progress
- Lack of Collaboration
- Handoffs between people (WIP++; Collaboration--)
- Separation of Roles i.e. QA/BA/Developer

6 of 9 #EffectiveScrum

January 7, 2025 at 5:28 PM
...during Sprint Planning, assuming it will magically make more sense when they work on it. (Hint: there is no magic).

Weak or Missing Acceptance Criteria - Bad user stories lead to weak or absent Acceptance criteria. Without good acceptance criteria...
5 of 8 #EffectiveScrum

February 5, 2025 at 4:32 PM
Yesterday, we looked at how poor understanding of User Stories, kills quality. Today it's Flow. Flow is an almost magical state, where do our best work. Scrum should help improve a team's flow. Refinement gives us a clear understanding of next Sprint's work

1 of 8 #EffectiveScrum
February 6, 2025 at 6:01 PM
Culture is hard to change; these issues are the ones that often get addressed last. Of course, failure to address these issues from the start makes real change much harder.

## Cultural Issues:
- Pressure to go faster - we have a culture focused on speed across North America...

1/6 #EffectiveScrum
February 23, 2025 at 2:12 PM
"Scrum was supposed to improve quality. All it's done is help get the bugs out the door faster." If I had a dime for every time, I have heard this comment, I would be rich.

We know it's possible to reduce low defect code. So, what leads to poor quality?... 1 of 8 #EffectiveScrum

February 5, 2025 at 4:32 PM
What to measure?
- Cycle Time and Throughput
- Team Morale
- Defects found in production

Do you want more on overcoming the busyness problem and other things that harm #EffectiveScrum? Subscribe to our newsletter:
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
agilepainrelief.com
January 17, 2025 at 3:21 PM
Without real user feedback, we’re developing the product with a blindfold.

What Process issues have you noticed that affect Quality? Sign up for our newsletter to see how I coach teams through this problem.

https://buff.ly/3W2atOR

5/5 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 25, 2025 at 8:28 PM
...We change lanes dozens of times in our commute despite knowing that it has a marginal effect at best. This shows up in Sprint Planning, where teams, even without external pressure, focus on cramming items into the Sprint.

2/6 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 23, 2025 at 2:12 PM
This is the classic Docker joke, but it's an awful quality standard.
- Insufficient Stakeholder Feedback - I’ve witnessed Sprint Reviews where the Product Owner gives a polished 20-minute demo (snooze). Stakeholders/End-Users nod politely and leave, or worse, don’t show up. ...

4/5 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 25, 2025 at 8:28 PM
It’s a bit like combining the role of coach and manager on a professional sports team.
- When there is no Definition of Done (when teams ignore it), then product quality is subjective. “Well, it worked on my machine” becomes the quality standard.

3/5 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 25, 2025 at 8:28 PM
Tomorrow we will work on Flow Breakers and how they affect quality.

Which of these do you recognize from your own Experience? What have I missed? Sign up for our newsletter to see how I coach teams through this problem.

8 of 8 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
agilepainrelief.com
February 5, 2025 at 4:32 PM
This principle holds true whether you're developing software or competing in sports. Ask any competitive athlete. They all want to go faster. Most know that speed involves improving technique (learning) and expending less energy (quality). As we learned with many 4 a.m. drives..

5/6 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 26, 2025 at 2:12 PM

- Poorly defined roles - Many orgs use Scrum as a coat of paint on top of their existing process. They add SM and Product Owner as additional responsibilities to already busy people. Worse, they combine both into one role, assuming there isn't much going on for either role.

2/5 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 25, 2025 at 8:28 PM
To create a skills matrix, run a workshop. You can follow the step-by-step in my article "How to Build a Powerful Team from Scratch" here 👉🏻 buff.ly/Z4gIixu

#EffectiveScrum #SkillsMatrix #TeamBuilding #Agile #Scrum #Collaboration #Teamwork #HighPerformanceTeams
December 1, 2025 at 2:12 PM
Sign up for our newsletter to learn how to be more effective. (Sadly, I know that I'm as fit as I was playing rugby when I was in my 20s). https://buff.ly/3W2atOR

6/6 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
agilepainrelief.com
February 27, 2025 at 2:12 PM
Today's duplicate code and additional complexity will be a source of problems in 2026 and beyond.

#EffectiveScrum Teams find where their real bottlenecks are and address those problems. (AI may not be included).

5/6
February 27, 2025 at 2:12 PM
Since the bottleneck was never the rate at which we write code, generating code faster with AI is a waste.

I will say it out loud: LLM-generated code will be a leading source of quality problems in 2025.

4/6 #EffectiveScrum
February 27, 2025 at 2:12 PM
Here are the effects we can document about AI/LLMs
- Code Complexity is going up, not down
- Deployment Frequency has slowed, and Rollbacks have Increased

The Theory of Constraints says that any improvements that don't affect the key constraint are an illusion.

3/6 #EffectiveScrum
February 27, 2025 at 2:12 PM
Measuring perception and not the code itself, leads to false conclusions.

The data shows that duplication is increasing and refactoring is decreasing. The data tells us that perception doesn't match reality. (GitClear AI Copilot Code Quality: 2025 https://buff.ly/3QvIBPy

2/6 #EffectiveScrum
AI Copilot Code Quality: 2025 Data Suggests 4x Growth in Code Clones - GitClear
Stack Overflow's 2024 Developer Survey showed that 63% of professional developers are currently using AI in their development process, with another 14% saying they plan to begin using AI soon.
buff.ly
February 27, 2025 at 2:12 PM
I perceive that I am the fittest I've ever been. If the data doesn't back my perception, then it doesn't matter.

The DORA 2024 State of DevOps report (https://buff.ly/3Ab2YNe) misses the boat. They measure Developer's perceptions about AI: feel productive++ and complexity--.

1/6 #EffectiveScrum
DORA | Accelerate State of DevOps Report 2024
DORA is a long running research program that seeks to understand the capabilities that drive software delivery and operations performance. DORA helps teams apply those capabilities, leading to better…
dora.dev
February 27, 2025 at 2:12 PM
Arbitrarily determined deadlines become immovable goal posts. Team members contort themselves to achieve these goals.
- Speed over Quality and Learning - Speed comes from focusing on Quality and Learning. Not the other way round.

4/6 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 26, 2025 at 2:12 PM
People will forgo time to make improvements, fix tech debt, cross-skill to cram another item into a Sprint, even though this is counter-productive.
- Too often, the pressure also comes from above. Pressure to finish more features and meet meaningless deadlines worsens problem.

3/6 #EffectiveScrum
Newsletter
Sign up for our newsletter to get regular updates on our courses, content, and advice and resources on Agile and Scrum.
buff.ly
February 26, 2025 at 2:12 PM