00:00if you've found this video the chances
00:01are you've just done a search for the
00:03difference between scrum and kanban well
00:05you've come to the right place not only
00:07do i have a great video for you i also
00:09have a cheat sheet for you to download
00:13hi this is gary welcome to development
00:15that pays we've got a ton of stuff to
00:17get through today so let's get straight
00:19scrum and kandan are perhaps the best
00:21known of a whole range of agile software
00:23development methodologies
00:25let's break that down
00:27software development in very broad terms
00:30the product owner decides what to build
00:34the development team
00:38and customers use it experience it
00:40benefit from it in some
00:42way what makes software development
00:45agile is that value is delivered to the
00:46customer in small increments
00:49and importantly feedback is gathered
00:52from the customers and fed back into the
00:56it's the product owner's job to take
00:57input from customers and from other
01:00and to organize it into a prioritized
01:02list of features and user stories
01:06this list is known as the product
01:10now what happens between the product
01:11backlog and the customer is what
01:14distinguishes scrum from kanban
01:16as we'll see each has its own routines
01:18and rituals and it's this person's job
01:21to help the product owner and the
01:22development team to adopt and maintain
01:25good habits in scrum the role is known
01:27as the scrum master in kanban the role
01:30is known as the agile coach
01:33something that scrum and kanban have in
01:34common is that both are pull systems
01:37without getting into too much detail the
01:39pull system ensures that work gets from
01:41product backlog to customer in the
01:43shortest possible time
01:45the pull system also helps to uncover
01:47bottlenecks in the process which helps
01:49to ensure that work gets from product
01:51backlog to the customer in the shortest
01:55as you'll see in a moment scrum and
01:57kanban implement the pull system in two
01:59strikingly different ways
02:02scrum teams work in a series of sprints
02:04most commonly two weeks in duration
02:07each sprint is preceded by a sprint
02:09planning meeting run by the scrum master
02:11and attended by the product owner and
02:13the development team
02:14together they select high priority items
02:17from the product backlog that the
02:18development team believe it can commit
02:20to delivering in a single sprint
02:23this is the poll i was talking about
02:26the selected items are known as the
02:30for the next two weeks the development
02:31team focuses on working through the
02:33items in the sprint backlog and only
02:35those items in the sprint backlog
02:38in all but the most exceptional
02:39circumstances any new requirements that
02:41crop up have to wait for the next sprint
02:45it's common practice for scrum teams to
02:47use a board to track the progress of
02:48work it's called a scrum board or an
02:51agile board or even slightly confusingly
02:56each day during the sprint there's a
02:57scrum meeting it's a standard meeting
02:59where the team takes a maximum of 15
03:01minutes to discuss progress and to
03:03identify any blockers
03:05at the end of the sprint the work
03:07completed during the sprint is packaged
03:10any incomplete items are returned to the
03:13the sprint ends with two rituals the
03:15sprint review which is a demonstration
03:17of new functionality to the stakeholders
03:20and the sprint retrospective which is an
03:22examination of what went well what went
03:25badly what could be improved the aim of
03:27the retrospective is to ensure that the
03:29next sprint is more efficient and
03:31effective than the last
03:35kanban does a few things differently
03:38there's no two-week sprint kanban is a
03:42and of course there's no sprint backlog
03:44the pull system in kanban happens in a
03:46different way via work in progress
03:50each column on the kanban board has a
03:52work in progress limit related to the
03:54team's capacity for example a team with
03:56two developers would set a limit between
03:58two and four items the lower the better
04:02let's see the pull system in action
04:05when testing of a particular feature is
04:07complete the corresponding ticket moves
04:10the empty column is a signal to the
04:12previous column to send another ticket
04:16similarly when the build column is
04:18almost empty it's a signal to the dev
04:20team to select another high priority
04:22item from the backlog that's the pull
04:25kanban has a number of rituals in common
04:27with scrum although the naming is
04:29slightly different daily stand-up
04:31meetings demos for stakeholders and
04:37so now you know the difference between
04:38scrum and kanban two important things to
04:43first thing neither scrum nor kanban are
04:45as prescriptive as i may have made them
04:47appear high performing teams discover
04:50what works for them and flex the system
04:54secondly i've put together a cheat sheet
04:56for you that covers everything that
04:58we've talked about today plus some
04:59additional notes that i think you will
05:01find useful you can grab a copy from my
05:03blog via the link that you'll find
05:05somewhere around this video
