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

@1:53 failed 1st test on the 1st drilled hole: reflect about what tested your test? Early testing helps for early correction, and in some cases you can choose between possibilities variants of correction methods and this should be taken into consideration when and how to test, to be able to make the best correction as possible. Here I think the test result (1st positioned drilled hole) can be the result of a chain of all steps before (including measuring and marking the center of the hole to be drilled), but in this video point it looks like exactly 1 step in the process of drilling and screwing. The mentioned waterfall approach have tests at the end, which is to late for intermediate correction steps as shown in the next minute.

love the amount of knowledge you share, thank you!

Ofc you release it then you release a dlc to ask ppl to pay for it

I understand that in the #noestimates approach, story size and sprint/development capacity are considered constants, correct? There also seems to be an assumption that we MUST complete our backlog items to deliver anticipated value! No?

thank you so much 😍😍😍

Nice example for BDD & TDD and non-IT field. Thanks

I would go with TDD in an actual world, but BDD in this case of hanging a shelf is more practical and faster with a quick mallet touch and alignment check. I would think in most organizations is the lack of awareness of TDD which drives development/QA organizations to move to BDD. There is again the talk about white box and black box testing which also plays an important role as to whether development teams resolve to TDD or BDD. In deployment pipelines we also have Sonarqube which helps with coverage analysis but component/integration tests are usually black box tests written by QA organizations. TDD or BDD is a very debatable topic and past experience has told me that really depends on what the development/QA (engineering organization) are comfortable with to get latest code to customers asap.

This video goes to the point and super easy to understand.

Nice!!!!

Nice tutorial. So informative.