I need it quickly

18
=
IT PROJECT MANAGEMENT TECHNIQUES
Executive Summary
This report evaluation has been defined in a broad way and does recommendations on the part where it is of need. In most of the parts, it has been found that the project has been done accordingly but information with diagrams are not provided in an according manner. This as a result does not make the project a fruitful one to evaluate accordingly. In the part of appendices, it has been found that gantt chart and network diagram is not provided which makes the project not appropriate to evaluate in the best possible way. Budget, which has been provided along with the WBS, is analysed accordingly and with the requirements.

Table of Contents
1. Introduction    4
2. Critical analysis of PMP    4
2.1. Introduction    4
2.2. Organisation    5
2.3 Management and technical approach    6
2.4. Work to perform    9
2.5. Schedule    10
2.6. Budget    11
Conclusions    11
References    13
1. Introduction
        In order to lead to a successful project, it is important to follow proper project management techniques and methodologies. This particular report will majorly focus on critical analysis of the PMP (Project Management Plan) regarding the project of “Sovereign Hill App Development Project 20xx”. A critical analysis will be highlighted in detail including their risk management plan, budget plan and many other aspects. The organisational structure along with the project schedule will also be shed light on.
2. Critical analysis of PMP
2.1. Introduction
The particular project management plan is all about producing a particular mobile application for both Android devices and iPhone. This particular application has the ability to enhance the experience of the visitors by permitting them for planning the visits in advance. It will also provide all kinds of information related to walking hours, directions and many other factors. Now, by considering the name of the project, it can be said that it is quite meaningful and relatable to the respective project. The name has been reflecting the actual nature of the project. As stated by Eskerod & Jepsen (2016), by considering the project description, it can be conferred that it has not provided a complete detailing regarding the actual reason behind the initiation of such a project. It is written in a simple language as well.
It has been noticed in this context that the time and cost has not been predicted in the description section of the project management plan. However, evaluation the details of the sponsors, it can be said that the sponsor details are quite significant in the respective project management plan because each and every single detail regarding the name and title of the sponsor along with their contact information are significantly provided in the description section of the PMP. In the portion of the “Team member register”, detail description of each of the team member of the respective project has been mentioned along with their contact number as well as email id. As commented by Larson & Gray (2017), detailed information about the project manager can also be obtained with the help of this particular section.
In case, the deliverables section has been taken into consideration, then it can be seen that the respective authors have provided key deliverables related to the respective project of creating an application. Such deliverables include the scope statement, schedule, budget report along with a report of the final project. According to Chen, Kang & Lee (2017), the authors have systematically provided a particular list along with the respective description of each of the product which has been created in the project management plan. These are not separated into the product and the associated categories of the project management. By evaluating the reference list, it can be observed that the reference plan has covered different knowledge areas related to the topic such as the plan of quality management, procurement management and many others. The definition section is missing in this plan. However, the definition of product requirements and characteristics has been provided in this plan as well.
2.2. Organisation
     Figure 1: Roles and Responsibilities of Associated person in Project
Under the segment of the organisation, it has been observed that a transparent organisational chart has been provided in which the name and the respective description has been provided clearly. In this particular part, an organisational chart of the Thrones technology along with Sovereign Hill has been provided with the help of the structure of an organisational chart. The responsibility of each of the team member is reflected in the Matrix of Responsibility Assignment. As opined by Costantino, Di Gravio & Nonino (2015), functions of the project are listed in the report of the milestone. However, after a detail evaluation of this particular segment, it can be observed that the names and roles are visible transparently. The lines of the authority are still not that much clear. This section could have been improved a bit.
Figure 2: Organisational Chart
By taking into consideration the section of project responsibilities, it can be seen that the RAM or Responsibility Assignment Matrix provided in the form of a Work Breakdown Structure. Some particular has been used in this particular matrix in order to simplify the overall matrix. It has been noticed in this particular matrix the "R" denotes Responsible, "A" denotes Assists, "C" denotes Consulted and lastly, "I" denotes Informed. Different colours have been used in this WBS matrix in order to make the whole matrix much attractive. RAM has included all kinds of tasks as well as activities it has been accompanied by a particular explanatory key. This indicates the responsible person and respective duties and responsibilities of that person.
2.3 Management and technical approach
    In this...