Assessment 4

Group Assessment

Weightage 30%

Australia Advance Education Group Pty Ltd. trading as Sydney International School of Technology and Commerce

1. Aim

The aim of this assessment is to evaluate proficiency of students in conceptualizing and implementing an IT project from inception to completion. By designing and developing a comprehensive project management plan document, students will apply their knowledge and skills in IT Project Management, incorporating both Traditional and Agile methodologies. This assessment aims to assess students' understanding and application of the Project Management Body of Knowledge (PMBOK) knowledge areas and Agile principles.

2. Learning Outcomes

• Evaluate project requirements, phases, techniques, and processes in the project development life cycle.
• Analyze and critically evaluate the application of Project Management Tools.
• Exhibit understanding and expertise in analyzing and evaluating the theories and concepts of Project Management Body of Knowledge (PMBOK) and Agile principles.
• 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 a group assessment, and no individual submissions will be accepted. Please make groups of 4 students for this assessment. 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 presentation. The report should be between 2500 and 3000 words in length, excluding the title page and list of references. All pages must be numbered. The deadline for submission of the report is midnight on Sunday, end of week 11 (Refer to the submission link for the due dates). Only one submission per group is needed. The similarity index of your report should be lessthan 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. Each group will give a presentation of 10 minutes (including a 2-3 minutes of Q&A session) in the lecture of week 12. You must convert your PowerPoint slides into PDF format and upload them on the moodle before the presentation. All students must give the presentation to receive marks. Zero marks will be awarded if a student is absent or fails to deliver the presentation.

Recommended software tool to develop Project Management Diagrams:
Free access software and you can use it over cloud. Access link:
https://www.atlassian.com/try/cloud/signup?bundle=jirasoftware&edition=free&skipBundles=true

4. Assessment Details

To complete this assessment, students have the freedom to choose any IT related project. They will need to perform a thorough analysis of their chosen IT project, identifying project goals, objectives, and constraints. They should demonstrate their ability to develop a clear project scope statement, create a work breakdown structure, define project milestones, estimate project costs, allocate resources and identify potential risks. Additionally, students should consider the iterative and adaptive nature of Agile project management, incorporating Agile methodologies such as Scrum or Kanban into their project management plan. Throughout the assessment, students should demonstrate critical thinking, analytical skills, and the ability to make informed decisions in project planning and management. They should justify their choices by referring to relevant project management principles, methodologies, and industry standards. In this assessment, students can judiciously make assumptions about various resources needed for their project. By successfully completing this assessment, students will enhance their ability to plan, execute, and manage IT projects effectively, preparing them for real-world project management challenges they may encounter in their future careers.

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 Project Management Plan

In this Project Management Plan, you should provide a clear explanation of following key aspects:

a. Scope Statement, Objectives and Deliverables:

Briefly explain the issues/problems the project will solve and its associated benefits for the organization. Define the boundaries of the project by outlining what will be included and what won't. Clearly state the goals and outcomes that the project aims to achieve. Describe the tangible outputs or results that will be produced by the project.

b. 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.

c. 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.

d. Project Network:

Convert your WBS to a Project Network and use the Activity on Node (AON) method to calculate the Critical Path of your project. You can judiciously assume the values of Early Start (ES), Early Finish (EF), Slack (SL), Duration (DUR) etc. You can use any tool to draw the Project Network. You must put a screenshot in the report. The screenshot must show the date and time from the task bar. Detailed explanation is needed along with the screenshot.

e. Resource Allocation:

Identify key resources such as human resources, technological resources etc. needed for the project. Based on the requirements and constraints of your project, determine whether it is primarily time-constrained or resource-constrained in terms of resource allocation. Explain your approach to allocating resources effectively to meet project requirements while considering factors such as team availability, skills, and equipment needs.

f. Cost Management:

Estimate the total cost of the project, considering factors such as labor, materials, equipment, overhead expenses etc. Explain the rationale behind the chosen estimation method and how it aligns with the project's scope and complexity. Make a time-phased budget for the project and show the results in the form of a table. You must put a screenshot in the report. The screenshot must show the date and time from the task bar. Detailed explanation is needed along with the screenshot.

g. Risk Management:

Explain five potential risks specific to your project and develop a contingency plan for each risk. Show your results in the form of a Risk Response Matrix. You must put a screenshot in the report. The screenshot must show the date and time from the task bar. Detailed explanation is needed along with the screenshot.

h. Ethical Issues:

For your project, identify and elaborate on any three key ethical issues that could arise during its management and execution. Consider how these issues might impact the project, the stakeholders involved and the overall success of the project.

i. Implementation of Agile Methodology:

You have the option to choose between utilizing Scrum or Kanban methodologies for managing your project.

For Scrum methodology, you must

• Create a comprehensive Product Backlog Table that lists all the features or user stories prioritized for the project. Each backlog item should be described with sufficient detail, including its priority, estimated effort or complexity, and acceptance criteria. You must put a screenshot in the report. The screenshot must show the date and time from the task bar. Detailed explanation of Product backlog table is needed.
• Create a Sprint Backlog Table that outlines the features or user stories selected for a specific sprint. Each sprint backlog item should include estimated effort, assigned team members, and any dependencies or constraints for each sprint backlog item. You must put a screenshot in the report. The screenshot must show the date and time from the task bar. Detailed explanation of Sprint Backlog Table table is needed.
• Explain how you will organize and execute sprints throughout the project, including the duration of each sprint and the activities involved.

For Kanban methodology, you must

• Develop a visual Kanban board using any tool like Asana, Trello etc. that represents the workflow of your project, including columns for different stages of work such as "To Do," "In Progress," and "Done. Populate the Kanban board with project tasks or user stories, ensuring clarity and transparency in the workflow visualization. You must put a screenshot in the report. The screenshot must show the date and time from the task bar. Detailed explanation is needed along with the screenshot.
• Explain how you will establish Work in Progress (WIP) limits for each column on the Kanban board to optimize workflow efficiency.
• Explain how you will conduct regular Kanban board reviews to assess performance, identify areas for optimization, and refine workflow processes accordingly.

5.5 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.6 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 (Will be weighed down to 20 marks)

Abstract

(5 marks)

High Distinction (85- 100%)

Clear, concise, and comprehensive summary demonstrating advanced understanding.

Distinction (75-84%)

Clear summary with minor omissions or errors, conveying good understanding.

Credit (65-74%)

Adequate summary with some clarity issues, demonstrating basic understanding.

Pass (50-64%)

Summary lacking clarity and detail, showing limited understanding

Fail (0-49%)

Unclear or missing summary, indicating significant misunderstanding.

Introduction

(5 marks)

High Distinction (85- 100%)

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

Distinction (75-84%)

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

Credit (65-74%)

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

Pass (50-64%)

Brief introduction, limited understanding, and mention of challenges.

Fail (0-49%)

Missing or unclear introduction, no understanding of operations, challenges not addressed.

Scope, Objectives and Deliverables

(10 marks)

High Distinction (85-100%)

Clearly defined scope,specific and achievable objectives, and thorough deliverables exceeding expectations.

Distinction (75-84%)

Adequately defined scope, objectives that are specific and attainable, and deliverables meeting expectations effectively.

Credit (65-74%)

Somewhat defined scope, objectives that may lack specificity or achievability, and deliverables meeting basic requirements.

Pass (50-64%)

Unclear or overly broad scope, objectives lacking specificity or achievability, and minimal deliverables meeting requirements.

Fail (0-49%)

Undefined or inappropriate scope, absent objectives, and incomplete or missing deliverables

Work Break Down Structure

(5 marks)

High Distinction (85-100%)

Comprehensive WBS with thorough task decomposition and clear hierarchy.

Distinction (75-84%)

Clear WBS with structured task decomposition and reasonable hierarchy.

Credit (65-74%)

Adequate WBS with basic task decomposition and some hierarchy.

Pass (50-64%)

Basic WBS with limited task decomposition and unclear hierarchy.

Fail (0-49%)

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

Gantt Chart

(5 marks)

High Distinction (85-100%)

Detailed Gantt chart with clear scheduling and milestones.

Distinction (75-84%)

Clear Gantt chart with well-defined scheduling and milestones.

Credit (65-74%)

Adequate Gantt chart showing basic scheduling and milestones.

Pass (50-64%)

Basic Gantt chart with limited scheduling and unclear milestones.

Fail (0-49%)

Incomplete Gantt chart lacking scheduling and milestones, or Gantt Chart copied from the internet

Project Network

(10 marks)

High Distinction (85-100%)

Accurate, detailed Project Network Diagram with clear Critical Path; comprehensive explanation and screenshot provided.

Distinction (75-84%)

Well-constructed Network Diagram, correct Critical Path; detailed explanation and screenshot.

Credit (65-74%)

Adequate Network Diagram, identified Critical Path; clear explanation and screenshot provided.

Pass (50-64%)

Incomplete Network Diagram, but identified Critical Path, basic explanation and screenshot.

Fail (0-49%)

Incomplete or inaccurate Network Diagram, Critical Path is incorrect; inadequate explanation or missing screenshot.

Resource Allocation

(10 marks)

High Distinction (85-100%)

Clearly identifies resources, determines constraints, and details an effective allocation strategy considering team availability, skills, and equipment needs.

Distinction (75-84%)

Identifiesresources adequately, determines constraints, and outlines an allocation strategy considering team availability, skills, and equipment.

Credit (65-74%)

Lists resources, determines constraints, and suggests an allocation strategy with consideration for team availability and skills.

Pass (50-64%)

Lists resources, vaguely determines constraints, and proposes a basic allocation strategy with limited consideration for team availability and skills.

Fail (0-49%)

Fails to identify resources, constraints, or propose a coherent allocation strategy, lacking consideration for team availability and skills.

Cost Management

(10 marks)

High Distinction (85-100%)

Accurately estimates project cost with detailed rationale; time-phased budget is organized and reflects cost allocation, supported by a clear screenshot.

Distinction (75-84%)

Provides reasonable project cost estimate with clear rationale; time-phased budget effectively shows cost allocation, accompanied by a clear screenshot.

Credit (65-74%)

Offers project cost estimate with reasonable explanation; time-phased budget adequately reflects cost allocation, supplemented by a clear screenshot

Pass (50-64%)

Provides basic project cost estimate with limited detail; time-phased budget lacks clarity, with a somewhat clear screenshot.

Fail (0-49%)

Fails to estimate project cost accurately; time-phased budget is poorly organized and lacks clarity, with a screenshot that is unclear or missing.

Risk Management

(10 marks)

High Distinction (85-100%)

Clearly identifies risks, develops comprehensive plans, provides detailed Matrix with screenshot.

Distinction (75-84%)

Identifies risks adequately, develops reasonable plans, provides Matrix with screenshot.

Credit (65-74%)

Identifies some risks, develops basic plans, provides Matrix with screenshot.

Pass (50-64%)

Identifies few risks, develops basic plans, provides simplified Matrix with screenshot.

Fail (0-49%)

Failsto identify or explain risks, lacks coherent plans, provides incomplete Matrix or Matrix is missing.

Agile Methodology (Scrum or Kanban)

(15 marks)

High Distinction (85-100%)

Comprehensive, detailed tables with clear explanations and priorities, supported by clear screenshots. Well-organized sprint plan demonstrating comprehensive understanding.
Creates a visually appealing Kanban board, sets clear WIP limits, and plans detailed board reviews, showcasing deep understanding of workflow optimization.

Distinction (75-84%)

Detailed tables with clear explanations, priorities, and efforts,supported by clear screenshots. Adequate sprint plan covering key aspects.
Develops a well-designed Kanban board, establishes adequate WIP limits, and outlines plans for regular board reviews, demonstrating understanding of workflow optimization.

Credit (65-74%)

Adequate tables with basic descriptions and priorities, supported by clear screenshots. Basic sprint plan addressing some aspects.
Creates a functional Kanban board, sets basic WIP limits, and offers plans for regular board reviews, with some understanding of workflow optimization.

Pass (50-64%)

Basic tables with limited descriptions, supported by unclear screenshots. Simple sprint plan covering basics.
Generates a basic Kanban board, sets simplistic WIP limits, and outlines rudimentary plans for regular board reviews, showing basic understanding of workflow optimization.

Fail (0-49%)

Inadequate tables lacking detail, supported by unclear screenshots. Poorly defined sprint plan showing lack of understanding.
Produces an inadequate Kanban board, fails to establish clear WIP limits, and lacks plans for regular board reviews, indicating poor understanding of workflow optimization.

Ethical Issues

(5 marks)

High Distinction (85-100%)

Clearly identifies and explains three relevant ethical issues. Provides thorough analysis of their impacts on the project and stakeholders.

Distinction (75-84%)

Identifies and explains three relevant ethical issues. Analysis of their impacts is clear and relevant.

Credit (65-74%)

Identifies three ethical issues with some explanation. Analysis of their impacts is basic but relevant.

Pass (50-64%)

Identifies three ethical issues but with limited explanation. Analysis of their impacts is minimal or somewhat unclear.

Fail (0-49%)

Fewer than three issues identified, or explanations are unclear. Analysis of their impacts is missing or inadequate.

Conclusions

(5 marks)

High Distinction (85-100%)

Clearly summarizes key results of the report.

Distinction (75-84%)

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

Credit (65-74%)

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

Pass (50-64%)

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

Fail (0-49%)

Summarization has major errors and omissions.

References

(5 marks)

High Distinction (85-100%)

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

Distinction (75-84%)

At least ten peer reviewed academic resources are used but few are not in proper APA format.

Credit (65-74%)

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

Pass (50-64%)

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

Fail (0-49%)

Less than ten academic resources areused. They are not peer reviewed and are not in proper APA format.

Grading Rubric for the Oral Presentation

Total Marks =10

Content

(3 marks)

High Distinction (85-100%)

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

Distinction (75-84%)

Clear and thorough analysis, demonstrating a solid understanding of the topic.

Credit (65-74%)

Adequate analysis covering key points adequately.

Pass (50-64%)

Limited analysis addressing key pointssuperficially.

Fail (0-49%)

Inadequate analysis, missing key points entirely.

Organization

(2 marks)

High Distinction (85-100%)

Highly organized structure with seamless transitions.

Distinction (75-84%)

Well-organized structure facilitates comprehension.

Credit (65-74%)

Adequate structure with some room for improvement.

Pass (50-64%)

Structure is somewhat unclear or disjointed.

Fail (0-49%)

Chaotic or nonexistent structure, making it difficult to follow.

Delivery

(2 marks)

High Distinction (85-100%)

Engaging and confident, captivating the audience.

Distinction (75-84%)

Engaging delivery maintains audience interest.

Credit (65-74%)

Somewhat engages but lacks consistency in maintaining audience interest.

Pass (50-64%)

Lacks engagement and confidence, impacting audience interest.

Fail (0-49%)

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

Answers to Questions

(3 marks)

High Distinction (85-100%)

Comprehensive, insightful, and accurate answers that demonstrate deep understanding of the topic.

Distinction (75-84%)

Clear and detailed answers, enhancing audience understanding with thoughtful engagement.

Credit (65-74%)

Responds adequately to questions, though answers may lack depth or detail.

Pass (50-64%)

Limited or incomplete answers, struggling to engage effectively with questions.

Fail (0-49%)

Irrelevant or incorrect responses, demonstrating a lack of understanding and engagement.