100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Previously searched by you
Previously searched by you
logo
Essay Unit 9 - IT Project Management $13.97
Add to cart
Quickly navigate to
Preview
  2.  
  3. PEARSON (PEARSON)
  4.  
  5. Information Technology 2016/2017 NQF
  6.  
  7. Unit 9 - IT Project Management

Essay

Essay Unit 9 - IT Project Management

2 reviews
 7 purchases
  • Course
  • Unit 9 - IT Project Management
  • Institution
  • PEARSON (PEARSON)

Distinction level work was written in spec with Information Technology Course by Pearson This document covers: A.P1 - Explain, using appropriate definitions, the characteristics of different methodologies applied in IT projects. A.P2 - Explain the project management structures applied in differe...

[Show more]

Preview 3 out of 19  pages

Document information

  • February 28, 2022
  • 19
  • 2022/2023
  • Essay
  • Unknown
  • A+

Subjects

  • information technology
  • project management
  • ap1 explain
  • using appropriate definitions
  • the characteristics of different methodologies applied in it projects
  • pearson
  • ap2 explain the project manag

Written for

  • BTEC
  • PEARSON (PEARSON)
  • Information Technology 2016/2017 NQF
  • Unit 9 - IT Project Management
All documents for this subject (121)

2  reviews

review-writer-avatar

By: fh6400424 • 1 year ago

review-writer-avatar

By: charliepalmer • 3 year ago

Seller

avatar-seller
marcinsielewicz

Reviews received

Content preview

Level: Distinction



Unit 9 IT Project Management Assignment
Introduction
I am a trainee project manager at a software development company. Currently, the company is at
the stage of establishing different procedures before undertaking any project. My manager has
asked me to investigate three different project management methodologies, which the company can
use in their procedures. Those methodologies are Prince2, RAD, Waterfall or Agile. I will be taking
into consideration their design and structure, as well as a benefits and drawbacks all of those
methodologies offer. I will try and cover the different the different aspects of the structure, which
should allow the company to figure out the suitability of those methodologies.

A.P1 - Explain, using appropriate definitions, the
characteristics of different methodologies applied in IT
projects.
Project Management
Project Management is a way to establish the needs of the project and ensuring that all the
appropriate steps within a project are undertaken in a controlled manner, to optimise success
through the management of budget, staff and time effectively. To do that, there are several project
management methodologies which must be chosen regarding the project scope. Some of those
project management methodologies are Prince2, RAD and Waterfall. All those project management
methodologies contain different characteristics as well as features which make them individual in
approach as well as have a better suit for different types of projects. Those projects may vary in size,
outcome and the time required to get a result, as well as the overall deadline for the entire project.
Meaning that for a project to be successful, every factor must be managed appropriately, to a
satisfactory standard and all the problems must be resolved and any risks that may occur should be
prevented beforehand.

Most Project Management Methodologies are based on the same lifecycle which is:

● Initiating – outlines the justification and requirements, this stage is used to establish client
requirements that will fit the brief and justification for the project to run smoothly within
planned costs as well as the time frame projected. On this stage of the lifecycle the Project
Initiation Document is created.
● Planning – details of how the project will work will be carried out, monitored and controlled.
In this stage, the plan created in the previous stage is enhanced as well as this stage is used
for consideration.
● Executing: human, machine resources needed within constraints – time, cost, quality. This
stage is used for accomplishing the aim, set in the planning stage. This is where the teams
allocated do the specific tasks preferably within time frame provided and under supervision
from the Managers and Directors up to the cost and quality as set in the planning stage
● Monitoring and controlling – control of the project in line with the initiation and planning
documents. This stage is about managing the work completed ensuring that all the
paperwork is completed. This also means that the completed work was reviewed in this

,Level: Distinction


stage by supervisors and the work that is acceptable is approved, any issues are highlighted
are captured and sent back to the execution stage to be fixed.
● Closing – formally closed, review of the process to highlight success and mistakes. This stage,
the project officially comes to an end whether completed the aims that were set in the
planning phase, or not. All documents must be prepared so that a project can be closed in a
sensible manner, and the finished project is handed over to the client. A formal evaluation is
written determining and outlining all the accomplishments as well as strengths and
weaknesses of the project



Management Methodologies are:
Prince 2:
Prince2 is a unique methodology. It is generally only well known within the UK, being established as
one of the best project management methodologies. Prince2 is very well known, for providing great
amount of control within the project. This is because of its structured methodological approach
which enables project managers to divide a project into smaller, easier to manage for greater control
as well as improved communication within an entire team. The five stages of prince2, ensure that
the project is being managed well within the timescale provided as well as being monitored for
potential risks and deal with them accordingly. This method is also well known for preparation that
goes on before the project launches, this is because this method is about going into every stage
prepared so that it runs smoothly as possible. This methodology requires to keep a constant logs and
approvals due to its very strict controlled structure.

Rapid Application Development (RAD)
RAD is a methodology mainly used for designing computer software. This methodology does not
evolve around doing extensive research prior to starting the project. This methodology is very hands
on, methodology. This methodology relies heavily on potential user feedback and prototyping;
however, this methodology is very fast at bringing results, and any progress can be seen almost
immediately this allows for identification of problems very early on. This methodology is structured
based on assigning people to work on the projects solution, meanwhile doing all the improvements
as well as eliminating problems, with little documentation. This makes the methodology being able
to constantly handle change, as well as being focused on the architecture of the solution.

Waterfall
Waterfall methodology is an organised methodology, with everything happening in a systematic
order, one at a time, mainly used for making websites. This methodology is very simple to use as
there is only one thing happening at a specific time. This methodology is structured in a way that
ensures the completion of every stage before starting another one. This methodology, is about
dealing with issues as they come along, as well as this methodology relies on keeping constant track
of what stage is the project at, with sufficient documentation. The way this methodology is
structured, makes it difficult to have mouldable requirements, as when a certain stage is completed
it makes it impossible of going back a stage without re-doing all the work again.

A.P2 - Explain the project management structures
applied in different IT projects.

, Level: Distinction


PROJECT MANAGEMENT JOB ROLES AND RESPONSIBILITIES:
All the methodologies contain those job roles, however they just vary based on the methodology
that is being used:

● Project manager – responsible for creating any plans, in regards of the way that a project will
be carried out. This includes managing teams, individuals as well as stakeholders. In
addition, project managers are responsible for ensuring that the communication flows well
through the entire team, which results in a better management of schedules, dealing with
risks, including budgets to ensure a high standard of delivery of the final project.

● Systems architect – responsible for any designs and the implementation of any system
infrastructure of a project. In addition, systems architects are responsible for justifying their
decisions, in regards of how a specific piece of hardware meets the requirements of the final
system and how it affects its performance.

● Electronics engineer – responsible for providing or designing all electronical components
that are required for implementation and development stages. Those components include
circuits and interfaces.

● Product owner – responsible for establishing requirements, prioritizing work to ensure that
the start vision is matched at the end of the project. Product owner is also identified as the
key stakeholder within the project because without them the project would not even be
tried to be transferred into reality.

● Lead developer – responsible for overseeing the entire project, finding and fixing any risks.
Enhancing communication between teams and showcasing their knowledge and experience
to less experienced co-workers.

● Developer – responsible for writing code allowing for it to be implemented.

● QA Test lead – responsible for writing the test plans that will enable to establish whether the
project has been completed successfully and determine whether all the requirements have
been met. In addition, they are also responsible for managing testers and assigning tasks for
them to do, they also give assistance to junior testers due to their far greater expertise.

● QA tester – responsible for carrying out tests according to the test plan, that will test both
functional and non-functional requirements for the product

● IT Support technician – responsible for logging and fixing any technical difficulties within the
IT Services to maintain the systems operational enabling to meet the needs of both the
organization and the user.

● User – responsible for testing out the products success, as well as reporting with any
feedback to any of the key stakeholders to encourage improvements and increased
efficiency

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

Quick and easy check-out

You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.

Focus on what matters

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying these notes from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller marcinsielewicz. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for $13.97. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

65040 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy study notes for 15 years now

Start selling
$13.97  7x  sold
  • (2)
Add to cart
Added