How to Handle Defects During the Scrum Sprint (DON'T ESTIMATE BUGS...)

Here's what we will cover in this video:
- What are defects and bugs in agile scrum?
- Difference between defects and bugs?
- How to handle defects in agile scrum?
- How to manage defects in agile scrum?
- How to track defects in agile scrum?
- Should Story Points Be Assigned to a Bug Fixing Story?
- Should defects be estimated in agile scrum?
- How to handle defect management during the sprint?
- What are spikes? How to handle spikes in agile scrum?

What this channel is about:
The #1 place on YouTube for all things Agile.

This channel explores:
- Agile methodology, principles and value
- Agile advanced scrum masters training
- Scrum developer, scrum product owner
- Kanban, Extreme Programming (XP)
- Agile project management and software development
- Agile SAFe
- etc.

I want to hear from you. Please ask your question, provide feedback and give your point of view on the topic in the comment section below. Thanks for your support

[agilecoach]

I want to hear from you. What topic do you want me to cover next?

[Glundberg]

I am starting as a fresh (and only) Scrum Master at the firm I am working for now in August and I have understood the one of the big challenges the team has is that the team is both responsible for Operations (maintaining already existing products) and develop now once. Unfortunately it's not rare that some critical bug appear somewhere in their operations portfolio that ram the sprint from the side and f%#¤ everything/the planing up. I guess I will have to try to use the bucket strategy for that...

[shadyworld]

Already recommended to be included in the Agile WOW 👌

[Daniel-jstd]

I like that your videos are both informative and entertaining

[oleeGforreal-nepali]

I would have gotten a PM job if I had watched this video earlier!

[bryanlagrange]

Good explanation on how to manage bugs

[etdp.]

Hello folks!

I would really appreciate some contribution/suggestions.
I have just started off a PO role, belonging to a mature dev team of which capacity is so distributed:

> 70% tech-debt/bugs depending on the fact the FE of the app was refactored switching from ember to react
> 30% new features

how would you handle this situation?

> lightweight scrum for the new features

> what about the bugs due to the entity/quantity of those, please? what would be the best way to handle those? should we decouple the backlogs and handle the bugs maybe more in a kanban way?


planning is definitely not easy on such a condition


thanks!