Up next in 10
Agile Frameworks Explained | Scrum, Kanban, XP, FDD, DSDM, AgileUP
Jun 27, 2025
Are you preparing for the PMP exam and confused about all the Agile frameworks? In this video, we break down six major Agile frameworks you must know: ✅ Scrum ✅ Kanban ✅ Extreme Programming (XP) ✅ Feature-Driven Development (FDD) ✅ Dynamic Systems Development Method (DSDM) ✅ Agile Unified Process (AgileUP) Each section covers key concepts, unique characteristics, and their relevance to the PMP exam. Plus, you'll get exam-style questions with explanations to help reinforce your understanding. 🎯 Perfect for PMP exam prep and project managers who want to grasp Agile fundamentals across various frameworks. ⏩ Use the video chapters to skip directly to each framework if you're reviewing. 0:00 Intro 0:48 Scrum 6:06 Kanban 9:44 XP 13:09 FDD 16:37 DSDM 20:11 AgileUp
View Video Transcript
0:00
are you preparing for the PMP exam and
0:02
trying to make sense of all the agile
0:04
frameworks in this video we'll walk
0:06
through six major agile frameworks that
0:09
you need to know including Scrum Conbon
0:11
Extreme Programming Feature-driven
0:13
Development DSDM and Agile Unified
0:16
Process we'll explain what each one is
0:18
how it works and what makes it unique
0:20
especially in the context of the PMP
0:23
exam at the end of each framework we
0:25
will go over a practice question
0:26
together to help reinforce the learning
0:29
if you just want to review the agile
0:31
framework without the question you can
0:33
use the timeline below to skip to the
0:35
next framework make sure to watch until
0:37
the end for a clear understanding of
0:39
each framework along with key concepts
0:42
and exam function insights that can help
0:44
you feel more confident on test day
0:46
let's begin one scrum scrum is the most
0:51
widely used agile framework it's built
0:53
around short time box iterations called
0:56
sprints usually lasting between 2 to 4
0:59
weeks at the end of each sprint the team
1:01
delivers a working increment of the
1:03
product key roles in scrum include
1:06
product owner owns the product backlog
1:08
and is responsible for maximizing the
1:11
value of the product they prioritize
1:13
work items based on business value and
1:16
customer needs scrum master is a servant
1:19
leader who ensures the team understands
1:21
and applies scrum principles they remove
1:24
impediments and foster team
1:25
collaboration development team is
1:28
self-organizing and crossf functional
1:30
they select and commit to the work for
1:32
the sprint and build the deliverables
1:35
key artifacts in scrum include product
1:38
backlog this is a prioritized list of
1:42
all the work needed to improve the
1:44
product it's dynamic and evolves as the
1:46
product and business needs change it is
1:49
owned and maintained by the product
1:51
owner items may include features bugs
1:54
technical tasks or research the product
1:57
backlog is ordered by priority with high
2:00
value items at the top it's never
2:02
considered complete it's a living
2:04
document sprint backlog this is a subset
2:08
of the product backlog that the team
2:09
commits to completing during a sprint it
2:12
is owned by the development team it
2:14
includes selected backlog items and a
2:16
plan for delivering them it's flexible
2:19
during the sprint in terms of how the
2:21
work is done but the scope generally
2:24
stays stable increment this is the sum
2:27
of all completed product backlog items
2:30
during a sprint and includes the work
2:31
from all previous sprints it must meet
2:34
the team's definition of done which is a
2:36
shared understanding of what it means
2:38
for work to be complete the product
2:40
owner reviews the increment during the
2:42
sprint review to determine if it's ready
2:44
to release scrum also includes events
2:47
such as sprint planning the team
2:48
discusses what can be delivered and how
2:50
it will be achieved daily scrum is a
2:53
short daily meeting of 15 minutes to
2:55
sync up and plan the next 24 hours
2:59
sprint review is held at the end of the
3:01
sprint to inspect the increment and
3:03
adapt the product backlog sprint
3:05
retrospective typically occurs after the
3:08
sprint review when the team reflects on
3:10
the sprint and identifies improvements
3:11
for the next one for the PMP exam expect
3:15
questions about who owns which artifacts
3:18
how the team commits to the work and how
3:20
value is delivered through short
3:22
iterative cycles also know how Scrum
3:25
supports self-organization frequent
3:27
feedback and transparency let's look at
3:30
a Scrum question together a company is
3:33
developing a new mobile application
3:34
using Scrum during sprint planning the
3:37
team selects several product backlog
3:39
items but midway through the sprint a
3:41
few team members express concerns that
3:43
some selected items may not be completed
3:45
by the end of the sprint the product
3:47
owner insists that all selected items
3:50
must be completed since they were agreed
3:52
upon during sprint planning the scrum
3:55
master observes rising tension and
3:57
reminds the team of scrum values as the
4:00
project manager what is the most
4:02
appropriate response to ensure alignment
4:04
with scrum principles and support value
4:07
delivery a remind the team that the
4:09
sprint commitment means all selected
4:12
items must be delivered regardless of
4:14
unforeseen challenges b coach the
4:18
product owner that the team owns the
4:20
sprint backlog and that scope
4:21
adjustments may occur as they
4:23
self-organize around their sprint goal c
4:26
advise the team to raise a change
4:28
request to formally reduce the sprint
4:30
scope d support the product owner in
4:33
holding the team accountable for
4:34
delivering all the selected backlog
4:36
items to maintain transparency and trust
4:39
you can pause the video here if you need
4:41
more time all right let's walk through
4:43
this together the correct choice is B in
4:47
Scrum the development team owns the
4:49
sprint backlog and is empowered to
4:51
self-organize to meet the sprint goal
4:53
while the team commits to the goal
4:55
during sprint planning they do not
4:56
commit to every selected product backlog
4:59
item scrum supports adaptation
5:01
transparency and frequent inspection
5:03
which means teams can adjust within the
5:05
sprint if necessary the product owner
5:07
owns the product backlog but the sprint
5:09
backlog belongs to the team coaching the
5:12
product owner on these role boundaries
5:14
reinforces collaboration and agility
5:17
choice A is incorrect sprint planning
5:20
leads to a commitment to a sprint goal
5:22
not a guarantee that all backlog items
5:25
will be completed scrum recognizes that
5:28
work may evolve and delivery of value is
5:30
prioritized over rigid scope adherence
5:34
choice C is incorrect scrum does not
5:36
involve formal change requests for
5:38
adjusting the sprint scope the team
5:40
inspects and adapts their work through
5:42
the daily scrum and other ceremonies
5:44
enabling flexibility without
5:46
bureaucratic overhead choice D is
5:49
incorrect holding the team strictly
5:51
accountable for all items selected in
5:53
sprint planning overlook Scrum's
5:55
empirical nature it may also harm
5:57
psychological safety and discourage
5:59
transparency especially when unforeseen
6:02
issues arise okay let's move on if you
6:05
are ready two conbon conbon focuses on
6:09
visualizing workflow and limiting work
6:12
in progress to improve efficiency unlike
6:14
scrum conbon does not use sprints
6:17
workflows continuously through stages
6:19
defined on a conbon board such as to-do
6:22
in progress and done core concepts
6:25
include work in progress limits controls
6:28
how many tasks are in progress at once
6:31
to avoid overload pull-based system the
6:34
team members pull work based on capacity
6:36
rather than being assigned tasks delete
6:39
time is the total time from request to
6:42
delivery cycle time is the time taken
6:45
from the start of the work to completion
6:48
throughput is the number of items
6:51
completed in a time frame conbon is
6:54
great for environments with ongoing
6:55
tasks like operations or service teams
6:59
for the PMP exam you may see conbon in
7:02
scenarios involving flow-based work
7:05
visual management or continuous delivery
7:08
be prepared to identify and explain how
7:10
metrics like lead time and work in
7:12
progress limits are used to improve
7:15
efficiency let's look at a conbon
7:17
question together your organization is
7:20
using a conbon system to manage support
7:23
tickets for its software platform
7:25
recently stakeholders have raised
7:27
concerns that requests are taking too
7:29
long to complete upon reviewing the
7:31
conbon board you notice several tickets
7:34
sitting in the in progress column for
7:36
extended periods the team explains they
7:38
are multitasking across multiple work
7:40
items to keep everyone busy as the
7:43
project manager what is the best action
7:45
to improve flow efficiency and reduce
7:47
delivery times a encourage the team to
7:51
prioritize higher value tickets and
7:53
focus on completing those first b
7:55
increase the number of items in progress
7:58
to reduce idle time and fully utilize
8:00
team capacity c implement work in
8:04
progress limits and review lead time
8:06
trends to identify and remove
8:08
bottlenecks d restructure the team to
8:11
assign individuals to specific types of
8:14
tickets to streamline responsibility you
8:16
can pause the video here if you need
8:18
more time all right let's walk through
8:21
this together the correct choice is C in
8:24
conbon work in progress limits are a
8:27
core practice used to prevent
8:28
overloading the system encourage focus
8:30
and improve flow efficiency by setting
8:32
work in progress limits the team will be
8:34
forced to finish current work before
8:36
starting new items helping reduce lead
8:38
time and deliver value more quickly
8:40
monitoring leadtime trends allows for
8:42
identifying bottlenecks and making
8:43
datadriven improvements which directly
8:45
addresses the stakeholder concern choice
8:48
A is incorrect while prioritization is
8:51
important it doesn't directly address
8:53
the root cause of delayed flow if
8:55
multitasking continues work will still
8:58
be slow even for high priority tickets
9:01
without limiting work in progress
9:02
focusing on priority won't fix the
9:05
inefficiency choice B is incorrect this
9:08
approach worsens the problem increasing
9:11
work in progress leads to context
9:13
switching longer cues and reduced team
9:15
focus ultimately increasing lead time
9:17
and reducing throughput which is the
9:19
opposite of Conbine's intent choice D is
9:22
incorrect reassigning roles may provide
9:25
short-term clarity but does not solve
9:27
the systemic issue of too much work in
9:30
progress conbon emphasizes teamwide
9:33
ownership of flow not rigid role
9:35
assignments and the real opportunity for
9:37
improvement lies in controlling work in
9:39
progress and monitoring flow metrics
9:42
okay let's move on if you're ready three
9:45
extreme programming extreme programming
9:48
XP is a software ccentric agile
9:51
framework that emphasizes technical
9:53
excellence rapid feedback and customer
9:55
involvement pxp practices include our
9:59
programming is when two developers work
10:01
together on the same code improving
10:03
quality and knowledge sharing testdriven
10:06
development TDD means write tests first
10:09
then build just enough code to pass the
10:11
test continuous integration the
10:14
developers integrate code frequently to
10:16
catch defects early refactoring improves
10:20
code structure without changing behavior
10:23
lastly XP emphasizes simple design and
10:26
small releases xp also encourages
10:30
on-site customer presence and working at
10:32
a sustainable pace to avoid burnout for
10:35
the PMP exam questions may focus on
10:37
agile quality practices fast feedback
10:40
cycles or how to improve team
10:42
collaboration and technical outcomes xp
10:44
is often the correct context when the
10:47
scenario emphasizes software engineering
10:49
practices let's look at an extreme
10:51
programming question together a software
10:54
development team using extreme
10:56
programming is experiencing issues with
10:58
defects being discovered late in the
11:01
iteration the team currently runs tests
11:04
at the end of the development cycle and
11:05
individual developers write and commit
11:08
code independently the project manager
11:10
wants to improve code quality feedback
11:12
speed and collaboration what is the best
11:15
recommendation to align the team with XP
11:18
practices and improve outcomes a
11:21
introduce formal design reviews and
11:23
require signoff before coding starts b
11:27
encourage the use of pair programming
11:29
and test-driven development as standard
11:31
practices c extend iteration length to
11:35
allow for more time to test before
11:37
release d assign a dedicated QA team to
11:41
thoroughly test completed work at the
11:43
end of each iteration you can pause the
11:46
video here if you need more time all
11:49
right let's walk through this together
11:51
the correct choice is B in extreme
11:54
programming key practices like pair
11:56
programming and test-driven development
11:58
are designed to improve code quality
12:01
reduce defects and deliver fast feedback
12:03
pair programming enhances collaboration
12:06
and knowledge sharing while test-driven
12:08
development ensures that code is written
12:10
with testing in mind from the beginning
12:12
reducing late cycle bugs and promoting
12:15
cleaner design choice A is incorrect
12:18
while formal reviews may be useful in
12:20
traditional environments XP favors
12:23
lightweight continuous collaboration
12:25
over formal signoffs this choice slows
12:27
down feedback and doesn't support XP's
12:29
iterative adaptive approach to quality
12:32
choice C is incorrect extending the
12:35
iteration length contradicts the XP
12:37
principle of rapid feedback cycles xp
12:40
values short consistent iterations to
12:43
detect issues early and adapt quickly
12:46
more time to test at the end doesn't
12:48
prevent defects introduced early in the
12:50
process choice D is incorrect xp
12:54
promotes continuous testing and shared
12:56
ownership of quality not handoffs to QA
12:59
at the end a dedicated QA team working
13:02
after development violates XP's emphasis
13:04
on collaboration automation and built-in
13:08
quality okay let's move on if you are
13:11
ready four feature-driven development
13:15
feature-driven development FDD is a
13:17
model-driven short iteration process
13:19
designed for larger teams and structured
13:22
environments fdd process includes one
13:26
develop the overall model two build a
13:29
feature list three plan by feature four
13:34
design by feature five build by feature
13:38
each feature is a small client valued
13:40
function deliverable within 2 weeks or
13:42
less fdd introduces specific roles such
13:46
as chief programmer class owners and
13:48
domain experts it blends agile values
13:52
with structured practices to maintain
13:54
control and clarity across large-scale
13:56
development effort for the PMP exam be
13:59
familiar with FDD's emphasis on domain
14:02
modeling clear role separation and its
14:05
use in larger more hierarchal teams it's
14:08
often a match for questions involving
14:10
scalability or structured agile planning
14:13
let's look at a feature-driven
14:15
development question together a large
14:17
organization is developing a complex
14:19
financial platform using agile methods
14:22
the team has adopted feature-driven
14:23
development to better handle the size
14:25
and structure of the project during a
14:27
planning session several developers
14:29
express confusion about who is
14:31
responsible for breaking down features
14:33
into smaller tasks and how modeling
14:35
should fit into their workflow the
14:36
project manager wants to reinforce
14:38
proper process alignment with FDD
14:40
principles what is the most appropriate
14:43
action to support the team and ensure
14:46
clarity of roles and planning structure
14:48
a assign the scrum master to manage
14:51
modeling activities and delegate feature
14:53
breakdown to the team collectively
14:56
b remind the team that the chief
14:58
programmer is responsible for feature
15:00
breakdown and coordinating development
15:01
tasks c instruct business analysts to
15:05
complete the modeling upfront before
15:07
development starts to avoid confusion d
15:11
have all developers participate equally
15:13
in modeling and feature decomposition to
15:16
encourage shared ownership you can pause
15:18
the video here if you need more time all
15:21
right let's walk through this together
15:23
the correct choice is B in
15:26
feature-driven development there is
15:28
clear role separation the chief
15:30
programmer plays a central role by
15:32
coordinating the design and planning of
15:33
features including breaking down
15:35
features into smaller development tasks
15:37
this structure helps support scalability
15:39
and clarity of responsibilities in large
15:42
hierarchical teams domain modeling is
15:44
also a key initial activity in FDD often
15:47
facilitated by domain and technical
15:49
experts choice A is incorrect the scrum
15:53
master role is not part of the FDD
15:55
framework assigning modeling or planning
15:58
duties to a scrum master introduces
16:00
confusion
16:02
choice C is incorrect fdd emphasizes
16:05
collaborative modeling and incremental
16:07
planning not big upfront modeling having
16:10
business analysts do all modeling
16:12
upfront violates the iterative
16:14
feature-driven approach and reduces
16:16
developer engagement
16:18
choice D is incorrect while
16:21
collaboration is important FDD relies on
16:24
specific roles and responsibilities to
16:26
manage complexity at scale having all
16:28
developers equally manage modeling and
16:30
decomposition may result in
16:32
inconsistency and a lack of structure
16:35
which FDD is designed to address okay
16:38
let's move on if you are ready five
16:42
dynamic systems development method
16:44
dynamic systems development method DSDM
16:48
offers a controlled agile approach
16:50
suitable for organizations needing
16:52
strong governance it uniquely fixes time
16:56
and cost allowing scope to flex within
16:59
those constraints key practices include
17:03
Moscow prioritization is a technique
17:05
used to categorize requirements into
17:07
four levels of importance must have
17:09
should have could have and won't have
17:12
this time time boxing is a practice
17:15
where work is delivered within fixed
17:17
duration iterations active user
17:20
involvement ensures continuous alignment
17:23
integrated testing is embedded from the
17:25
start dsdm is ideal for regulated or
17:29
contratheavy environments that still
17:31
want to benefit from agile for the PMP
17:34
exam look for questions about balancing
17:36
agile with governance prioritizing
17:38
features effectively or working under
17:40
fixed time and budget constraints let's
17:43
look at a DSDM question together a
17:46
government agency is building a
17:48
compliance reporting system under a
17:50
fixed deadline and budget the team is
17:52
using dynamic systems development method
17:54
to balance agile delivery with
17:56
organizational governance requirements
17:58
partway through development a
18:00
stakeholder requests additional features
18:02
they consider valuable the team is
18:04
concerned about maintaining the timeline
18:06
and budget as the project manager what
18:09
is the most appropriate response based
18:12
on DSDM principles a add the requested
18:15
features and extend the timeline to
18:17
ensure stakeholder satisfaction b advise
18:21
the team to rep prioritize all features
18:23
and remove any that are less critical to
18:25
accommodate the new request c confirm
18:28
whether the new features are within the
18:30
could have category and reinforce that
18:33
time and cost are fixed in DSDM d inform
18:38
the stakeholder that no changes can be
18:40
made once development has started due to
18:42
the fixed scope you can pause the video
18:45
here if you need more time all right
18:47
let's walk through this together the
18:49
correct choice is C dsdm operates under
18:52
the principle of fixed time cost and
18:54
quality while flexibility comes from
18:56
adjusting the scope features are
18:58
prioritized using the Moscow soft method
19:01
must have should have could have won't
19:03
have when stakeholders request new
19:05
functionality the team must assess
19:07
whether the request falls into a could
19:09
have or won't have category allowing
19:12
delivery to continue without
19:14
jeopardizing commitments this approach
19:16
balances agility with governance in high
19:18
stakes environments choice A is
19:21
incorrect extending the timeline
19:23
violates the core DSDM principle that
19:25
time and cost are fixed satisfying the
19:27
stakeholder by changing these
19:29
constraints undermines predictability
19:31
and governance control choice B is
19:34
incorrect while rep prioritizing is
19:36
allowed removing existing features
19:38
without a formal review and alignment
19:40
with Moscow priorities risks omitting
19:42
must-have items the correct DSDM
19:46
approach is to assess new requests
19:48
against existing priorities not overhaul
19:51
the backlog without structured analysis
19:54
choice D is incorrect dsdm does allow
19:57
change but manages it through structured
19:59
prioritization saying no to all changes
20:02
contradicts DSDM's agile and adaptive
20:05
nature the key is to manage scope
20:07
dynamically while keeping time and cost
20:10
fixed okay let's move on if you are
20:13
ready six agile unified process agile
20:18
unified process or agile up adapts the
20:21
rational unified process to be agile
20:24
friendly it keeps a structured life
20:26
cycle but applies agile principles
20:28
throughout phases of agile up include
20:31
one inception involves defining business
20:33
case scope and feasibility two
20:37
elaboration involves identifying
20:39
architecture and risks three
20:42
construction involves developing the
20:44
product incrementally four transition
20:46
involves deploying the product and
20:48
supporting it postrelease agileup allows
20:51
for modeling and documentation but in a
20:54
lightweight approach keeping agile
20:56
values intact for the PMP exam agileup
21:00
may appear in questions about hybrid
21:02
project environments phase-based
21:04
delivery or balancing structure with
21:06
adaptability
21:08
let's look at an agileup question
21:10
together your organization is delivering
21:12
a large-scale enterprise solution using
21:14
a hybrid agile approach based on agile
21:17
unified process while working through
21:19
the construction phase one of the
21:20
executive sponsors expresses concern
21:22
about the lack of traditional
21:24
documentation and questions how quality
21:26
and governance are being ensured the
21:29
team is following agile practices but
21:31
also needs to maintain compliance with
21:32
organizational standard as the project
21:35
manager what is the best response to
21:37
address the sponsor's concerns while
21:39
remaining aligned with agile principles
21:42
a explain that agile projects do not
21:44
emphasize documentation and offer to
21:46
demonstrate working software instead b
21:50
highlight that agile up includes
21:51
structured phases and promotes just
21:53
enough documentation to support
21:55
governance and traceability c assure the
21:58
sponsor that documentation will be
22:00
created at the end of the project during
22:02
the transition phase d offer to switch
22:05
the project to a fully traditional model
22:07
to ensure alignment with stakeholder
22:09
expectations you can pause the video
22:12
here if you need more time all right
22:14
let's walk through this together the
22:17
correct choice is B agile Up is a hybrid
22:20
agile framework that combines the
22:22
structure of the unified process with
22:24
distinct phases like inception
22:26
elaboration construction and transition
22:29
with agile values like adaptability and
22:31
iterative delivery it supports just
22:33
enough documentation which satisfies
22:36
compliance and governance without
22:37
compromising agility this makes it ideal
22:40
for environments that need both
22:41
structure and flexibility choice A is
22:44
incorrect while agile values working
22:47
software over documentation completely
22:50
dismissing documentation especially in a
22:52
regulated or enterprise environment is
22:54
inappropriate choice C is incorrect
22:58
deferring documentation until the end of
23:00
the project ignores agile principles of
23:03
early and continuous feedback and puts
23:05
governance at risk agile Up encourages
23:08
documentation throughout the process
23:10
tailored to actual needs choice D is
23:13
incorrect switching to a traditional
23:15
model undermines the benefits of Agile
23:17
Up which was specifically chosen to
23:19
balance structure and agility changing
23:21
methodologies midstream can lead to
23:24
confusion disruption and reduce
23:25
stakeholder confidence before we wrap up
23:28
let's quickly review what we covered
23:31
scrum uses sprint-based delivery with
23:32
defined roles and key artifacts like
23:35
product backlog sprint backlog and
23:37
increment conbon uses visual workflow
23:40
management with continuous delivery and
23:42
work in progress limits
23:45
extreme programming emphasizes software
23:48
engineering excellence through practices
23:50
such as test-driven development and
23:52
continuous integration feature-driven
23:55
development is a feature- focused
23:57
framework suited for larger more
23:59
structured teams dynamic systems
24:02
development method combines agile
24:03
flexibility with project governance and
24:05
time boxing agile is a structured
24:08
phase-based agile approach designed for
24:10
hybrid environments that blend
24:12
predictive and adaptive practices each
24:14
of these frameworks has its place your
24:17
ability to recognize their differences
24:18
and apply them to project scenarios is a
24:21
valuable asset especially on the PMP
24:23
exam if you found this video helpful
24:25
please give it a thumbs up it helps
24:27
support the channel and lets us know
24:28
what content you want more of let us
24:31
know in the comment below if you want a
24:33
similar video for the scaled agile
24:34
frameworks and if you're preparing for
24:37
the PMP exam don't forget to subscribe
24:40
for more exam focused videos and visit
24:42
our website at pmasprint.com
24:45
for additional project management
24:47
resources
24:48
thanks for watching and I will see you
24:50
in the next video
#Jobs & Education