Reference no: EM132189585 , Length: word count:2800
Project
Project Management Real-Life Situation inside the Organisations
The main objective of this assignment is to test your ability and apply your knowledge in project management and to understand the growing need for better project management, especially for information Systems (IS) projects. In order to understand IS project work environments, common project team problems, and the importance of communication within the project team.
1. Grouping/Teams: In this assignment you are required to work in a groups of (3) members. Based on your selected organisation in assignment (2) and (3) which aims to identify a real world situation. Please note that the course coordinator has the right to change and/or cancel your project at any time based on the team performance or unexpected circumstances with your team. Also, In case if you select and decide on the team you want to work with it, you do not have the right to change it. In the event of any obstacles within the team, you must inform and report it to the course coordinator as soon as possible to avoid any reflections that may impact on the overall assessment of the team.
2. Required Deliverable Tasks and Requirements: Prepare a project investigation and definition report (approximately 2500 - 3500 words). This report defines all major aspects of the project and forms include the basis for its planning and management and also the assessment of overall success based on tasks and requirements.
3. Final Submission Deliverables and General Comments: please note that this project is divided into 5 sections. For the first part, I will provide a benchmark points for assessment and feedback and the rest of your project will be assessed at the end of this course. There are several deliverables for your project that will be graded individually to make up your final project score. Each group will write and submit a technical report. It is important that each part be completed on schedule so that there is adequate time for feedback before the next part be completed. There are several deliverables for your project that will be graded individually to make up your final project score. Each group will write and submit a technical report, this report must include:
Part (1): Selection and Prioritisation for Project Management and Feasibility Study
I. Selection of an Organisation
II. Information Systems Planning Process
III. Selection of Main Project Idea
IV. Feasibility Study Analysis
Part (2): SWOT Analysis Project Time Management, and Produce a Work Breakdown Structure
I. SWOT Analysis discussion
II. Plan Schedule Management: define activities and create a detailed work breakdown structure for your project and enter realistic durations for each task, and then link the tasks as appropriate.(The breakdown should have a clear logical basis, although technical details may vary).
III. Sequence Activities: create a schedule network diagram for your project considering all logical relationships, dependencies, and leads and lags in your project. (Create your own category names as required and remember that there can never be only one right way for a project of this nature, as long as you justify your choice.
IV. Develop a critical path method, a critical chain method for your project.
V. Print screen the Gantt Chart view, Network Diagram, and view for the project and put in your project report.
VI. Print screen the schedule table to see key dates and slack times for each task put in your project report.
VII. Explain what basis you use to create the categories and work packages (tasks beneath each category).
Part (3): Human Resources Management Requirements Processes:
In this part of the project, each team is expected to outline the human resources management requirements to identify the resources they intend to use. The purpose of this part is to allow you to exercise methods and approaches to design and develop an appreciate technique for their implementation and document for the project. To meet this step, in your report, please include the requirement specification as following:
I. Human resources requirements and processes.
II. RAM (Responsibility Assignment Matrix)
III. Roles and Responsibilities for the organisational structures
IV. Create training materials for the customer on how to perform update if needed
V. Train the customer's staff on updating the project outcome if needed
VI. Use the Resource Usage view to see each person's work each month.
VII. In case that one project team member will be unavailable (due to any reason) for a few weeks in the middle of the project. Make adjustments to accommodate this situation so that the schedule does not slip and the costs do not change.
VIII. Document the changes from the original plan and the new plan.
Part (4): Project Cost Management Requirements Processes
To meet this step, in your report, please include the requirement specification as following:
I. Cost Management Plan and Activity Cost Estimates
II. Cost Estimating Worksheet and Cost Baseline
III. Suggest your project team and the hourly charge for each team member.
IV. Estimate an average number of hours per week for each team member to spend in this project for the duration of the project period. Assign resources to the tasks, and try to make the final cost in line with this estimate.
Part (5): Project Risk Management Processes
I. Identify 15 major risks for the project, linking each risk to the overall project objectives in Task 1.
II. Prioritise them using a Probability Impact Risk Assessment matrix and develop comprehensive mitigation steps for each of the top five risks.
III. You must then reflect on why identifying risk is important in the project management process.
IV. You should refer to academic literature on risk management.
4. General Recommendation for your Project:
1. Throughout the course of project management, you are constantly reminded about the triple constraints of a project are: (Scope, Time, and Cost). As a group, in this final project of the project management course you are required to illustrate and demonstrate how you will tackle these three constraints in your own project topic.
2. Keep in mind that during your project there could be many levels of interaction:
I. The technical staff on your project, lower levels of project management (if they exist on your project),
II. The customer(s), the PM's manager (upper management), vendors, subcontractors (rare), and so on.
III. Your management approach should account for all of the levels of interaction which are relevant and allowed in your project.
IV. Feel free to add narrative text to explain your approach for management. How often status and other meetings are performed could depend on the size of the project, the type of application or system being created, the culture of your organization, the nature of the customer, etc.