As a developer I hate both, especially the meetings

Sorry but TDD IS not related to unit test 😉

We need this kind of animation rather than telling stories the whole time. The best way to make beginners know those approaches. Thanks for the effort.

I could listen to Gary for hours

¡Qué interesante video sobre TDD! 🤔 Siempre me ha costado empezar con los tests antes del código, pero entiendo que es súper útil para evitar errores. ¿Alguien más ha tenido problemas con el mocking? Estoy aprendiendo en сodigо herоe y me encanta cómo explican todo. 😊

I come here 7 years later and the cheat sheet is no longer available, can that me uploaded again? LOL, thank you so much for this video

Awesome video. Thanks for sharing the cheat sheet. Have a great weekend.📝👍236 likes

Need cheat sheet please.

Why not so much thumbs up? It’s so clarifying! Is everybody pretending or I am dumb?

🤯

I always have a "Fast Track" column to keep from reordering or adding to my "Doing" column for emergency tasks that emerge from QA.

I have a construction Bussiness and I found scrum and kanban very useful. But most of the videos are on software development. Anyway good to find Kan-ban.

New to this, and I guess I wonder.. how do I think of this in context of a major new project? There I see more scrum / sprint planning, but I see this working well for ongoing enhancements to existing products. Can both scenarios be tackled under the same framework?

Simplicity is the ultimate sophistication. Killer job, man.

Lubowitz Drives

Perfect lesson, thank you so much

Excellently explained

Agree that the backlog should be flexible to a certain extent and anything new should absolutely directly contribute to the sprint goal and existing product goal. However, if the backlog has been managed well and sprint backlog items effectively scaled and discussed, surely any completely new requirements should be refined and then added to the next or a future sprint? It also undermines the authority of the Scrum team (however formally they work in terms of purist Scrum methedology) if it's realised that outside influence can throw in hand grenades at any time?

Perhaps the only channel which knows how to teach and deliver effectively. These 5 minutes were more productive than watching hours and hours of videos and reading tons of articles on this subject, yet left confused and unclear. Thank you for providing such a quality education. ❤

Very well said

simple and lucid explanation

Great question about Scrum + smth = ? My answer would be - if you adding smth, especially smth detailed and complicated, you probably loosing the initial (and the most important) part of Guide - Pillars and Values. E.g. a team which properly understands Focus value, does not need WIPs to be imposed by the board. They just naturally strive to complete an item of work before taking next one. Same Focus value + understanding of 'developer' concept naturally forces them to exchange tasks rather than creating silos around group of columns on the board - 'I'm a programmer, I don't test'. While those 'technical' elements might help the team to perform (and have fun as well), it does not replace proper understanding of the Guide, and the more tools/processes/practices are implemented, the further team gets away from Scrum in its spirit.

I did get back to the recording after getting called away yesterday. What is the book that lead you to the 7 steps?

Yep. Save yourself 5 minutes. This video does not answer its own questions.

You conveniently failed to mention when the demo and the retrospective are done in Kanban!

Good stuff. I know they may not be a part of either framework, but Definition of ready to let items into the sprint, and the Definition of Done, to gain a universal agreement on what it means for a work item to be done, are as important as wip limits imo. They help prevent work from getting stuck inside the sprint, or forgetting quality gates on the way out. Super helpful video overall though. Just thought I'd add this thought.

I apperciate your simple and clear explaination of topics , The video was really awesom ! thank you

Amazing !

Very informative and useful for me to start implementing scrumban into my team. I love the way you presented it, which was much simple to understand, thanks

Great video, trying to sell course and material for 37$ instead of cheatsheet was a big turn off though. Edit: Gary sent me the cheatsheet later! Thanks a lot, you've gained a subscriber! Sorry for judging :)

Good video! Would be nice to have one about story partitioning.

We used to. But a point was a day, and soon we did away with points and went with hours (except for my team, because I mocked the idea of that level of accuracy). Anyway that was a big mistake, so I'll be fighting for t-shirt sizes soon.

Yh i was confused but have received it thanks

Your explanation is very clear and to the point, thank you!

Your pencil-football analogy hit the nail on its head. Great work!!

you mispelled cheat

Wow one of your best vidéo (nice, valuable, smart)

all are fake science. just do dev naturally.

still got no clue