0:00
are you wondering if scrum or Canan is
0:01
the right agile framework for your team
0:04
hi I'm Andrew from PM aspirin scrum and
0:07
Canan are two of the most widely used
0:09
agile Frameworks and while they share
0:11
some common principles they approach
0:13
project management differently in this
0:15
video we'll explore how each framework
0:17
works and highlight their similarities
0:19
and differences let's Dive Right In
0:22
scrum is a structured framework that
0:24
organizes work into short and focus
0:26
Cycles called Sprints each Sprint
0:28
typically lasts 2 to 4 weeks and has a
0:30
clear goal to deliver a potentially
0:32
shippable product increment it all
0:35
begins with Sprint planning the team
0:37
gathers to decide what they can
0:39
realistically accomplish during the
0:40
Sprint pulling tasks from the backlog
0:43
into the Sprint backlog this backlog
0:45
acts as the to-do list for the Sprint
0:47
and once the Sprint starts it's locked
0:49
no new tasks can be added during the
0:52
Sprint daily standup meetings help the
0:54
team stay aligned these quick check-ins
0:57
are where everyone shares what they're
0:58
working on any challenge they're facing
1:01
and what they plan to do next at the end
1:04
of the Sprint the team holds two key
1:06
meetings first there's the Sprint review
1:09
where they showcase their completed work
1:10
to stakeholders and gather feedback then
1:13
comes the retrospective a reflection
1:15
session where the team discusses what
1:17
went well what didn't and how they can
1:20
improve in the next Sprint scrum also
1:22
defines specific roles to keep
1:24
everything running smoothly the product
1:26
owner prioritizes the work ensuring the
1:29
team focuses on on the most valuable
1:30
tasks the scrum Master acts as the
1:33
facilitator removing obstacles and
1:35
making sure the team follows agile
1:37
principles finally the development team
1:39
handles the actual work turning ideas
1:42
deliverables a key Concept in scrum is
1:45
velocity this metric shows how much work
1:47
the team completes in a Sprint often
1:49
measured in story points velocity helps
1:52
teams plan future Sprints more
1:53
accurately ensuring they deliver
1:55
consistent value con ban on the other
1:58
hand takes a more flexible approach
2:01
instead of time box Cycles it focuses on
2:03
continuous delivery and optimizing
2:05
workflow work is visualized on a board
2:08
typically divided into columns like
2:10
to-do in progress and done tasks flow
2:12
from one stage to the next giving
2:14
everyone a clear realtime view of
2:17
progress one of canan's standout
2:19
features is work in progress limits
2:22
these limits cap how many tasks can be
2:23
in progress at once why to prevent
2:27
bottlenecks and ensure the team isn't
2:30
when one task is completed the team
2:32
pulls in the next task from the backlog
2:36
capacity Camin also relies on Flow
2:38
metrics like cycle time which measures
2:41
how long a task takes from start to
2:42
finish and lead time which tracks the
2:45
total time from when a task is requested
2:47
to when it's completed these metrics
2:49
provide insights into the team's
2:50
efficiency and highlight areas for
2:52
improvement unlike scrum conand doesn't
2:55
define specific roles it's all about
2:58
flexibility allowing teams to adapt the
3:00
framework to fit their unique
3:02
needs while scrum and can band differ in
3:05
their structure they share workflow
3:06
similarities that align them under the
3:09
umbrella both Frameworks start with a
3:11
product backlog or a prioritized list of
3:14
tasks or user stories that need to be
3:15
completed these backlogs act as the
3:18
single source of Truth For What the team
3:19
should work on next tasks are typically
3:22
written as user stories which describe
3:24
the work from the user's perspective for
3:27
example as a customer I want to reset my
3:29
password so I can access my account this
3:32
shared use of user stories ensures the
3:34
team understands the work's purpose and
3:36
its value to the customer in both
3:39
Frameworks teams pull tasks from the
3:41
backlog to work on scrum teams do this
3:44
during Sprint planning deciding on a
3:46
fixed set of tasks to complete in the
3:48
Sprint conand teams pull tasks
3:50
continuously based on their capacity and
3:52
the workflows work in progress limits
3:54
while the timing differs the act of
3:56
selecting work based on priority is a
3:58
shared trait from a workflow perspective
4:01
both Frameworks emphasize visualization
4:04
scrum uses Sprint boards to track tasks
4:07
during a Sprint and can band uses a
4:09
continuous flow board in both cases the
4:11
board is divided into stages like to-do
4:14
in progress and done making the status
4:17
of each task transparent to everyone
4:20
while their goals are similar scrum and
4:21
can band take different paths to get
4:23
there scrum is all about structure using
4:26
Sprints to create focused time box
4:28
cycles of work con band on the other
4:30
hand is continuous and flexible allowing
4:33
tasks to flow through the system as
4:36
needed scrum has specific roles like
4:39
scrum master and product owner to guide
4:41
the process while comand leaves roles
4:43
undefined giving teams the freedom to
4:45
manage responsibilities in their own way
4:49
when it comes to boards scrum Sprint
4:51
board resets with every Sprint focusing
4:53
only on the current tasks con band's
4:55
board however visualizes the full
4:58
workflow and doesn't reset offering a
5:00
broader view of the team's overall
5:02
progress the way each framework handles
5:05
Improvement is another key difference
5:07
scrum relies on Sprint review and
5:09
retrospectives at the end of each Sprint
5:11
these sessions allow teams to gather
5:13
feedback reflect on their performance
5:16
and decide on actionable changes for the
5:18
next Sprint can ban however focuses on
5:21
real-time optimization by tracking flow
5:24
metrics like cycle time and identifying
5:26
bottlenecks as they happen Canen teams
5:29
continuously fine-tune their process
5:31
without waiting for a formal review the
5:33
choice between the two often comes down
5:35
to the type of work you do and your
5:38
preferences let's quickly recap scrum is
5:41
structured with time box Sprints defined
5:44
roles and metrics like velocity to guide
5:47
progress con ban is flexible focusing on
5:50
Continuous Flow work in progress limits
5:53
and real-time metrics like cycle time
5:57
both Frameworks emphasize transparency
5:59
collaboration and Improvement and that's
6:01
scrum versus Canin both Frameworks are
6:04
powerful tools and the best choice
6:06
depends on your team's goals in workflow
6:08
also you may want to learn about how to
6:10
combine these two Frameworks commonly
6:11
referred to as scrun bin if you found
6:14
this video helpful please give it a
6:15
thumbs up your support helps us create
6:17
more project management content and if
6:19
you haven't already please consider
6:21
subscribing to our channel for more
6:23
insights into agile and project
6:25
management let us know in the comment
6:27
below which framework your team prefers
6:30
questions thanks for watching and I'll
6:32
see you in the next video
