Unit 9 – IT Project Management (Part A)
Contents
Introduction:......................................................................................................................................2
Project Management Methodologies:...............................................................................................2
Waterfall............................................................................................................................................2
The principles of waterfall model are:...............................................................................................2
Rapid Application Development (RAD)..............................................................................................3
The principles of the RAD methodology are:.....................................................................................3
PRINCE2.............................................................................................................................................4
The principles of the PRINCE2 methodology are:..............................................................................4
Agile...................................................................................................................................................5
The principles of the Agile methodology are:....................................................................................6
The Ford Edsel (Failed Project) – Agile...............................................................................................6
The car industry in 1950s...................................................................................................................7
Why did Ford Edsel fail?....................................................................................................................7
How would the Ford Edsel have been successful?.............................................................................7
PlayStation 2 (Successful Project) – PRINCE2.....................................................................................7
How did the PlayStation 2 use PRINCE2 and how did it help make the project a success?...............8
Why was the PlayStation 2 a success?...............................................................................................8
Sony Betamax (Failed Project) – Agile................................................................................................8
Videotape format industry in early 1970...........................................................................................9
Why did Sony Betamax fail?..............................................................................................................9
How would the Sony Betamax have been successful?.......................................................................9
Conclusion:......................................................................................................................................10
Evaluation:.......................................................................................................................................10
Bibliography:....................................................................................................................................10
Learning Aim A: Investigate the principles and methodologies of IT
project management as used in industry
1|Page
, Unit 9 – IT Project Management (Part A)
Introduction:
In this assignment, I will be investigating different IT project management methodologies
that the company can use. I'll assess three different projects, each of which was completed
utilising a different project management methodology, such as PRINCE2, RAD, Waterfall, or
Agile. This will provide an understanding of the methodologies, the phases, and the
advantages and disadvantages of each methodology.
Project Management Methodologies:
Waterfall
The waterfall model is a prominent software engineering and product development
approach that takes a linear, sequential approach to the software development life cycle
(SDLC). The waterfall approach emphasises a logical step-by-step process. Each phase starts
only when the old phase finishes. The Waterfall approach is the most common method for
project management, with group members operating in a linear fashion toward a common
overall aim.
The waterfall model has the advantage of clearly and properly stating the requirements, as
well as providing easy control and transparency for the client due to a strict reporting
system. One of the disadvantages of this waterfall model is that after a task is completed, it
is difficult to go back and make modifications to it. When the project has already been
integrated, it is tough to go back and locate the source of the problem.
The principles of waterfall model are:
1. Analysis - This is when the requirements are investigated in greater depth, and they
are documented in a work document. This is the most critical stage of the project,
and it is likely that success or failure will be determined here.
2|Page
, Unit 9 – IT Project Management (Part A)
2. Design - This phase helps identify system requirements and plan the system's
architecture, as well as develop the design for the project. Instead of coding,
guidelines for how the task should be accomplished are established.
3. Implementation - This is where the product is made. It is necessary to develop the
system in units and to code it in order for it to function. There should be no need to
pause to reflect.
4. Testing - After the system's coding is finished, it is tested to look for any faults that
may occur so that they may address them before delivering the system. This is to
emphasise iterative processes, which reflect, and change work based on a brief burst
of activity followed by testing.
5. Maintenance - This phase focuses on developing fixes and upgrades to address any
code issues. If any faults are discovered during testing, the development team will be
required to enhance the product within a certain time frame in order for it to be
more effective.
Rapid Application Development (RAD)
RAD is a sort of agile methodology that emphasises rapid prototype deliveries. The RAD
Model, also known as the Rapid Application Development Model, it is a software
development approach that is built on prototyping with no particular planning. In the RAD
model, less emphasis is placed on planning and more emphasis is placed on development
activities. It aims to create software in a short period of time.
Advantages of this models are, it is flexible an adaptable to changes, less people can be
productive in a short time, the overall project risks can be reduced. Disadvantages of this
model are it only can be used for big projects, not all kind of applications are compatible
with RAD and when technical risk is high it is not suitable.
The principles of the RAD methodology are:
1. Planning the Requirements - This stage is similar to a project scoping meeting.
Although the planning phase is shorter than in other project management
3|Page
Contents
Introduction:......................................................................................................................................2
Project Management Methodologies:...............................................................................................2
Waterfall............................................................................................................................................2
The principles of waterfall model are:...............................................................................................2
Rapid Application Development (RAD)..............................................................................................3
The principles of the RAD methodology are:.....................................................................................3
PRINCE2.............................................................................................................................................4
The principles of the PRINCE2 methodology are:..............................................................................4
Agile...................................................................................................................................................5
The principles of the Agile methodology are:....................................................................................6
The Ford Edsel (Failed Project) – Agile...............................................................................................6
The car industry in 1950s...................................................................................................................7
Why did Ford Edsel fail?....................................................................................................................7
How would the Ford Edsel have been successful?.............................................................................7
PlayStation 2 (Successful Project) – PRINCE2.....................................................................................7
How did the PlayStation 2 use PRINCE2 and how did it help make the project a success?...............8
Why was the PlayStation 2 a success?...............................................................................................8
Sony Betamax (Failed Project) – Agile................................................................................................8
Videotape format industry in early 1970...........................................................................................9
Why did Sony Betamax fail?..............................................................................................................9
How would the Sony Betamax have been successful?.......................................................................9
Conclusion:......................................................................................................................................10
Evaluation:.......................................................................................................................................10
Bibliography:....................................................................................................................................10
Learning Aim A: Investigate the principles and methodologies of IT
project management as used in industry
1|Page
, Unit 9 – IT Project Management (Part A)
Introduction:
In this assignment, I will be investigating different IT project management methodologies
that the company can use. I'll assess three different projects, each of which was completed
utilising a different project management methodology, such as PRINCE2, RAD, Waterfall, or
Agile. This will provide an understanding of the methodologies, the phases, and the
advantages and disadvantages of each methodology.
Project Management Methodologies:
Waterfall
The waterfall model is a prominent software engineering and product development
approach that takes a linear, sequential approach to the software development life cycle
(SDLC). The waterfall approach emphasises a logical step-by-step process. Each phase starts
only when the old phase finishes. The Waterfall approach is the most common method for
project management, with group members operating in a linear fashion toward a common
overall aim.
The waterfall model has the advantage of clearly and properly stating the requirements, as
well as providing easy control and transparency for the client due to a strict reporting
system. One of the disadvantages of this waterfall model is that after a task is completed, it
is difficult to go back and make modifications to it. When the project has already been
integrated, it is tough to go back and locate the source of the problem.
The principles of waterfall model are:
1. Analysis - This is when the requirements are investigated in greater depth, and they
are documented in a work document. This is the most critical stage of the project,
and it is likely that success or failure will be determined here.
2|Page
, Unit 9 – IT Project Management (Part A)
2. Design - This phase helps identify system requirements and plan the system's
architecture, as well as develop the design for the project. Instead of coding,
guidelines for how the task should be accomplished are established.
3. Implementation - This is where the product is made. It is necessary to develop the
system in units and to code it in order for it to function. There should be no need to
pause to reflect.
4. Testing - After the system's coding is finished, it is tested to look for any faults that
may occur so that they may address them before delivering the system. This is to
emphasise iterative processes, which reflect, and change work based on a brief burst
of activity followed by testing.
5. Maintenance - This phase focuses on developing fixes and upgrades to address any
code issues. If any faults are discovered during testing, the development team will be
required to enhance the product within a certain time frame in order for it to be
more effective.
Rapid Application Development (RAD)
RAD is a sort of agile methodology that emphasises rapid prototype deliveries. The RAD
Model, also known as the Rapid Application Development Model, it is a software
development approach that is built on prototyping with no particular planning. In the RAD
model, less emphasis is placed on planning and more emphasis is placed on development
activities. It aims to create software in a short period of time.
Advantages of this models are, it is flexible an adaptable to changes, less people can be
productive in a short time, the overall project risks can be reduced. Disadvantages of this
model are it only can be used for big projects, not all kind of applications are compatible
with RAD and when technical risk is high it is not suitable.
The principles of the RAD methodology are:
1. Planning the Requirements - This stage is similar to a project scoping meeting.
Although the planning phase is shorter than in other project management
3|Page
