Technical a technical guide that aims to

Technical guide to Project




We Will Write a Custom Essay about Technical a technical guide that aims to
For You For Only $13.90/page!

order now

Table of Contents
Introduction. 2
Project methodologies. 3
Prince2. 3
Waterfall 3
Spiral methodology. 3
Critical path method. 3
Agile development 3
Individual methodologies. 3
Reference page. 4
Bibliography page. 5




is a technical guide that aims to help with readers who wish to study project
management and as such this will act as a tutor guide, within this guide it
will do the following; Describe and compare the features and benefits of the
following methodologies:



Spiral methodology

Critical path method

Agile development

the guide will explain the different life cycles and then evaluate their
importance of each phase of the following projects:

Initiation phase

Planning phase

Execution phase

Evaluation phase

will be project issues where the guide will proceed to describe them and
explain what happens within them, the following project issues are:


External factors


Lack of management/leadership

Poor planning


the guide will proceed to describe and explain the documentation, going through
the main documentation and the main control registers and plans, which are the
following: Main documentation

Project brief/project mandate

Project initiation document


Business case

Client acceptance form

Work breakdown structure

Project progress report

Project closure report

Lessons learned report

control registers and plans

Project planner

Risk register

Issues register

Lessons learned register

Project methodologiesJB1 

During a project’s development there are certain
methodologies that are used based on how the project is delivered, as such
certain methodologies are chosen to ensure the project runs smoothly, some
projects are better at using specific methodologies.


Prince2 is a project methodology that is widely known and
follows a strict development process, usually with a step by step instructions
this means that it does not require too much leadership as they’d already know
what to do, whiles it is strict, this methodology is not limited to just IT
industry for example it could be a project that aims to design a football
stadium, they would need to follow a strict set of instructions to ensure that it
is done as intended. This methodology has seven stages which will either be
followed or be monitored since if it’s a large project it can be very complex,
meaning issues are more likely to be encountered. The benefit of Prince2 is
that due to it being strict


Waterfall is a project methodology that does not change its
plan, unless it is necessary to do so and like the name implies it is a linear
structure, it was also originally used in projects relating to the development
of software, unlike agile development this does not repeat any of its steps,
assuming there wasn’t any change as stated earlier with it not doing so unless
necessary. This methodology has a lot of versions which with different amount
of stages, however they will all work like each other no matter the choice.

Spiral methodology

Spiral is a project methodology that was originally used as
a prototyping methodology, but has been adapted to produce a project management
system which allows for management to emphasises the importance of a risk
analysis. It should also be noted that this methodology is recommended to use
for projects that have a high risk and want to evaluate them, or even if the
user is unaware of the needs or want to quickly finish the project due to

Critical path method

Critical path method also known as CPM is a project
methodology that is also a step by step technique used to identify activities
on a critical path, this is a project that allows project scheduling as it
allows the ability to break the project into work tasks and can be displayed
often with flow charts this allows for the ability to calculate the project’s
duration based on estimated durations of each task and allows to identify tasks
that are critical, time-wise in completing the project.

Agile development

Agile development is a project methodology that is free and
doesn’t restrain the project, this is because it believes that large projects
cannot be planned since the client is most likely going to change their
objectives during development or unpredictable circumstances, it is also known
that agile development has been used in game development since the client could
change on how they want it and also since some game development engines can be


Project Life CycleJB2 



The Initiation phase is where the project would start,
usually this is where the project leader and the client or stakeholder would
consider the reasons for the project, who is the project for like is it for the
stakeholder, client or a target audience, and then what the goal of the project
is and who will carry out the project for example workers, next is who will be
involved, for example stakeholders, clients, and finally is does it have the
required support, this can include but not limited to IT Support, potential
users, managers, etc.


The planning phase identifies the project initiation phase
and would turn it into a more detailed project plan that will be used for
reference by the project manager and stakeholders throughout the project. In
addition it will also allow for the ability to monitor the project and control
the time, costs and the quality.


Execution phase is a more complicated stage of the project.
Firstly any deliverables are produced so that the project manager and team can
use the project’s plan to allow them to follow through the steps and be able to
monitor and control its pace as it develops, any milestones and projected
timings are monitored on tools such as but not limited to Gantt charts and even
the critical path method, assuming critical path method was chosen the tasks
are shown on the chart with time it must be completed, how long it will take
and which activities rely on each other.


The evaluation phase is the final phase that looks into the
overall quality of the deliverables, all of the successes of the project and
the team’s performance, along with the applications of tools and techniques
used during the project’s life cycle and ricks and issues and how they were
dealt with throughout the cycle and finally any lessons learned which would
improve future projects such as how they may of dealt to with a problem, and
how it was caused to help reduce the chance of it happening.