Project Management Plan Critique Essay Example

of each task are clearly mentioned in the PM.

The main of this project is to critically analyze the roles and phases used in this management plan. . Name The name of the project is Video Delivery. The name is not very clear of whether it is online video delivery or tradition video delivery. Old members may get it but for the new one it is unclear and confusing if they don't have the project details or description. Description The description mentioned in the PM is very detailed and it gives a very good outlook of what the project will look like when completed and how much it will cost and the time frame. . Project manager and Team Members The name, email address, cost and position of all the team members and project manager is clearly mentioned. However, it forgets to mention the phone number, qualification, actual address, and back-up contact person. Stake Holders All the stake holders with their details and complete responsibilities is acknowledged with their respective managing relationships. Their area of interest and level of interest in also well coated. 11. Deliverables There are no immediate and test deliverables.

A final product will be released at the end of the project cycle but it will be tested and adjusted when required during each phase. Definitions Definitions are clearly mentioned and creates no confusion. So it is correct. Introduction Project management critique requires a detailed and careful insight of the project. It requires a high level overview of the project and what is included in the project Management Plan, and most importantly the approach is adequate for project completion. Excessive details is

not necessary but a critical comprehension is a must.

Organization In project, team chart, responsibilities and work frame is clearly mentioned but the organizational chart is yet to be announced. Both roles and names are clearly visible and there are no confusions. However, the line of authority is not clear and could rate problems afterwards. Lack of organizational chart may create misunderstanding. Each team members are assigned with risks they may be responsible with the required solution. So, it would be easier to tackle if the risk arises. Also, the indication of probability and impact can make team member alert prior to the situation.

Management and Technical Approach 5. Management objectives Management and technical approach requires a well-defined and realistic groundwork of scope, cost analysis, cost management, time management, quality assurance and management, human resource management, communication management, risk management, and procurement management. 5. Project Controls Even though this project plan outlines the team members and their corresponding tasks, there is no communication planning. Each individual is supposed to inform the team member but it fails to explain if there is any back up person in case the team leader is sick.

Nevertheless, all the risks are not covered. There is no clear meeting agenda for control and monitor. Was the team leader and sponsors to meet on a weekly schedule and ascertain the completion of milestones, it would be easy to meet the scope. The weekly status reports are generated in a weekly basis which outlines the completed tasks, accomplished milestones, project quality, problems, and current status of the project. Confusions are also cleared in weekly meetings. This techniques is very helpful in monitoring

and controlling the quality of the project which helps team members to deliver a high quality project on time.

The project is not well planned in budgeting. It is already exceeding the assumed amount by $120,000. There is no back up amount for risk or scope creep. The revised budget and increase of additional fund already shows the insensitive planning of the management. The nature of complexity of this project requires more time then allocated as certain tasks can get complicated and extensive. Scope creep is when project starts off as one thing but slowly grows into something bigger/unplanned. This usually happens because of unplanned project budget, uncontrolled changes, and deadlines. To get more revenue, scope has to be well managed.

Scope creep can be a good thing when the deliveries is better than expected but uses the same amount of resources. Unlikely, in this case, the budget was revised and an additional amount was increased which is undesirable and indicates bad management. This part is not well written and planned. 5. Risk Management In this project for risk management, risk register and risk probability/impact matrix are used.

These techniques are useful for handling risks and managing problems. In risk probability/impact matrix various fields are used are:

1. No.
2. Rank
3. Risk
4. Description
5. Category
6. Root Cause g. Triggers
7. Risk Response
8. Risk Owner
9. Probability
10. Impact

Status These fields are used for mentioning various things in the process of risk management. In the risk field, the name of the risk is mentioned. The description is written in the respective field. There are different categories of risks and organizing them makes it easier to resolve. The root cause helps to

identify the main reason behind the problem so it can be avoided before any accident happens. In the risk trigger field, all the anticipated consequences are recorded. For example, a low quality product can create dissatisfaction among clients.

In this way all the fields represent some special information and this information is very helpful for managing risks. It is very necessary to discover risks related to the product for a successful completion. In risk management various techniques are used to manage risks. For example risk registers are one of a popular technique to handle risks. In the process of risk management risk registers are also used for mentioning all the risks in that register. So this part of the report is well written. Project Staffing The types of people, numbers, and their specific Job is well recovered.

However, the absence of organizational chart can create confusion. All the reporting and communication is done on the basis of the organizational chart. Although there is team leader to handle the communication flow, an organizational chart would have en helpful. Technical processes This part of the report is not well written. The documentation standards are good. No information about system development life cycle approach is mentioned. The technique which is used is correct. Work to Perform. Major work packages This phase of the report includes the scope and work breakdown structure.

Project scope document is very important to finalize the Project Plan and word Breakdown Structure. The requirements and acceptance criteria is acknowledged in this project but more key issues like Project Boundaries, Assumptions, Initial project organization, Project configuration management requirements, detailed Project and product objectives, and Approval

requirements are overlooked. It is not a well- planned scope.

In work breakdown Structure various fields mentioned are:

1. Task name
2. Duration
3. Start
4. Finish
5. Predecessors By using of these fields work breakdown structure works.

The WEBS is an 8-level hierarchical grouping of activities that provides for a progressively detailed definition of work elements for all levels of review, including staff, functional manager, project manager or program manager. Work Breakdown Structure (WEBS) should be created n Microsoft Project. WEBS contains work packages which are developed through close collaboration among stake holders and team members and also includes past research and input from functional managers. Proper time charging gives managers a tool to track the actual cost of projects, review the project status, and allocate resources.

In the PM report, WEBS is mentioned in a well-mannered way. Key Deliveries This part includes the immediate and final product of the project. The project does not have an immediate or in-the-process product which could be studied for risks laity, and scope scoop. The project is solely intended for one final product but overlooks major client's assumptions. Other This part of the project is well written. Assumptions, Hardware/Software requirements are clearly mentioned in this part of report on the project management plan. Schedule

Summary Schedule is a significant part of project management. The project is not successful if it is not completed on time. A lot of factors and reasons are there because of which project teams have fallen behind schedule (SAME, 2011). A project must follow the proposed schedule. If a project falls behind, it is team leader's responsibility to put the team back on schedule. There are various

techniques that can be used by management like overtime. Not everyone likes to work overtime thus making it team leader's responsibility to confront it before scheduling individual tasks to team members.

However, there is no mention of overtime in this project. Reallocate resources are another technique to tackle behind schedule problem. In this technique resource are reallocated in such a way that it can be fully utilized and more results are produced to track back on schedule. During reallocating of sources it is very necessary to allocate more resources to modules which required more resources. Crashing is also a useful way in which extra resource is allocated to critical paths. It can be sometime used to get the biggest schedule gain.

Sometimes, multiple activities are performed in the same time to cover the schedule and actual time. This is called Fast Tracking. Milestones and Giant charts are used in this project for scheduling. This part is well- written. Detailed In detailed part, schedule is discussed in a detailed manner. Giant chart and network diagram are used for this purpose. The Giant chart is a type of bar chart which illustrate the project schedule (REF Electronics, 2011). The purpose of a Giant chart is to display a project schedule in a visual way that is easily understood.

A Giant chart looks at the activities on the left hand side, and then draws a horizontal bar that indicates the start, end and duration of each activity that is listed. In addition to providing scheduling information, a Giant chart can be used very well in the implementation of projects. You can use a Giant chart to draw every

week the ACTUAL duration of activities, and to ask project team members to report back on heir activities that they were responsible for. You can also use a Giant chart to determine the cash flow of a project, and you can assign responsibilities in a Giant chart.

So in this part of report scheduled is well described by using of Giant chart and network diagrams. Other In this part of report assumptions related to schedule are clearly mentioned and these assumptions are well described. 18. Budget Summary A revised version of budget is mentioned in the project plan which shows the increment of $120,000. The total budget is broken down into three areas: Hardware, Labor, and consulting and outsourcing. Budget for each areas is well detailed and defined. The management is budget is very essential for project's success and this is not easy task.

However, there are no funds allocated for emergency or scope scoop. Detailed Each areas have its own budget which is well formulated and organized. The tables clearly shows every details from individual salary packages, hardware costs, to third party payment for outsourcing. Other Assumptions are described related to budget in this section of report in well manner. By reviewing project Management Plan of Video Game 20, it is understood that lancing and budgeting is very crucial for project achievement. The project is unusable if it does not yield result.