IT Project Management (ICT 504) Assessment 2 Assessment Help

1. Aim The purpose of this assessment is to evaluate the proficiency of students in conceptualizing and  implementing an IT project from start to finish. The focus of the project is to identify an existing  system, such as an organization, a shopping store, a business, a university education system, or  any other relevant field, and design a new IT system to improve upon the current one

2. Learning Outcomes 

Evaluate project requirements, phases, techniques, and processes in the project  development life cycle. 

Exhibit expertise in the critical analysis of the socio-cultural and technical issues that  affect project success and the development of potential solutions. 

3. Submission Details 

This is an individual assignment. The report is to be submitted in a word or pdf format. The  assessment constitutes 30% of the total grade, with 20% allocated for the report and 10% for  the recorded presentation. The report should be between 2000 and 2500 words in length,  excluding the title page and list of references. All pages must be numbered. The deadline for  submission of both the report and the recorded 15-minute presentation is midnight on Sunday,  28 April 2024. The report and presentation must be uploaded via the Turnitin links provided  on the Moodle before the deadline. The similarity index of your report should be less than 20%.  Do not cut and paste from the internet or from AI tools including ChatGPT. Late  submissions will incur a 10% deduction in marks for each day beyond the due date. A delay of  more than 5 days will result in a grade of 0. 

4. Assessment Details 

You have the freedom to choose your own IT project, which should encompass the following  aspects: 

Problems Identification: You must identify the current problems and limitations in the  existing system and assess how a new IT system can overcome these challenges. 

Project Proposal: Once you have identified the problems, you need to develop a project  proposal outlining your proposed IT solution, which should include the scope statement,  objectives, timeline, and deliverables of the project. 

Implementation, Testing, and Deployment: After developing a project proposal, it’s time to  put your plans into action and bring the new IT system to life. Remember, there’s no need for  actual coding here, but you’ll need to dive into various elements to make it happen. You also  need to discuss the testing strategies you have employed to check for any glitches, errors, or  areas that might need improvement. Finally, in deployment phase, you will discuss the process  of rolling out the system, ensuring smooth integration with the current setup, and outlining  strategies for addressing any potential challenges during this transition phase.

In summary, this assessment requires you to demonstrate your ability to initiate an IT project,  create relevant artifacts, and implement a new IT system to improve upon an existing system.  You have the flexibility to choose your own project, provided that it addresses an existing  system and meets the aforementioned criteria. 

5. Structure of the Report  

5.1 Title Page 

This should contain the title of the report (make title as informative as possible), student name and  ID, unit code and name, and the instructor’s name. 

5.2 Abstract 

You should provide a concise summary of the key points covered in the report. Abstract should be between 200 – 300 words long (tip: write the abstract last). Do not use headings, figures or in-text  citations in this section. 

5.3 Introduction 

This section should include the following, 

Briefly introduce the organization or industry sector under consideration. 

Provide context by describing the broad areas or operations in which the organization is  involved. 

Highlight the challenges or problems faced by the organization within its current IT  systems. 

Introduce the purpose and scope of the assessment, emphasizing the goal of  conceptualizing and implementing a new IT system to overcome these challenges. 

5.4 Problems Identification and Solutions 

In this section, you should explain in detail about the current problems and limitations faced in the  existing system that is currently being used by your organization. Furthermore, you should  elaborate on how implementing a new IT system can effectively address and overcome these  challenges. 

5.5 Project Proposal 

In the project proposal, you should provide a clear explanation of following key aspects: 

Scope Statement: Define the boundaries of the project by outlining what will be included and  what won’t.  

Objectives: Clearly state the goals and outcomes that the project aims to achieve.

Deliverables: Describe the tangible outputs or results that will be produced by the project.  Milestones: Identify important checkpoints or stages in the project timeline.  

Technical Requirements: Specify the hardware, software, and other technical resources that  will be needed to complete the project successfully. 

Limits and Exclusions: Clearly define any constraints or limitations that may affect the project,  such as budget, time, or resources.  

Work Break Down Structure (WBS): Draw a WBS related to your project. You must draw it  by yourself in any project management tool. You must put a screenshot in the report. The  screenshot must show the date and time from the task bar. Do not cut and paste the WBS from  the internet. 

Gantt Chart: Draw a Gantt chart to present the timeline for the project, including key  milestones and deadlines. You must draw it by yourself in any project management tool. You  must put a screenshot in the report. The screenshot must show the date and time from the task  bar. Do not cut and paste the Gantt Chart from the internet. 

5.6 Implementation, Testing and Deployment 

In this section, you will give a brief explanation of how the project will be implemented by  creating design documents. These documents will act as the architectural blueprints for the IT  project. They will outline how various components will interact and the overall structure of the  system. No coding is needed for this assessment. You will also discuss the testing strategies  employed, including how glitches, errors, or areas needing improvement are identified. Finally,  you will explain the process of deploying the system, ensuring its seamless integration with the  current setup. 

5.7 Conclusions 

Using an analysis of the preceding sections, the conclusions should summarize your key findings.  Conclusions are the results of your own critical thinking, they should be justified through analysis  of your findings and written in your own words with no citations. 

5.8 References 

You must use correct APA (7th edition) for referencing various academic resources that you have used to write this report. Your references should enable someone reading your report to easily identify and refer to any works you have used. At least 10 recent and relevant academic resources (i.e. peer-reviewed journal articles and conference papers etc.) are needed in the report.

Grading Rubric for the Report

Total Marks = 100

Abstract 

(5 marks)

Clear, concise, and  

comprehensive  

summary  

demonstrating  

advanced  

understanding.

Clear summary  

with minor  

omissions or  

errors, conveying  good  

understanding.

Adequate summary  with some clarity  

issues,  

demonstrating basic  understanding.

Summary lacking  

clarity and detail,  

showing limited  

understanding

Unclear or  

missing summary,  indicating  

significant  

misunderstanding.

High Distinction 

(85- 100%)

Distinction 

(75-84%)

Credit 

(65-74%)

Pass 

(50-64%)

Fail 

 (0-49%)

     

Introduction 

(10 marks)

Comprehensive  

introduction with  detailed insight into  organization, thorough  analysis of IT system  challenges, clear  purpose, and scope.

Clear introduction with adequate  context, good  understanding of  operations, and  highlighted  

challenges.

Introduction with  context, basic  understanding of  operations, and  mention of  challenges.

Brief introduction,  limited  

understanding, and  mention of  challenges.

Missing or unclear  introduction, no  understanding of  operations,  

challenges not  addressed.

High Distinction 

(85- 100%)

Distinction 

(75-84%)

Credit 

(65-74%)

Pass 

 (50- 

64%)

Fail 

 (0-49%)

     

Problems  

Identification  

and Solutions 

(15 marks)

Comprehensive  

explanation of current  system issues, detailed  analysis of new IT  system benefits.

Clear explanation  of current issues,  analysis of new IT  system benefits.

Adequate  

explanation of issues,  basic analysis of new  IT system benefits.

Brief explanation of  issues, limited  analysis of new IT  system benefits.

Missing or unclear  explanation of  issues, no analysis  of new IT system  benefits.

High Distinction 

(85-100%)

Distinction 

(75-84%)

Credit 

(65-74%)

Pass 

(50-64%)

Fail 

(0-49%)

     

Project  

Proposal 

(35 marks)

Comprehensive  

explanation of various  aspects of the project  proposal,  

demonstrating  

thorough  

understanding and  

detailed analysis.

Clear explanation  covering various  aspects of the  

project proposal  adequately,  

showing good  

understanding and  analysis.

Adequate  

explanation  

addressing various  aspects of the project  proposal with basic  detail and  

understanding.

Basic explanation  with limited  

coverage of various  aspects of the  

project proposal,  

demonstrating  

minimal  

understanding.

Incomplete or  

unclear  

explanation  

lacking coverage  of various aspects  of the project  

proposal, showing  no understanding.

High Distinction 

(85-100%)

Distinction 

(75-84%)

Credit 

(65-74%)

Pass 

 (50-64%)

Fail 

(0-49%)

     

Work Break  

Down  

Structure 

(7.5 marks)

Comprehensive WBS  with thorough task  decomposition and  clear hierarchy.

Clear WBS with  structured task  decomposition and  reasonable  

hierarchy.

Adequate WBS with  basic task  decomposition and  some hierarchy.

Basic WBS with  limited task  decomposition and  unclear hierarchy.

Unclear WBS  lacking task  decomposition and  hierarchy or WBS  copied form the  internet.

High Distinction 

(85-100%)

Distinction 

(75-84%)

Credit 

 (65-74%)

Pass 

 (50-64%)

Fail 

(0-49%)

     

Gantt Chart 

(7.5 marks)

Detailed Gantt chart  with clear  scheduling and  milestones.

Clear Gantt chart  with well-defined  scheduling and  milestones.

Adequate Gantt chart  showing basic  scheduling and  milestones.

Basic Gantt chart  with limited  scheduling and  unclear milestones.

Incomplete  

Gantt chart  lacking  

scheduling and  milestones, or  Gantt Chart  copied from the  internet

High Distinction 

(85-100%)

Distinction 

(75-84%)

Credit 

 (65-74%)

Pass 

(50-64%)

Fail 

 (0- 49%)

     

Implementation  Testing and 

 Deployment 

 (10 marks)

Comprehensive  

implementation  

explanation, thorough  testing discussion,  detailed deployment  process.

Clear  

implementation  

explanation,  

sufficient testing  discussion,  

adequate  

deployment  

process.

Basic  

implementation  

explanation, brief  testing mention,  minimal deployment  explanation.

Minimal  

implementation  

explanation, brief  testing details,  limited deployment  details.

Incomplete or  unclear 

implementation  

explanation, lack  of testing and  deployment  

details.

High Distinction  (85-100%)

Distinction 

(75-84%)

Credit (65- 

74%)

Pass 

 (50-64%)

Fail 

 (0-49%)

     

References 

(5 marks)

At least ten peer reviewed academic resources are used with all of them in proper APA format.

At least ten peer reviewed 

academic 

resources are used but few are not in proper APA format.

At least ten academic resources are used.  Few of themare not  peer reviewed and  are not in proper  APAformat.

Less than ten academic resources  are used. Most of them are not peer reviewed and/or are  

not in proper APA format.

Less than ten academic  

resources areused. They are not peer  reviewed and are not in proper APA format.

High Distinction  (85-100%)

Distinction 

(75-84%)

Credit 

 (65-74%)

Pass 

(50-64%)

Fail 

(0-49%)

     

Conclusions 

(5 marks)

Clearly summarizes  key results of the report

Summarizes key results of the report with minor errors and/or minor missions

Summarizes key results of the report with one major error  

and/or one major  omission

Summarizes key results of the report with more than one major error and/or more than one major omission

Summarization 

has major errors and omissions

High Distinction  (85-100%)

Distinction 

 (75-84%)

Credit  

(65-74%)

Pass  

(50-64%)

Fail 

(0-49%)

     

Grading Rubric for the Recorded Presentation

Total Marks =10

Content 

(4 marks)

Exceptional clarity,  depth, and relevance  demonstrated with  insightful analysis.

Clear and  thorough analysis,  demonstrating a  solid  

understanding of  the topic.

Adequate analysis  covering key  points adequately.

Limited analysis  addressing key  points superficially.

Inadequate analysis,  missing key points  entirely.

High Distinction 

(85-100%)

Distinction 

(75-84%)

Credit 

(65-74%)

Pass 

(50-64%)

Fail 

(0-49%)

     

Organization 

(3 marks)

Highly organized  structure with  seamless transitions.

Well-organized  

structure  

facilitates  

comprehension.

Adequate  

structure with  

some room for  

improvement.

Structure is  somewhat unclear or  disjointed.

Chaotic or  nonexistent  

structure, making it  difficult to follow.

High Distinction 

(85-100%)

Distinction 

(75-84%)

Credit 

(65-74%)

Pass 

(50-64%)

Fail 

(0-49%)

     

Delivery 

(3 marks)

Engaging and  

confident,  

captivating the  

audience.

Engaging delivery  maintains  

audience interest.

Somewhat  

engages but lacks  consistency in  maintaining  

audience interest.

Lacks engagement  and confidence, impacting audience  interest.

Lacks engagement,  coherence, and  confidence, making  it challenging for the  audience to stay  focused.

High Distinction 

(85-100%)

Distinction 

(75-84%)

Credit 

(65-74%)

Pass 

(50-64%)

Fail 

 (0-49%)