Project Management History and Relevance to Software Development

Running head: PROJECT MANAGEMENT HISTORY AND RELEVANCE TO SOFTWARE
DEVELOPMENT
Project Management history and relevance to Software Development
Name of the Student
Name of the University
Author’s note

1PROJECT MANAGEMENT HISTORY AND RELEVANCE TO SOFTWARE DEVELOPMENT
Table of Contents
1. Introduction..................................................................................................................................2
2. Discussion....................................................................................................................................3
2.1 Waterfall History and Review...............................................................................................3
2.2 Waterfall Issues and Success.................................................................................................4
2.3 Agile History and Review.....................................................................................................5
2.4 Agile Issues and Success.......................................................................................................7
2.5 Observation of Current Industry Trends and Methodology Selection...................................8
3. Conclusion...................................................................................................................................9
References......................................................................................................................................11
Bibliography..................................................................................................................................14

2PROJECT MANAGEMENT HISTORY AND RELEVANCE TO SOFTWARE DEVELOPMENT
1. Introduction
The software project management can be defined as an art and rigorous planning based
on the leading software development projects. The software project management can be defined
as an art in which the software projects are previously planned, monitored, implemented and
controlled by efficient project managers. With the introduction of computers, the industry of
software development has grown rapidly (Fuller et al., 2017). In order to manage the new efforts
based on development, the various companies have majorly applied the knowledge of various
project management methods to design the project schedules, allocate costs and implement other
features for the purpose of project development.
Agile software development can be defined as an approach to the process of software
development based on which the solutions and requirements evolve with a collaborative effort.
In the 1990s, a vast number of methods based on software development had evolved in order to
handle the existing heavy weight methods, which were also considered as micro-managed,
planned and regulated (Abrahamsson et al., 2017). The methods of agile development break the
work of product development into various smaller increments that are able to minimize the
amount of planning of work. The various iterations are considered as short time-frames that
normally last for a few weeks.
This report thus discusses the history of a waterfall and agile method of software
development, the issues discovered and the success criteria of the software development process.
The report also discusses the current trends within the industry and the discussion about the
chosen methodologies that could put an impact on the organizational procedures.

3PROJECT MANAGEMENT HISTORY AND RELEVANCE TO SOFTWARE DEVELOPMENT
2. Discussion
2.1 Waterfall History and Review
The Structured Systems Analysis and Design Method or the Structured approach are
defined as a systems approach for the purpose of conducting an analysis and design of the
Information Systems. This approach can also be defined as a waterfall method based on the
purpose of performing analysis and design over the information systems (George, 2019). The
principle design of the structured approach of waterfall method had initiated from the 1980s and
thus the several versions had evolved further.
On the other hand, the object-oriented analysis can be defined as a technical approach for
the purpose of analyzing and then design an application, business or system. The object-oriented
waterfall approach with the addition of visual modeling helps in fostering a better form of
stakeholder communication and improving product quality. The object-oriented approach has
been considered as the best form of a modern software engineering technique that is mainly
conducted in an incremental and iterative way (Dennis, Wixom & Tegarden, 2015). In the initial
days of the development of this approach, there were many different computing methodologies
in relation to objected-oriented modeling and software development. In that time there were no
such standard notations, process guides, and consistent terms, which were considered as the
major concerns during that time. The lack of such necessities had degraded the efficiency of
communication and also lengthened the learning curves.
The traditional structured approach views the entire system from a top-down view. It has
been described as a formalized step-by-step approach that is in relation to software development
and thus consists of various phases or activities (Buede & Miller, 2016). In both of the
approaches based on the Waterfall method, the process of software development follows a step-