ITECH 5213 PMP CRITIQUE

SUBMITTED BY: Bejal S

Brahmbhatt
STUDENT ID: 30098204

Title Page:
In the title page they have given the project name, date, organisation name and
project manager name and contact details and number with team members details.
Critique: In this project management plan they gave all the details but the cover
page is too simple; it could have done in better way. They have just put all the
information but not followed the particular format or design and left the organisations
contact details along with organisations address and postcode.

Executive Summary:
This project management plan include the summary with the project plan for the
Video Delivery system that includes the projects objectives, relevant stakeholders
and their contact information, the projects scope statement, the work break down
structure of the project, potential risks that the project may encounter and the budget
that
the
project
is
going
to
follow.

Table of Contents:
In the table of contents they include summary, project objectives,approaches,roles
and responsibility, scope statement, organisational chart,mildstone report,WBS,Gantt
chart along with risk management and budget factors.
Critique: In this PMP plan they missed the main part of the project that the
Introduction because that is really necessary of any PMP plan. Besides that they
forgot to add the main task of the plan that is Quality management plan which is
base of any successful project. In that PMP plan they did not include the staff
management plan.

Introduction:
The Introduction provides a high level overview of the project and what is included in
this Project Management Plan. This should include a high level description of the
project and describe the projects deliverables and benefits. Excessive detail is not
necessary in this section as the other sections of the project plan will include this
information. This section should provide a summarized framework of the project and
its purpose.
Critique: they did not gave the introduction for the PMP so they missed the main
important part of that and this gives a worst impression to others.

Organisation:
This project has given detail information about its goals and objective. The objective
is to develop and produce a web based services that allow customers to rent video
games. These all information is given in very simple and understandable form. And
also it has also given its budget estimation.
Critique: For achieving the success, every organisation will have certain aims and
objective. Without having any goal it will be worthless to start any project. In this
project also they have written about the project objectives but he did not mention the
specific and measurable objectives clearly in the objectives

Project Management Approach:

The approach was almost clear. They have decided that team 2 will work on
information collection and documentation and then send for reviewing by sponsor.
Then after appropriate documentation will be finalised, budget will be finalized before
letting money go out for any purpose.
Brief design, when the software will be implemented, testing done by the users
before deployment, testing is done to verify the exactness of the project.
Having regular meetings with the sponsors of the project to inform about the
progress and level of the project, to verify if the project is going according to the plan
in the right way so that it meets the standards and requirements of the sponsors.

Critique: The author have been given a clear description of the requirements of the
project, the documentation part, Cost, the payments major design, testing of the
project but they have no measurement of standard that their sponsor are following
and without having that idea this approach may be failed.

Roles and Responsibilities:

The author have given the list of team worker who are involved in this project, he
also have mentioned their role or can be said as position be are supposed to be and
their contact detail in table in very clear format.

Critique: In this, he was supposed to give the detail of role and responsibilities of
team but he has just mentioned the role but there is no any discussion about the
responsibilities that the each role has to perform which made unclear about the
responsibilities that they actually have to move forward with.

Stake Holders:
The information about the stake holders, the scope statement and the organizational
chart is given. The author has given details about the individual stake holder's
organization, the roles and responsibilities of each person associated to the project,
the interest levels of them, the impact and influence one have over the other, the way
they maintain relations with one another. All these are mentioned well in the project.

Critique: In this information no specific milestones are present .Neither the key
events nor the end date of the project is given. The prioritization of the conditions is
not given.

Scope statement:
The scope statement details the project deliverables and describes the major
objectives. The author has also mentioned the major objective of the project in this
section, characteristics and requirements and figure of expected budget.
The scope statement from the project charter should be used as a starting point;
however, the project plan needs to include a much more detailed scope than the
charter. This detail should include what the project does and does not include. The
more detail included in this section, the better the product. This will help to clarify
what is included in the project and help to avoid any confusion from project team
members and stakeholders.
The author has given a clear view of the aim, goals and the objectives of the project.
The aim is to develop a web based service which lets the customers in renting video
games by making use of the internet and on monthly basis.
The cost of the video games can be seen by the customers. The prices are
reasonable and are kept changing. They are different for each type of game. A
customer can order any number of video games in a single go. Most of the video
games are related to fields such as sports, education.
These video games must be platform independent, Searching option must be
successful, the interface must provide options for user to input data., Various
languages must be accepted.
Critique: The first thing is the format of scope statement is not correct; it should
follow a certain format. Second thing is it has described about the characteristics and
requirement which is unnecessary and budget information is also not so clear. Scope
statement format should be in the following format.
Example:
Scope statement
Title:
Department:
Project Manager:
Date:
Budget:

Prepared by whom:

Owner

Role and Responsibility

Project closure report version control

Version

Author

Required changes

Organisational chart:
The organisational chart that they have given is correct format, they have mentioned
the entire role in very well position and made easy to understand that who is going to
work under whom.

Critiques: The main part is they had not mentioned about the vice president that he
was the project sponsor. Another thing is the author has not given his attention
toward the font of the text that is written in chart.

Milestone Report:
In this report provide a summary list of milestones including dates for each
milestone. Include an introductory paragraph in this section which provides some
insight to the major milestones. This section should also mention or discuss actions
taken if any changes to the milestones or delivery dates are required.
In this have given the name of person who have prepared and schedule of
completion date, status, and the name of person who have certain role in project.
There is everythings that the complete milestone needs to be.

Critique: first of all milestone is often put at the end of a stage to mark the
completion of work but it has been done before the work has been done, after that
the work which is not done or started work dates has also been mentioned. This is
totally carelessness and come to know that they dont have knowledge about where
the milestone report should be.

Work Breakdown Structure:

This section should discuss the WBS, WBS Dictionary, and Schedule baseline and
how they will be used in managing the projects scope. The WBS provides the work
packages to be performed for the completion of the project.
The WBS Dictionary defines the work packages. The schedule baseline provides a
reference point for managing project progress as it pertains to schedule and timeline.
The schedule baseline and work breakdown structure (WBS) should be created in
Microsoft Project. The WBS can be exported from the MS Project file.
In this PMP Work Breakdown structure has been done very well. Every work has
been separated for certain time, there are 5 stages and for each stage time is divides
such as 40 days for initiating, 60 days for Hold Team Planning meeting and soon.

Network diagram:
They have presented this in very clean format. Divided different branch for different
section.

Risk Management:
This section provides a general description for the approach taken to identify and
manage the risks associated with the project. It should be a short paragraph or two
summarizing the approach to risk management on this project.
Since risk management is a science in itself, we have many risk management
templates available on our website. Look for the detailed Risk Management Plan,
Risk Register along with templates for performing a risk assessment meeting.
It has been categorized in three sections that are high, medium and low. Estimated
budget is in high risk, disagreement is medium in risk, in this way the author have
given with many other detail such as category, cause, risk response etc.

Budget Summary:
In the Budget Summary they have to defines how the costs on a project will be
managed throughout the projects lifecycle. It sets the format and standards by
which the project costs are measured, reported, and controlled.
Working within the cost management guidelines is imperative for all project team
members to ensure successful completion of the project. These guidelines may
include which level of the WBS cost accounts will be created in and the
establishment of acceptable variances. The Cost Management Plan:

Identifies who is responsible for managing costs

Identifies who has the authority to approve changes to the project or its
budget
How cost performance is quantitatively measured and reported upon
Report formats, frequency and to whom they are presented

The budget for the Video Game Delivery Project has been broken down into the
three following areas: Hardware, Labour and consulting and outsourcing. This is a
revised budget with an extra $100,000 dollars allocated to the budget.
Total hardware cost: $6,475.45 Total labour cost: $249,972.45 total consulting and
outsourcing cost: $ 363,552.10
Total cost for project: $620,000.00
This has also been given in tabular format which is very easy to understand.

Revised Resource work Report:

This is the bar chart where we can see that which worker worked how many hour,
whether they meet the availability or not, every worker name is given and hours
available to work and worked hour are also given. The bar chart is very crystal clear.
Also below the bar chart there is given which worker worked how many hour exact
hour.

Change Management Plan:

This section should describe your change control process. Ideally, this process will
be some type of organizational standard which is repeatable and done on most or all
projects when a change is necessary.
Changes to any project must be carefully considered and the impact of the change
must be clear in order to make any type of approval decisions. Many organizations
have change control boards (CCBs) which review proposed changes and either
approve or deny them.
This is an effective way to provide oversight and ensure adequate feedback and
review of the change is obtained. This section should also identify who has approval
authority for changes to the project, who submits the changes, how they are tracked
and monitored.
For complex or large projects the Change Management Plan may be included as an
appendix to the Project Management Plan or as a separate, stand-alone document.
We have a detailed Change Management Plan template available on our website.
In this PMP they have given the format of change request is perfect. There is project
name, submitted by, severity, date etc. the entire requirement needed in form are
available.

Quality Management plan:

This section discusses how quality management will be used to ensure that the
deliverables for the project meet a formally established standard of acceptance. All
project deliverables should be defined in order to provide a foundation and
understanding of the tasks at hand and what work must be planned.
Quality management is the process by which the organization not only completes
the work, but completes the work to an acceptable standard. Without a thorough
Quality Management Plan, work may be completed in a substandard or
unacceptable manner. This section should include quality roles and responsibilities,
quality control, quality assurance, and quality monitoring.
For larger or more complex projects, the Quality Management Plan may be included
as an appendix or separate document.

Critique: they have forgot to add quality management in that PMP so they do not get
the same or high quality as per the requirement of the project and this will be the one
of the major problem during the project development.

Conclusion:
In this project there are many things that need to be corrected. So many of the thing
has been done with carelessness. If I will get chance to make the report than firs of
all I will not repeat those mistakes again. Then I will first study the market, try to
understand the customer need and then develop the goal which will be achievable,
measurable, realistic, and manageable. As per my PMP Critique it shows that how
effectively managed PMP by project developer in any organisation.

References:

Alfred D. Chandler, Jr. (1962). Strategy and Structure: Chapters in the History of the
American Industrial Enterprise. Cambridge, MA: MIT Press
Flyvbjerg, B., Bruzelius, N., &Rothengatter, W. (2003). Megaprojects andrisk: An
anatomy of ambition. Cambridge,A: Cambridge University Press.
Johnson, Brunn, & Platt, 2002 OR Johnson, Brunn and Platt (2002) Subsequent
citations: (Johnson et al., 2002)
Kahneman, D., & Lovallo, D.(1993). Timid choices and bold forecasts: A cognitive
perspective on risk taking. Management Science, 39, 1731
Lovallo, D., & Kahneman, D.(2003, July). Delusions of success:How optimism
undermines executivesdecisions. Harvard Business Review,5663.
Ringsven, M. K., & Bond, D. (1996). Gerontology and leadership skills for nurses.
(2nd ed.). Albany (NY): Delmar.