ITSU2006 Project Management
Report
Report - 30% (Due Session 12)
This assessment is to be completed in team of maximum 4 students. A group participation form, which is available in LMS, needs to be completed, signed by all group members and submitted till session 5. Once submitted, the teams will remain fixed and no member additions or deletions will be allowed unless by approval of your unit facilitator.
Objective(s)
Students are required to identify key project parameters during the phases of the project life cycle, which could accurately estimate the project flow and resources, project milestones and detailed work breakdown and scheduling. Students are required to employ project execution and monitoring techniques, which lead to a successful project closing, risk assessment and control and recommendations.
The following LOs are assessed in this assessment.
LO1 Describe the systems approach to project management and project life cycle phases.
LO2 Apply standard project management techniques and demonstrate use of associated software tools models using visual tools.
LO3 Critically determine project quality, including risks and project issues.
LO4 Identify and discuss effective communication and team management skills, techniques and strategies required of a project manager.
LO5 Write project documentations and explain the processes involved in their preparation.
LO7 Analyse techniques for monitoring and evaluating the progress of a project.
INSTRUCTIONS
The purpose of this group assessment 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. Since a project scope statement is given, the statement should be used to analyse and identify project issues, different project management tools and techniques to manage the project, conduct project risk assessment and make recommendations for improvements in the future. 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: Initially you will select your chosen company, where the workflow of the product or service needs to be studied, identified and pictured clearly. The main goal of this project is to improve the customer service for products and services via deployment of a new customer relationship management software.
Task 2: Your next task is to design a 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 3: 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., workflow analysis, configure setting, prototyping, training and releasing the software) mentioned in this project. Moreover, you should 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 4: Discuss a risk assessment plan. This should include: identifying possible risks, performing qualitative and quantitative risk analysis and planning for risk responses. To identify risks, you should apply common risk identifying techniques (for example, brainstorming, Delphi technique, interview, SWOT analysis, fish bone diagram etc.). For the simplicity, you need to apply risk assessment plan at only one stage of the project (i.e., workflow analysis, configure setting, prototyping, training and releasing the software).
Task 5: The final task is to critically analyse a controlling and monitoring method. Monitoring and controlling are aimed primarily at the scope, schedule, costs, and risk. Propose a controlling and monitoring method that suits for your project. Students can apply any one of the methods (earned value management (EVM), to complete performance index (TCPI), estimate at completion (EAC), estimate to completion (ETC) and performance reviews).
The report should be prepared in Microsoft word and uploaded on to the LMS. The word limit of the report is 2000 words. The report must use Times New Roman, 12-point font size and single line spacing with appropriate section headings.
Submission Guidelines:
All submissions are to be submitted through turn-it-in. Drop-boxes linked to turn-it-in on the LMS.
Assignments not submitted through these drop-boxes will not be considered.
Submissions must be made by the due date and time and determined by your Unit facilitator. Submissions made after the due date and time will be penalized at a rate of 10% per day.
The turn-it-in similarity score will be used in determining the level if any of plagiarism. Turn-it-in will check conference web sites, Journal articles, the Web and your own class member submissions for plagiarism. You can see your turn-it-in similarity score when you submit your assignment to the appropriate drop-box. If this is a concern you will have a chance to change your assignment and resubmit. However, re-submission is only allowed prior to the submission due date and time. After the due date and time have elapsed you cannot make re-submissions and you will have to live with the similarity score as there will be no chance for changing. Thus, plan early and submit early to take advantage of this feature. You can make multiple submissions, but please remember we only see the last submission, and the date and time you submitted will be taken from that submission.
Your document should be a single word or pdf document containing your report.
Your report must include:
• Title Page: The title of the assessment, the name of the paper you are reviewing and its authors, and your name and student ID.
• Introduction: A statement of the purpose for your report and a brief outline of how you will discuss the selected article (one or two paragraphs). Make sure to identify the article being reviewed.
• Body of the Report: Describe the intention and content of the article. If you use any research report, discuss the findings and comment on problems or issues highlighted by the authors. Discuss the conclusions of the article and how they are relevant to what you are studying this project.
• Conclusion: A summary of the points you have made in the body of the paper. The conclusion should not introduce any ‘new’ material that was not discussed in the body of the paper. (One or two paragraphs)
• References: A list of sources used in your text. They should be listed alphabetically by (first) author’s family name. Follow the IEEE style.
• The footer must include your name, student ID, and page number
CASE SCENARIO
Project scope statement normally describes the project objectives, scope, summarized costs, and resource requirements. The following scope statement particularly captured six major items: strategic goals, tactical goals, milestones, constraints, assumptions, and specifically excluded scope.
Project Scope Statement
Strategic Goals
Improve customer service for products and service by 5 percent via deployment of a new customer relationship management software.
Time: Finish by September 15, 2020; Cost: $150,000; Quality: Per service level agreement
Tactical Goals
Analyse workflow, configure software, develop prototype, and release software.
Major Deliverables: Workflow analysis, configure settings, prototype, training, release
Key Milestones
• Workflow analysed by March 15, 2020
• Configure complete by April 15, 2020
• Prototype complete by August 15, 2020
• Training complete by August 15, 2020
• Release by September 15, 2020
Major Constraints
Our key developers will not be available in June because of their visit to our European ally. Major Assumptions
Configure software to meet our workflow; we will not change our workflow to meet software.
Specifically Excluded Scope
This project does not include training on customer service skills.
Marking Guide: 100 Marks
Task Description Marks
Introduction Write an introduction for the report 5
Report Layout Report layout, language and style should be good 5
Literature
Review Select three (3) recent (not older than 2015) research papers relevant to Project Life Cycles, Integration Management, Scope Management, Schedule Management, Resource Management, Communications Management, Risk Management, Agile Project Management, Change Management, and Stakeholder Management. 9
Workflow
Analysis Analyse and clearly identify the workflow of the product and service. 8
Project Charter Design a project charter that includes, background of the project, project objectives, main project success criteria, roles and responsibility of project stakeholders, and risk and dependencies. 20
Gantt Chart Construct 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. 24
Risk Assessment Discuss a risk assessment and management plan. This should include identifying possible risks, performing qualitative and quantitative risk analysis and planning for risk responses. 9
Project
Monitoring and
Evaluation Critically analyse a controlling and monitoring method. Propose a controlling and monitoring method that suits for your chosen company. 10
Conclusion A summary of the report 5
References Follow the IEEE style 5