Project management- Assignment 1
Project methodologies
Introduction
I have been recruited by a leading insurance company as a project manager and will be
responsible for setting guidance and governance for running IT projects. In this report I will
be investigating different project methodologies that the company could use when making a
project.
First, I will be giving a brief description of what project methodologies are and give a
description of what each project methodology is followed by a table underneath it which
will contain a description of all the phases that are included in the methodology, what they
are, who is involved in each phase and what gets delivered or produced by the end of the
stage.
After that I will be comparing the advantages and disadvantages between Waterfall and
Agile
After that I will be comparing the benefits and limitations between Waterfall and Agile. I will
do this by first making a table containing the benefits and limitations for each then
comparing them below the table followed by a conclusion.
Lastly, I will talk about project structures what they are and why they are important to
project methodologies. Also, I will be talking about what would happen if project structured
were not used and if the end goal of the project would change or not.
, What are project methodologies?
Project methodologies shows a roadmap of the project and lists all the steps and
requirements that are needed for the project then these project methodologies and
techniques are used to provide a detailed structure and a guideline for the project. There
are 3 types of project methodologies which are Waterfall, Agile and Prince2.
Waterfall methodology
Waterfall methodology is a breakdown of the project tasks into sequential phases where
each phase depends on the completion of the task before it and cannot be changed once
the task has been done and flows in one direction hence called the Waterfall methodology.
Phase What it is Who is involved What gets
produced/delivered
Requirements The requirements are Project manager, In the requirements
what the project is sponsors, and phase the project
about and what it stakeholders. manager will get a
requires to complete detailed
it. understanding of the
sponsors project
Functional and non- requirements and
functional make sure that they
requirements are are completed.
required in this phase
as well.
Analysis The analysis phase is Project manager, the A detailed analysis of
where the team that team, the any issues of the
are handling the stakeholders, and project so far and how
project analyse the sponsors. to fix them.
requirements and fully
understand the
problems in the
project.
This phase will have
job roles and
responsibilities that
will be needed such as
system architect.
Design In the design phase of Project manager, the In this phase the
the Waterfall team, the resource architecture required
methodology helps to managers, the for the project will be
specify what the sponsors, and specified and other
product will look like, stakeholders. things that will be
the hardware needed in the project.
requirements and the
overall system
architecture of the
product.
Project methodologies
Introduction
I have been recruited by a leading insurance company as a project manager and will be
responsible for setting guidance and governance for running IT projects. In this report I will
be investigating different project methodologies that the company could use when making a
project.
First, I will be giving a brief description of what project methodologies are and give a
description of what each project methodology is followed by a table underneath it which
will contain a description of all the phases that are included in the methodology, what they
are, who is involved in each phase and what gets delivered or produced by the end of the
stage.
After that I will be comparing the advantages and disadvantages between Waterfall and
Agile
After that I will be comparing the benefits and limitations between Waterfall and Agile. I will
do this by first making a table containing the benefits and limitations for each then
comparing them below the table followed by a conclusion.
Lastly, I will talk about project structures what they are and why they are important to
project methodologies. Also, I will be talking about what would happen if project structured
were not used and if the end goal of the project would change or not.
, What are project methodologies?
Project methodologies shows a roadmap of the project and lists all the steps and
requirements that are needed for the project then these project methodologies and
techniques are used to provide a detailed structure and a guideline for the project. There
are 3 types of project methodologies which are Waterfall, Agile and Prince2.
Waterfall methodology
Waterfall methodology is a breakdown of the project tasks into sequential phases where
each phase depends on the completion of the task before it and cannot be changed once
the task has been done and flows in one direction hence called the Waterfall methodology.
Phase What it is Who is involved What gets
produced/delivered
Requirements The requirements are Project manager, In the requirements
what the project is sponsors, and phase the project
about and what it stakeholders. manager will get a
requires to complete detailed
it. understanding of the
sponsors project
Functional and non- requirements and
functional make sure that they
requirements are are completed.
required in this phase
as well.
Analysis The analysis phase is Project manager, the A detailed analysis of
where the team that team, the any issues of the
are handling the stakeholders, and project so far and how
project analyse the sponsors. to fix them.
requirements and fully
understand the
problems in the
project.
This phase will have
job roles and
responsibilities that
will be needed such as
system architect.
Design In the design phase of Project manager, the In this phase the
the Waterfall team, the resource architecture required
methodology helps to managers, the for the project will be
specify what the sponsors, and specified and other
product will look like, stakeholders. things that will be
the hardware needed in the project.
requirements and the
overall system
architecture of the
product.
