The purpose of this assignment is to develop a well-analysed and well-researched project management report based on analysing and identifying the overall parameters of a project and establish the appropriate project management standards required to complete the project. A project case scenario is given that must be used to analyse and identify project issues, different project management tools and techniques to manage the project and conduct project risk assessment. Assumptions can be made where required. But the assumptions must be reasonable and documented. The assessment is based on the realistic nature of the project and how well it is presented. Make sure that the breakdown of the tasks, timeline, and the quality of the work is realistic, justifiable and sufficiently attractive to win a tender for a real project.
Task 1: Your first task is to prepare project charter that includes, background of the project, project objectives, main project success criteria, roles and responsibility of project stakeholders, and risk and dependencies.
Task 2: Design a Gantt Chart schedule that includes, work break-down structure (WBS), start and end date of each task, responsible person to perform the task and proceeding task/s. It is important to mention that WBS is required for all the stages (i.e., Integration and Request, Project Planning, Project
Execution, and Implementation and Support) mentioned in the case scenario. Moreover, you must include the relevant sub-stages necessary to complete the project. It is compulsory that students use Microsoft Project to complete WBS, allocate time and resources.
Task 3: Discuss a risk assessment plan. This must include identifying possible risks, performing qualitative and quantitative risk analysis and planning for risk responses. To identify risks, you must apply common risk identifying techniques (for example, brainstorming, Delphi technique, interview, SWOT analysis, fish bone diagram etc.). For detail understanding, you might conduct a brief research on common methods and techniques on project risk identification and risk analysis. For the simplicity, you need to apply risk assessment plan at only one stage of the project (i.e., Integration and Request, Project Planning, Project Execution, and Implementation and Support).
The IT organization for Mankind Hospital (MH) took the lead in championing the time keeping system (TKS) project that provides various types of services and solutions for both internal (doctors, nurses, students) and external (patients) customers. Some of those services and solutions include the registration system, employees’ clock in/out system, payment system for patients, and computing power for medical research. TKS is a formal project which has a project manager and a team of skilled and knowledgeable members. All the members are motivated and committed to the project. Project Scope It had been emphasized since the beginning of the project that the objective of TKS was to implement a new time keeping system for MH. The system’s replacement represented an operating necessity. It was a $1 million project and was anticipated to take 18 months to complete. The motivation for the project came from the fact that the vendor which provided services for the current time keeping system had sold its system to another company. As a result, MH was forced to make a change because the support for the current time keeping system would be discontinued by the new vendor. Management was faced with two options:
(1) purchase a new system from the new vendor, or (2) seek other vendors for time keeping systems. The first option appeared to offer fewer risks (familiarity with the previous generation of the system) and enabled MH to keep the front-end system for its employees (e.g., tax system, clock in, clock out). Furthermore, it is required to add a new transaction inquiry feature of the TKS system, which will make the system much more user friendly, a feature that currently is not in the project plan. However, the new feature imposes more technical difficulty than what the team had expected and will cause an increase in the project cost and schedule.
It primarily focuses on maintaining a stable, limited line of products or services; it offers best quality with low cost; and it delivers what its customers want. Influenced by the business strategy, project management elements are directed to satisfy customer needs through the delivery of quality products and services. The first priority of the TKS project is to install the system and make it work correctly with all other existing systems. The major constraints are cost and schedule, since the project has limited resources and a strict go – live date, previously announced to all employees. Objective: The objective of the TKS project is to implement a new time keeping system to the organization. The target customers are payroll specialists and the users of the new system. Product Details: The product is a time keeping system that stores all employee – related transactions. More precisely, TKS has to integrate employee data, leave accrual balances, labor schedules, and modified pay rules into a new system. This includes developing new interfaces, training 500 timekeepers, and deploying the application to all personal computing devices. Even though it is an off – the – shelf product, the team had to work on the details with the vendor, especially the product interfaces with the existing hardware which required some modifications by the vendor. The inputs from payroll specialists are vital for getting initial set – up and configuration of the system. Resources are required from the Payroll office, Field Technical Services, Network Applications, Unix Administration and Database Administration, and a focus group consisting of timekeepers and managers from a cross – section of the hospital.
Success Criteria: The primary success measure of the project was the accuracy of the system. Other success criteria include the following: user – friendly interface, July go – live, and $1 million total cost.
Project Process: TKS has four major phases (with addition to some sub-phases) to complete — Integration and Request (New IT requests, Initial analysis), Project Planning (Requirements documents, Planning), Project Execution (Execution), and Implementation and Support (Go-Live, Project Retrospective, Close-out)— and three major decision checkpoints: functional review, baseline review, and customer approval.