Comparing Project Management Methodologies: DAD, SAFe, and Scrum

This report provides a detailed comparison of three project management methodologies: Disciplined Agile Delivery (DAD), Scaled Agile Framework (SAFe), and Scrum. It explores the core processes, roles, artifacts, benefits, complexities, and tools associated with each methodology, using tables to facilitate a structured comparison across various domains. The report begins with an introduction to project management methodologies and their significance in achieving business success. It then delves into a comparative analysis of DAD, SAFe, and Scrum, highlighting their strengths and weaknesses. The report examines the processes, roles, artifacts, benefits, complexity, usage, and tools associated with each methodology. Finally, the report concludes with a recommendation on which methodology would be most successful for a company, providing justification for the choice. This comprehensive analysis is designed to provide a clear understanding of these methodologies and their practical applications.

Running head: PROJECT MANAGEMENT METHODOLOGY
Project Management Methodology
Name of the student:
Name of the university:
Author note:

1PROJECT MANAGEMENT METHODOLOGY
Table of Contents
Introduction:...............................................................................................................................3
Comparison between the project management methodologies:.................................................3
Recommendation on methodology that could be applied in company:.....................................4
Conclusion:................................................................................................................................4
References:.................................................................................................................................4

2PROJECT MANAGEMENT METHODOLOGY
Introduction:
Project management methodologies were first defined in the year 1960 in order to
find effective ways in business to gain profit and to organize the works defined in a project in
a structured way. Project management, practices are defined as a mixture of method,
processes and practices that are logically related in order to plan the best and to develop the
control and delivery of the project to gain complete success in the project. The project
organization procedures help in assisting the plan managers (Flora & Chande, 2014). When a
project us carried out systematically then there are more chances of success. For the
systematic execution there are already many project organization methods available for
project managers. There are diverse types of project administration methodologies like
PRINCE2, CPM, Disciplined Agile Delivery, Scaled Agile Framework, SCRUM, Six Sigma
and many more. Previously project management methodologies re mainly evolved from a
less complex reality of controlling small and easy projects. Many organizations and project
management communities in today’s world do not offer proper development management
methodologies as the project management practices are typically custom built. As modern-
day projects are often larger and more complex, they involve greater risks in them. Modern
projects consist of multiple delivery units, vendors, subcontractors, customer panels whose
activities are responsible for the effective delivery of organisations. So, organisations need to
build their own methodologies, their own methods that perfectly fits the type of scheme, the
size and the complexity of the project that they have. Managing projects in IT is different
than managing a project and healthcare, is different than managing projects in the oil and gas.
Though some of the project management principles are common but the methods or the
project management methodologies that are applied are highly reliant on the type of
manufacturing, its size and the type of project complexity that it supports. Most of the times
project management methodologies can be too complex for the projects to which they are

3PROJECT MANAGEMENT METHODOLOGY
applied, and often they are difficult to understand. Project management methodologies are
very much important for projects success and to improve the performance of the projects
(Ambler & Lines, 2016). This report is prepared to discuss about three methodologies
including Disciplined Agile Delivery, Scaled Agile Framework and SCRUM and to compare
these practices based on certain comparison factors.
Comparison between the project management methodologies:
Compariso
n Factor
DAD
(Disciplined Agile
Delivery)
SAFE
(Scaled Agile Framework)
SCRUM
Process Disciplined Agile
Delivery process is a
type of choice agenda
that enabled light
weight guidance in
order to help the
organisations to
initiate their process in
a subtle manner while
providing a basis for
the agility of the
business (Mandal &
Pal, 2015). The
processes of
Disciplined Agile
Delivery project
management
methodology include
the following-
Inception-
 Emerging
common
dream
 Bring into line
with enterprise
course
 Discovering
initial
possibility
 Classifying
risks
Construction-
 Producing a
Scaled Agile Framework is
type of easily available
information base in online
platform that allows users to
apply practices of lean- agile
method at the enterprise
levels. It delivers a
lightweight experience for the
teams responsible for
software development. The
whole framework of the
Scaled Agile Framework
project management
methodology is divided into
three consecutive segments
which includes teams,
programs and portfolio.
The segment of team is
responsible for the following
processes-
 Defining the user
stories
 Prioritizing the user
sections
 Making team
accumulation
 Generating Sprint
Accumulation
 Leading daily
standups
 Showing Sprint
Retrospective
The segment of the program
The SCRUM
framework in project
management
methodology helps team
to work in a unified
way. It encourages team
members to learn by
gaining experiences and
helps in self organizing
while working on
different problem data
seta. The SCRUM
framework is somewhat
heuristic and is based on
continuous process of
learning.
The process of SCRUM
project management
methodology includes
the following features-
 It defines the
user stories
 Conducts sprint
planning
 Executes sprint
(Dulock & Long,
2015)
 Determines the
shippable
products
 Conducts the
review of the
sprints

4PROJECT MANAGEMENT METHODOLOGY
potential
consumable
solution
 Addressing
change in the
need of the
stake holders
 Improving
Quality
 Moving earlier
to a deployable
issue
Transition-
 It ensures
whether the
solution is
consumable
 Deploying the
answer
Ongoing-
 Grow team
members
 Leverages and
enhances the
existing
infrastructure
 Governs the
delivery team
 Addresses the
risks
includes the following
processes-
 Defining the features
 Creating program
Kanban
 Conducting system
demos
 Establishing PI
objectives
 Conducting WSJF
 Creating program
backlog
 Conducting inspect
and adapt
The processes under the
portfolio segment includes-
 Founding strategic
melodies
 Making portfolio
accumulation
 Bring into line the
budgets with the value
rivulets
 Creating portfolio
Kanban
 Defining epics
 Conducts
retrospective
 Conducts daily
standups
 Creates backlogs
of sprints.
Roles The principles behind
Disciplined Agile
Delivery process
includes- enterprise
awareness, optimized
flow, delighted
customers, context
counts, pragmatism,
being unique and
opting for a good
choice. It consists of
two types of roles
primary and
secondary. The
primary roles of
Disciplined Agile
Delivery include-
 Product
proprietor
 Architecture
The roles behind the Scaled
Agile Framework project
management methodology
includes three segments with
specific roles which are as
follows-
Team-
 Product owner
 Team
 Scrum Master
Portfolio-
 Lean portfolio
management
 Enterprise Architect
 Epic owners
Program-
 Product management
 System Architect
 Release train engineer
A SCRUM team
essentially has three
specific roles-
 Product owner
 Development
team
 SCRUM master
As SCRUM teams are
usually cross functional,
the development team
often includes designers,
testers, operation
engineer, developers
and UX specialists
(Alqudah, & Razali,
2016). The roles of each
of the categories
include-
SCRUM product
owner-

5PROJECT MANAGEMENT METHODOLOGY
possessor
 Investors
 Crew lead
 Team members
Whereas the
secondary characters
include-
 Specialists
 Area expert
 Integrator
 Practical
Expert
 Independent
Testers
 Builds and
manages the
product backlog
 Gives the team a
clear guidance
about the
delivery features
 Decides about
the shipments of
the products
SCRUM development
team-
 They practice
the sustainable
development
processes
 The team
members have
different skill
sets which are
essential to
deliver work
 Ensures
successful
completion of
the sprints
SCRUM Master-
 They are
responsible for
training the
teams, product
owners and
businesses that
runs under the
SCRUM
process.
 Understands the
work that are
done by the team
members
 Helps in
optimizing the
transparency and
flow in the
delivery of work.
Artifacts The creation of artifact
of the Disciplined
Agile Delivery process
mainly depends on the
data warehousing and
The artifacts of the Scaled
Agile Framework project
management model are
defined founded on the three
categories that are found in
The SCRUM artifacts
help in providing a key
information about the
scrum team and its stake
holders (Bass, 2016). It

6PROJECT MANAGEMENT METHODOLOGY
the business
intelligence (Larson &
Chang, 2016). Since
last few years various
project management
teams have started
adopting the agile
approach towards
developing data
warehouse and
business intelligence
via techniques like
agile data modelling,
agile data testing,
refactoring database
and many more. The
relics of the
Disciplined Agile
Delivery project
management
methodologies
include-
 Initial vision
and funding
 Technology
roadmap
 Business road
map
 Original
architectural
vision
 Consumable
solution
 Funding and
response
 Release plan
 Iteration
Accumulation
this model.
Portfolio-
 Portfolio Vision
 Business and style
epics
 Portfolio
accumulation
 Investment themes
Program-
 Apparition
 Program backlog
 NFR’s
 Planning runway
 Metrics
 Product roadmap
 Business and
construction features
Team-
 Team accumulation
 Sprint areas
 Spikes
 Working software
 Team PSI objective
gives an idea of the
products that are under
the development, the
activities that are needed
to be planned and the
activities that are
already done in the
project (Permana,
2015). The artifacts of
the SCRUM project
management model
include-
 Sprint Goal
 Sprint
Accumulation
 Burn down
Chart
 Product Vision
 Augmentation
Benefits The benefits of the
Disciplined Agile
Delivery methodology
are as follows-
 The project
management
methodology is
well proven,
documented
and flexible
(Ebert &
Paasivaara,
The benefits of the Scaled
Agile Framework project
organization model include-
 Flexibility
 Hybrid framework
 Milestone phases with
large scale agile
delivery support
The benefits of the
SCRUM project
management model are
as follows-
 It helps in
gearing up
separate teams
and small
organisations
 It is easier to
tool as compared
to Disciplined

7PROJECT MANAGEMENT METHODOLOGY
2017)
 It has clear
parts, events
and relics
 The project
management
process is
ascendable
from levels
starting from 2,
3 and 4.
Agile Delivery
and Scaled Agile
Framework
project
management
model
Complexity The difficulty of the
Disciplined Agile
Delivery project
management
methodology is
medium.
The complication of the
Scaled Agile Framework
project management model is
high (Turetken, Stojanov &
Trienekens, 2017)
The complication of the
SCRUM project
management
methodology is low
(Laanti, 2014).
Usage The project
management
methodology of
Disciplined Agile
Delivery can be
scalable through entire
organisation and hence
not prescriptive.
The project management
methodology of Scaled Agile
Framework can be scalable
throughout the entire
organisation and hence it is
very much prescriptive.
The project
management
methodology of
SCRUM can only be
scalable up to the team
level (Darwish &
Megahed, 2016).
Tools The tools that are used
in the Disciplined
Agile Delivery project
management
methodology includes-
 Microsoft TFS
 Blueprint
 Transformation
Advisor
 IBM Rational
Method
Composer
(RMC)
 Method Park
Stages
The tools that are used in the
Scaled Agile Framework
project management
methodology includes-
 Atlassian- JIRA
 CA Technologies- CA
Agile Central
 Microsoft -In Cycle
 VersionOne-
VersionOne
The tools of the
SCRUM project
management
methodology include-
 One2Team
 Allocable
 Target Process
 Agile Zen
 Sciforma
 CA Agile
Central
 Smart Core
 You Track
Recommendation on methodology that could be applied in company:
Scaled Agile Framework project management methodology is a prescriptive approach for
disintegrating larger creativities into small brooks of work while implementing sum of teams

8PROJECT MANAGEMENT METHODOLOGY
in a equivalent way with timely additions of the works and their distribution to the stake
holders. In cases where industries lack the framework for scaling the large initiatives, The
Scaled Agile Framework model becomes extremely beneficial. But according to few reports
it is seen that companies are approaching towards the Disciplined Agile Delivery project
management methodology over the Scaled Agile Framework. Inn companies even though
they are lacking consistency in their working approach still they are more enthusiastic
towards choosing Disciplined Agile Delivery rather than Scaled Agile Framework. The
reasons for which they found that Scaled Agile Framework is not working for their
companies are-
1. The level of disruption that was required in order to roll out the Scaled Agile
Framework model across the organization was not appetizing.
2. The investments that are done in the training and the overheads that are associated
with the running procedure of the Scaled Agile Framework program are too high.
3. Scaled Agile Framework was not applicable for all types of project and so there was a
need of another type of framework for the company.
Thus, for all these reasons it is recommended to choose Disciplined Agile Delivery
project management model in place of Scaled Agile Framework project management
methodology.
In other case when comparison comes between Disciplined Agile Delivery project
management methodology and SCRUM project management methodology, it is often
seen that companies generally opt for the Disciplined Agile Delivery project management
methodology over SCRUM. Disciplined Agile Delivery project management
methodology addresses the innumerable issues that are often left in the SCRUM project
management model. Disciplined Agile Delivery goes into clear detailing of the issues

9PROJECT MANAGEMENT METHODOLOGY
than SCRUM. While using the SCRUM model organisations often need to spend huge
amount of money for determining the issues but while using the Disciplined Agile
Delivery project management model, it becomes much easier to solve the issues. The
primary reason for choosing Disciplined Agile Delivery over SCRUM is that the
Disciplined Agile Delivery project management methodology increases the chance to
improve the efforts that are done in the process with success without spending huge
amounts. Disciplined Agile Delivery project management methodology follows a holistic
approach to deliver solution opposing the prescriptive of the SCRUM project
management framework. Besides all these reasons there are few other reasons for which
Disciplined Agile Delivery project management methodology is better than SCRUM. The
reasons are listed below-
1. Disciplined Agile Delivery extends SCRUM
2. Disciplined Agile Delivery focuses on solution distribution and not just only software
distribution
3. Disciplined Agile Delivery explicitly supports the full transfer of the lifecycle
4. Disciplined Agile Delivery provides explicit advice on tailoring
5. Disciplined Agile Delivery reflects the realities of the agile enterprise
6. Disciplined Agile Delivery addresses all features of agile explanation delivery
7. Disciplined Agile Delivery certification is very much respectable than SCRUM
8. Disciplined Agile Delivery project management methodology is scalable and provides
real time advice.
9. Disciplined Agile Delivery provides more options than SCRUM.
Thus, due to all these reasons it us recommended to use the Disciplined Agile
Delivery project management methodology instead of SCRUM in companies.

10PROJECT MANAGEMENT METHODOLOGY
Hence while comparing the project management methodologies it is seen that the
Disciplined Agile Delivery project management methodology is much more beneficial for
using in companies than the Scaled Agile Framework and the SCRUM project
management methodologies.
Conclusion:
In conclusion it can be said that project management is an art of managing projects
and their deliverables with the finished services or products. There are several different ways
by which project managements can be executed. Project management refers to identifying of
the objects of the project and balancing the same while meeting demands of the stakeholders
ensuring that all the demands and purpose of the project are achieved. Thus, in order to
ensure the objectives of a project it is necessary to follow a structured approach towards
managing the practices of the project works and helping in the organizational development
procedure. Here in comes the importance of project management methodologies. Project
management methodologies helps in describing the system in a project. Before starting any
project, it is essential to chose the correct project management methodology that suits the
company’s project preferences. Among the different project management methodologies the
Disciplined Agile Delivery, Scaled Agile Framework and SCRUM project management
methodologies are discussed in the report and from the comparison that is reflected it can
thus be concluded that the Disciplined Agile Delivery project management methodology
plays a vital beneficial role in managing ,major projects in different companies and this is the
reason why companies and organisations are now using the Disciplined Agile Delivery
project management methodology instead of using the Scaled Agile Framework or the
SCRUM project management methodologies. The Disciplined Agile Delivery project
management methodology is basically a goal determined approach that allows avoiding being
rigid and hence is more supple and scalable than any other project management

11PROJECT MANAGEMENT METHODOLOGY
methodologies. Disciplined Agile Delivery extends the focus on the construction life-cycle of
SCRUM in order to discourse the end to end transfer of the project life cycle and project
initiation to the end operators. The framework of the Disciplined Agile Delivery process
advices about the technical process that is missing in the project lifespan and assistances in
governing the strategies that needs to be implemented in the project initiation phase.
Disciplined Agile Delivery effectively discourses the supple observes across the delivery
lifecycle of the project starting from its requirements, development, architecture to its
delivery and governance. Disciplined Agile Delivery is one of the best practice techniques in
project management methodologies that best suits in any project of any company fitting in the
end to end process for successful delivery of complex projects.

12PROJECT MANAGEMENT METHODOLOGY
References:
Alqudah, M., & Razali, R. (2016). A review of scaling agile methods in large software
development. International Journal on Advanced Science, Engineering and
Information Technology, 6(6), 828-837.
Ambler, S. W., & Lines, M. (2016, January). The disciplined agile process decision
framework. In International Conference on Software Quality (pp. 3-14). Springer,
Cham.
Bass, J. M. (2016). Artefacts and agile method tailoring in large-scale offshore software
development programmes. Information and Software Technology, 75, 1-16.
Darwish, N. R., & Megahed, S. (2016). Requirements engineering in scrum
framework. International Journal of Computer Applications, 149(8).
Disciplined Agile (DA). (2019). Retrieved from http://disciplinedagiledelivery.com/
Dulock, M., & Long, H. (2015). Digital collections are a sprint, not a marathon: Adapting
Scrum project management techniques to library digital initiatives. Information
Technology and Libraries, 34(4), 5-17.
Ebert, C., & Paasivaara, M. (2017). Scaling agile. IEEE Software, 34(6), 98-103.
Flora, H. K., & Chande, S. V. (2014). A systematic study on agile software development
methodologies and practices. International Journal of Computer Science and
Information Technologies, 5(3), 3626-3637.
Laanti, M. (2014, May). Characteristics and principles of scaled agile. In International
Conference on Agile Software Development (pp. 9-20). Springer, Cham.

13PROJECT MANAGEMENT METHODOLOGY
Larson, D., & Chang, V. (2016). A review and future direction of agile, business intelligence,
analytics and data science. International Journal of Information Management, 36(5),
700-710.
Mandal, A., & Pal, S. C. (2015). Achieving agility through BRIDGE process model: an
approach to integrate the agile and disciplined software development. Innovations in
Systems and Software Engineering, 11(1), 1-7.
Permana, P. A. G. (2015). Scrum method implementation in a software development project
management. International Journal of Advanced Computer Science and
Applications, 6(9), 198-204.
Scaled Agile Framework – SAFe for Lean Enterprises. (2019). Retrieved from
https://www.scaledagileframework.com/
Turetken, O., Stojanov, I., & Trienekens, J. J. (2017). Assessing the adoption level of scaled
agile development: a maturity model for Scaled Agile Framework. Journal of
Software: Evolution and Process, 29(6), e1796.