HI5029 IS Project Management T3 2024 Assignment Help

HI5029 IS Project Management T3 2024 Assessment

 

Group Assignment 

Assessment Details and Submission Guidelines   
Trimester T3 2024 
Unit Code HI5029
Unit Title IS Project Management
Assessment Type Group Assignment 
Due Date + time:

 24/Jan/2025

  11.59 pm (Melb / Sydney time)

Purpose of the assessment (with ULO Mapping) 1. Interpret and critique a variety of project management methodologies including both traditional and agile approaches; 2. Interpret user requirements and project management related data and make appropriate recommendations within a project context; 4. Apply scheduling, budgeting, risk management and other project management tools and procedures to a project.
Weight 40 % 
Total Marks Assignment (40 marks) 
(if also presentation component, please add here)
Word limit No limit words 
Submission Guidelines 
  • All work must be submitted on Blackboard by the due date along with a completed Assignment Cover Page. 
  • The assignment must be in MS Word format unless otherwise specified.     

  Academic Integrity

Information

Holmes Institute is committed to ensuring and upholding academic integrity. All assessments must comply with academic integrity guidelines. Please learn about academic integrity and consult your teachers with any questions. Violating academic integrity is serious and punishable by penalties that range from deduction of marks, failure of the assessment task or unit involved, suspension of course enrolment, or cancellation of course enrolment.
  Penalties
  • All work must be submitted on Blackboard by the due date and time, along with a completed Assessment Cover Page. Late penalties apply.
  • Your answers must be based on Holmes Institute syllabus of this unit. Outside sources may not amount to more than 10% of any answer and must be correctly referenced in full.  Over-reliance on outside sources will be penalised
  • Reference sources must be cited in the text of the report and listed appropriately at the end in a reference list using Holmes Institute Adapted Harvard Referencing. Penalties are associated with incorrect citation and referencing.

 

Group Assignment Guidelines and Specifications

 

Assignment Description

This assessment will be completed in groups of 4 students. Groups will be formed within the first 2 weeks of class.  Students are expected to critically evaluate the project requirements and provide a project plan that includes 6 main parts (9 tasks) listed in the group assignment case study below.

This assessment is worth 40% of the unit’s grade and is a major assessment. Groups are advised to begin working on this assessment as soon as possible.

Deliverable for this assessment as follows:

DeliverableWeightWeek Due
Group Case Study Report40%Week 9

Group Assignment Case Study

Case Study: "TechSolutions Portal"

Background:

TechSolutions, a global IT consulting firm, is undertaking a project to develop an innovative client portal - the "TechSolutions Portal" (TSP). The portal aims to enhance client interaction, streamline project collaboration, and provide real-time analytics. The project is critical for TechSolutions to maintain its competitive edge and elevate client satisfaction.

Project Overview:

  • Project Name: TechSolutions Portal (TSP)
  • Project Duration: 12 months
  • Project Budget: $8 million

Project Objectives:

  • Develop a user-friendly client portal for streamlined communication and project collaboration.
  • Implement advanced analytics features to provide clients with real-time insights into project progress and performance.
  • Ensure robust security measures to protect sensitive client information.
  • Integrate the portal with existing CRM and project management systems.
  • Provide comprehensive training and support for both clients and internal teams.

Project Team:

  • Project Manager: Group Leader
  • Lead Developer: Member 1
  • Security Specialist: Michael Thompson
  • Data Analyst: Member 2
  • CRM Integration Expert: Member 3
  • Training Coordinator: Sarah Patel

Project Phases:

Initiation (Months 1-2):

  • Define project scope, objectives, and key deliverables.
  • Assemble the project team and conduct stakeholder analysis.
  • Develop a project charter and secure stakeholder approval.

Planning (Months 3-4):

  • Create a detailed project plan, outlining tasks, timelines, and resource allocation.
  • Perform a risk assessment and develop a risk mitigation strategy.
  • Establish communication channels and reporting mechanisms.

Execution (Months 5-8):

  • Develop the client portal, incorporating user feedback through iterative processes.
  • Implement advanced analytics features for real-time project insights.
  • Integrate robust security measures to safeguard client data.
  • Begin CRM integration and conduct user acceptance testing.

Monitoring and Controlling (Months 9-10):

  • Regularly assess project progress against established milestones.
  • Monitor security measures and address any  vulnerabilities.
  • Ensure successful CRM integration and resolve any issues promptly.

Closing (Months 11-12):

  • Finalize the client portal development and conduct comprehensive testing.
  • Provide training sessions for clients and internal teams.
  • Launch the TechSolutions Portal with a marketing campaign.
  • Conduct a post-implementation review and document lessons learned.

Challenges:

  • Balancing innovation with security considerations.
  • Ensuring seamless integration with existing systems.
  • Managing user expectations during the iterative development process.
  • Providing effective training for diverse user groups.

Tasks

Your team is assigned the project of designing and implementing this “TechSolutions Portal” Project. Your organization uses an agile development approach. Your lecturer will play the role of the project sponsor. Your team will work collaboratively to develop a comprehensive project plan with detailed timelines and resource allocation. The project sponsor will guide your team regarding the project requirements and you are required to attend all the project meetings. In the meetings, your team should discuss the steps to initiate this project and discuss how to progress. The above given are only an indication of some basic requirements of the project. The actual project scope should be revised according to your project requirements. Your team is free to make necessary assumptions where necessary. You can make suitable assumptions and alter the project scope, budget and schedule if required. However, please indicate those parameters clearly in the introduction section.

Once you established the necessary assumptions, your group need to produce project management plans and other documents considering the project requirements you have selected. The completed project report should contain 6 main parts (9 tasks) as listed below:

  • Part 1: Project Integration Management
    • Task 1: Prepare a business case
    • Task 2: Prepare the project charter
  • Part 2: Project Scope Management
    • Task 3: Develop an initial scope management
    • Task 4: Develop a work breakdown structure (WBS)
  • Part 3: Project Schedule Management
    • Task 5: Create Gantt chart for WBS, and then identify at least five milestones
  • Part 4: Project Cost and Quality Management
    • Task 6: Develop documents for cost estimate and business case financial analysis
  • Part 5: Project Resource Management
    • Task 7: Prepare a Responsibility Assignment Matrix (RACI Chart) for the WBS
  • Part 6: Project Risk Management
    • Task 8: Create a risk register
    • Task 9: Plot the risks on a Probability/Impact Matrix

Deliverable Description

Your group needs to submit the final version of your assignment in Week 9. The structure of the final report is as follows:

  • Executive Summary: The executive summary should provide an overview of the report's outcomes and be no longer than half a page. You can find helpful guidelines on how to write an executive summary in this link: https://blog.pandadoc.com/how-to-write-executive-summary/
  • Table of contents
  • Introduction: State the purpose and objectives of the report.
  • Part 1: Project Integration Management
    • Task 1: Prepare a business case
    • Task 2: Prepare the project charter
  • Part 2: Project Scope Management
    • Task 3: Develop an initial scope management
    • Task 4: Develop a work breakdown structure (WBS)
  • Part 3: Project Schedule Management
    • Task 5: Create Grantt chart for WBS, and then identify at least five milestones
  • Part 4: Project Cost and Quality Management
    • Task 6: Develop documents for cost estimate and business case financial analysis
  • Part 5: Project Resource Management
    • Task 7: Prepare a Responsibility Assignment Matrix (RACI Chart) for the WBS
  • Part 6: Project Risk Management
    • Task 8: Create a risk register
    • Task 9: Plot the risks on a Probability/Impact Matrix
  • Overall Summary: Summarize your findings, consolidating and drawing attention to the main points of the report.
  • Referencing: Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using Harvard referencing style.
  • Appendix: Attach Meeting Agenda Minutes for 2 meetings.

Your group can use the templates provided in the .zip file to complete the report.

 

Marking Rubric

CriteriaFailPassCreditDistinctionHigh Distinction

Task 1 

(4 marks)

Major errors in business case preparation.Basic business case with some errors.Competent business case with minor errors.Well-structured and insightful business case.Exceptional, innovative business case.

Task 2 

(4 marks)

Major errors in project charter preparation.Basic project charter with some errors.Competent project charter with minor errors.Well-structured and insightful project charter.Exceptional, innovative project charter.

Task 3 

(4 marks)

Major errors in initial scope management.Basic initial scope management with some errors.Competent initial scope management with minor errors.Well-structured and insightful initial scope management.Exceptional, innovative initial scope management.

Task 4 

(4 marks)

Major errors in work breakdown structure development.Basic work breakdown structure with some errors.Competent work breakdown structure with minor errors.Well-structured and insightful work breakdown structure.Exceptional, innovative work breakdown structure.

Task 5 

(4 marks)

Major errors in Gantt chart and milestone identification.Basic Gantt chart with some errors.Competent Gantt chart with minor errors.Well-structured Gantt chart and insightful milestones.Exceptional, innovative Gantt chart and milestones.

Task 6 

(4 marks)

Major errors in cost estimate and financial analysis.Basic cost estimate with some errors.Competent cost estimate with minor errors.Well-structured and insightful cost estimate.Exceptional, innovative cost estimate.

Task 7 

(4 marks)

Major errors in RACI Chart preparation.Basic RACI Chart with some errors.Competent RACI Chart with minor errors.Well-structured and insightful RACI Chart.Exceptional, innovative RACI Chart.

Task 8 

(4 marks)

Major errors in risk register creation.Basic risk register with some errors.Competent risk register with minor errors.Well-structured and insightful risk register.Exceptional, innovative risk register.

Task 9 

(4 marks)

Major errors in the risk matrix.Basic plotting of risks with some errors.Competent plotting of risks with minor errors.Well-structured and insightful risk matrix.Exceptional, innovative risk matrix.

Appendix

(4 marks)

Incomplete or inaccurate meeting agenda. The minutes are adequately detailed, capturing key points of discussion and decisions made.Minutes demonstrate a good level of detail, providing a clear understanding of the discussions and decisions.Minutes are comprehensive, offering a thorough and insightful record of discussions, decisions, and action items.Exceptional quality minutes capturing nuanced discussions and demonstrating a deep understanding of the project.


 

Student Assessment Citation and Referencing Rules

Adapted Harvard Referencing Rules

Holmes Institute has implemented a revised Harvard approach to referencing. The following rules apply: 

  1. Reference sources in assignments are limited to sources that provide full-text access to the source’s content for lecturers and markers.
  2. The reference list must be located on a separate page at the end of the essay and titled: “References”.
  3. The reference list must include the details of all the in-text citations, arranged A-Z alphabetically by author surname with each reference numbered (1 to 10, etc.) and each reference MUST include a hyperlink to the full text of the cited reference source. For example:

1. Hawking, P., McCarthy, B. & Stein, A. 2004. Second Wave ERP Education, Journal of Information Systems Education, Fall, http://jise.org/Volume15/n3/JISEv15n3p327.pdf

 

  1. All assignments must include in-text citations to the listed references. These must include the surname of the author/s or name of the authoring body, year of publication, page number of the content, and paragraph where the content can be found. For example, “The company decided to implement an enterprise-wide data warehouse business intelligence strategies (Hawking et al., 2004, p3(4)).”

 

Non-Adherence to Referencing Rules

Where students do not follow the above rules: 

  1. For students who submit assignments that do not comply with the rules, a 10% penalty will be applied. 
  2. As per the Student Handbook, late penalties will apply each day after the student/s has been notified of the due date. 
  3. Students who comply with rules and the citations are “fake” may be reported for academic misconduct.


 

Submission Guidelines

Your documents should be a single MS Word or OpenOffice document containing your report. Do not use PDF as a submission format,

All submissions will be submitted through the safeAssign facility in Blackboard. Submission boxes linked to SafeAssign will be set up in the Units Blackboard Shell. Assignments not submitted through these submission links will not be considered.

Submissions must be made by the due date and time (which will be in the session detailed above) and determined by your Unit coordinator. Submissions made after the due date and time will be penalized per day late (including weekend days) according to Holmes Institute policies. "Get top-notch academic assistance and ensure your success with Punjab Assignment Help  your trusted partner for high-quality, plagiarism-free assignments delivered on time!"

The SafeAssign similarity score will be used in determining the level, if any, of plagiarism.  SafeAssign will check conference web-sites, Journal articles, the Web and your own class members submissions for plagiarism. You can see your SafeAssign similarity score (or match) 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 your assignment will be graded as late. Submitted assignments that indicate a high level of plagiarism will be penalized according to the Holmes Academic Misconduct policy, there will be no exceptions. Thus, plan early and submit early to take advantage of the re-submission feature. You can make multiple submissions, but please remember we grade only the last submission, and the date and time you submitted will be taken from that submission. 

Example invalid form file feedback

Join our 150К of happy users

Get original papers written according to your instructions and save time for what matters most.