Thank you for creating this video! It's helpful!

@DOITAGILE

3 жыл бұрын

Thanks for your feedback Sophia! I'm glad it helped! Feel free to check the other videos and subscribe the channel.

Very helpful video! Thanks a lot! I am gonna use that technique right away on my team

@DOITAGILE

2 жыл бұрын

Thanks a lot for your comment and support. I will keep adding them!

Well explained, very useful!

@DOITAGILE

Жыл бұрын

Glad it was helpful!

nice video !

@DOITAGILE

3 жыл бұрын

Thank you! Cheers!

I liked your video, simple and understandable.

@DOITAGILE

Жыл бұрын

Glad it was helpful! Thanks for dropping by!

what do you mean by story points being zero for an immediate but problem?

@DOITAGILE

2 жыл бұрын

@Etan Pfeiffer, thanks a lot for dropping by! When a Bug needs to be solved immediately within an iteration, it represents work that was never planned and it was never seen in the backlog. Additionally, it will take time from your iteration that was not foreseen (this is what I call an unplanned event). By not giving any point, you will implicitly reduce the team's velocity due to unplanned events. On the contrary, if you give points to a bug in this situation, you are considering that you are doing work as usual and you will maintain the team's velocity, stating that everything is business as usual. On top of that, teams tend to augment their estimates when they solve these type of issues to have the idea that they are progressing well, while in fact they are playing it against themselves :) I hope I was able to explain!

Why wouldn't someone just log a bug on the backlog of a project? What's the difference? Seems like you are just creating more work?

@palhinhas

7 ай бұрын

@anubis32377, thanks for dropping by! Regarding your question, bugs can be found during any moment in the project. They represent effort that was not foreseen and that will take time from your team. So, depending on how you want to plan that extra-work, it may make sense to have those bugs in your backlog to be estimated and planned for future implementation. This happens, for instance, when you find a regression bug. You may decide that you don't want to interrupt the team now (context switching also costs time and money). On the other hand, when you find errors in stuff that the team is currently developing, we do not consider them as bugs but instead, they are part of the development process. Because of that, they represent some additional work under a specific story and not a bug in the backlog. I mean, it wouldn't make much sense to create a bug in the backlog related to a story that haven't yet met the Definition of Done (not completed).

My name is Bill😂