Speaker 1: If you've found this video, the chances are you've just done a search for the difference between Scrum and Kanban. Well, you've come to the right place. Not only do I have a great video for you, I also have a cheat sheet for you to download. Hi, this is Gary. Welcome to Development That Pays. We've got a ton of stuff to get through today. So let's get straight at it. Scrum and Kanban are perhaps the best known of a whole range of Agile software development methodologies. Let's break that down. Software development in very broad terms looks like this. The product owner decides what to build. The development team builds it. And customers use it, experience it, benefit from it in some way. What makes software development Agile is that value is delivered to the customer in small increments. And, importantly, feedback is gathered from the customers and fed back into the process. It's the product owner's job to take input from customers and from other stakeholders and to organize it into a prioritized list of features and user stories. This list is known as the product backlog. Now, what happens between the product backlog and the customer is what distinguishes Scrum from Kanban. As we'll see, each has its own routines and rituals. And it's this person's job to help the product owner and the development team to adopt and maintain good habits. In Scrum, the role is known as the Scrum Master. In Kanban, the role is known as the Agile Coach. Something that Scrum and Kanban have in common is that both are Pulse Systems. Without getting into too much detail, the Pulse System ensures that work gets from product backlog to customer in the shortest possible time. The Pulse System also helps to uncover bottlenecks in the process which helps to ensure that work gets from product backlog to the customer in the shortest possible time. As you'll see in a moment, Scrum and Kanban implement the Pulse System in two strikingly different ways. Scrum teams work in a series of Sprints most commonly two weeks in duration. Each Sprint is preceded by a Sprint Planning Meeting run by the Scrum Master and attended by the product owner and the development team. Together, they select high-priority items from the product backlog that the development team believe it can commit to delivering in a single Sprint. This is the pull I was talking about earlier. The selected items are known as the Sprint Backlog. For the next two weeks, the development team focuses on working through the items in the Sprint Backlog and only those items in the Sprint Backlog. In all but the most exceptional circumstances, any new requirements that crop up have to wait for the next Sprint. It's common practice for Scrum teams to use a board to track the progress of work. It's called a Scrum Board, or an Agile Board, or even, slightly confusingly, Kanban Board. Each day during the Sprint, there's a Scrum Meeting. It's a stand-up meeting where the team takes a maximum of 15 minutes to discuss progress and to identify any blockers. At the end of the Sprint, the work completed during the Sprint is packaged for release. Any incomplete items are returned to the product backlog. The Sprint ends with two rituals. The Sprint Review, which is a demonstration of new functionality to the stakeholders. And the Sprint Retrospective, which is an examination of what went well, what went badly, what could be improved. The aim of the Retrospective is to ensure that the next Sprint is more efficient and effective than the last. And that's Scrum. Kanban does a few things differently. There's no two-week Sprint. Kanban is a continuous process. And there's no Sprint Backlog. The pull system in Kanban happens in a different way, via work-in-progress limits. Each column on the Kanban Board has a work-in-progress limit, related to the team's capacity. For example, a team with two developers would set a limit between two and four items. The lower, the better. Let's see the pull system in action. When testing of a particular feature is complete, the corresponding ticket moves to the Done column. The Empty column is a signal to the previous column to send another ticket. That's the pull. Similarly, when the Build column is almost empty, it's a signal to the dev team to select another high-priority item from the backlog. That's the pull again. Kanban has a number of rituals in common with Scrum, although the naming is slightly different. Daily stand-up meetings. Demos for stakeholders. And Retrospectives. So now you know the difference between Scrum and Kanban. Two important things to say at this point. First thing. Neither Scrum nor Kanban are as prescriptive as I may have made them appear. High performing teams discover what works for them, and flex the system accordingly. Secondly, I've put together a cheat sheet for you that covers everything we've talked about today, plus some additional notes that I think you'll find useful. You can grab a copy from my blog via the link in the description. You'll find it somewhere around this video.