COURSE CODE WIX2002

COURSE NAME PROJECT MANAGEMENT

SEMESTER 1
SESSION 2023/2024
LECTURER Dr. Hema Subramaniam
AP. Dr. Rodina
Dr. Chiam Yin Kia
TUTORIAL / PBL / SEMINAR SEMINAR 3
Final Project Presentation, Project Report and Peer
Assessment
WEEK WEEK 13 and 14
MODE OF TUTORIAL / PBL Group CYK4
(GROUP OR INDIVIDU)
CLO CLO 3 - Perform a project to track project
schedule, expenses and resources with the use of
suitable project management tools.

Project Report
Project Report outline as follows:

1. Project Overview

1. General Project Information

Project Title: Digitilize Legal aid
Project Advisor: Dr Chiam Yin Kia
*circle wherever applicable
SDG: SDG 16: Peace, Justice and Strong Institutions
*circle wherever applicable
Team ID CYK4

1
2. Project Team
Name Responsibilities E-mail
Project Manager: Ali Rangga Pratama Lead overall Project Alirangga3344@gmail.com
Planning and Coordination
Scrum Master: MI YING YE Facilitating Scrum miyingye0219@gmail.com
Processes
Design Lead: Ajeng Maheswari User Experience (UX) and ajengpurwanto28@gmail.c
Interface Design om

Test Lead: CHEN RUNZE Test Planning and Quality crz990723@gmail.com

Assurance

3. Possible Stakeholders (e.g., those with a significant interest in or who will be significantly affected by this project)
Legal Aid Organizations, End Users (students, immigrants, small business owners, and
anyone navigating legal processes), Legal Professionals

4. Project Scope Statement

Project Goal and Scope The primary goal is to empower individuals who may face legal challenges, providing them with the tools
and information needed to navigate the legal system effectively. (Target 16.3)
Scope
- immigrants, small business owners, and anyone navigating legal processes
- Young Adults (18-25), Working Professionals (26-40)

Project Objectives Describe the measurable outcomes of the project (at least 3 objectives)
1. To complete the prototype, initiate user onboarding, and gather feedback for future improvements in
week 14
2. To Address the specific needs of the target audience by providing clear legal information by january
2024
3. To develop an application that can be a source to any people who are facing any legal challenges by
the end of january 2024

Assumption and Constraints All of the members didn’t have any experience in technology since no one is from any major that
related into technology science / computer science

6. Sign-off
Name Signature Date
(MM/DD/YY
YY)
Project Advisor: Dr Chiam Yin Kia
Project Manager Ali Rangga Pratama (11/02/2023)

2. Description of product backlog items (PBI)

2
3
 3. Project Gantt Chart (Gantt Chart-Planning phase vs Gantt Chart – Final Phase)

4. Project Cost Estimation (Cost Estimation-Planning phase vs Cost Estimation– Final Phase)

RESPONSIBLE STORY Estimated Hours

TASK NAME Total Hours Total Cost
(Team Member Name) POINTS per story points

SPRINT 1
10
A001 Mi ying ye 1 10 450

10 450
A002 Ali Rangga 1 10

10 900
B002 Ajeng Maheswari 2 20

10 1350
B003 Chen Ruze 3 30

4
 Sprint Retrospective All none 10

SPRINT 2
10
.C001 Ajeng Maheswari 2 20 900

10
B001 Ali Rangga 2 20 900

10
A004 Chen Ruze 2 20 900

10
C002 Mi ying ye 2 20 900

Sprint Retrospective all none

SPRINT 3
10
D001 Chen ruze 2 20 900

10
C005 Ali Rangga 2 20 900

10
C003 Mi ying ye 2 20 900

10
D003 Ajeng Maheswari 3 30 1350

Sprint Retrospective all none

SPRINT 4
10
D002 Mi ying ye 2 20 900

10
C004 Ajeng Maheswati 3 30 1350

Sprint Retrospective all none

TOTAL COST 13.050

Assumption (BASED ON GROUPS DECISION) Every week work for 40 hours (8 hours per day * 5 days)
Every hour paid RM 45 Each story point could represent a range of 4-12 hours. (In this sample, we
used 10 hours for 1 story point)

5. Project Risk Management

a. Risk Assessment Form

Risk Event Likelihood 5 Impact 5 Detection When

(Most likely) (High impact) Difficulty
to 1 (least to Scale: 5 (no
5
 likely) 1 (No impact) warning) to 1
(lots of time
to
react).
Software integration issues 3 4 3 Development
Phase
Delay in development due 4 4 2 Throughout the
to lack of technical project
experience lifecycle,
especially
during initial
development
phases
Data privacy breaches 2 5 2 Post
Implementation
Scope creep due to 4 3 1 Throughout
changing legal Project
requirements Lifecycle

b. Risk Response Matrix

Risk Event Contingency Plan Trigger Who is

Responsible
Software integration Implement modular Integration test Ajeng Maheswari
issues integration and testing failures
Data privacy breaches Conduct regular security Security breach Chen Ruze
audits; have a breach detected
response plan in place
Scope creep from Regularly review legal Legal requirements Ali Rangga Pratama
changing legal changes and adjust scope change
requirements accordingly

6. Sprint Report
a. The Velocity Chart, shows the work that the team has finished in each sprint. This is
useful for indicating the team’s capacity (a sample of the Velocity Chart is given

6
 below).

Velocity Chart
4.5

3.5

2.5

1.5

0.5

0
Sprint 1 Sprint 2 Sprint 3 Sprint 4

Committed Completed

b. Sprint Reflection (Retrospective Board) – depending on how many sprints you have
scheduled.
i. Sprint 1
 Challenges: Team members struggled with technical tasks and understanding IT-
related requirements.
 Improvements: Focused on basic IT training and familiarization with technical
terms and processes.
 Successes: Completed foundational tasks on schedule despite the learning
curve.
ii. Sprint 2
 Challenges: Integration of technical work was slower due to lack of experience.
 Improvements: Learn from another IT friend on how to make a good prototype.
 Successes: Achieved better task breakdown, leading to clearer individual
responsibilities.
iii. Sprint 3
 Challenges: there are a lot of public holidays and a lot of members have a test,
causing delays.
 Improvements: Better and clearer flow of the task in the team
 Successes: Improved collaboration within the team and a better understanding
of testing protocols.
iv. Sprint 4
 Challenges: Finalizing tasks took longer as the team double-checked work.
 Improvements: Sought feedback from other friends regarding the prototype.
 Successes: Finished the assignment before the deadline.
7
7. Final Product Review
a. Module 1
i. Brief Description
Sign up module, user login app or register using their email
ii. Screenshot of the module

b. Module 2
i. Brief Description
user can change their profile details in this module
ii. Screenshot of the module

8
c. Module 3
i. Brief Description
User can connect with nearby lawyers, access documents regarding their
legal situation, and book a lawyer from here
ii. Screenshot of the module

d. Module 4
9
 i. Brief Description
User can access Frequent access question and give feedback for our app
ii. Screenshot of the module

8. Lesson Learned (What the lesson you have learned at the end of the project)

10
 a) Future Direction:
- To develop an application that can be a source to any people who are facing any legal challenges.
- To complete the prototype, initiate user onboarding, and gather feedback for future improvements.
- To Address the specific needs of the target audience by providing clear legal information.

b) Lessons Learned:
- Elaborate the purpose and importance of project management
- Planning, tracking and completion of project.
- How to make an application step by step.
- How to estimate project time and costs
- Perform a project to track project schedule, expenses and resources with the use of suitable
project management tools.
- SDGs 16
- How to make a project backlog, risk management, sprint report, Gannt chart etc
- How to work in teams.
- Fundamental of project management.
- Project control.
- Project audit and closure.

c) Accomplishments:
- Make a project backlog.
- Risk management
- Sprint report
- Finishing the application
- Cost and expenses report
- Final project report

d) Problem Areas:
- Team communication
- Understanding how to create an application.
- Doing the project according to the schedule.

Final Project Presentation

You are expected to present the Final project. The details as follows:
a) Presentation length: 20-25 minutes
b) Presentation format: Infographic style (1 page ONLY)

11
 c) Refer to the below example (information needed to include in the Infographic.)

Marking Rubric

Marking rubric (Project Report)

12
 Criteria
Project Overview
Description of product backlog
items (PBI)
Project Gantt Chant
Project Risk Management
Sprint Report
Final Product Review
Lesson Learned
Overall Mark (35%)
Marking rubric (Final Presentation)
Criteria
Presentation Quality
Understanding of the agile
approach
Responses to Questions
Overall Mark (10%)
Excellent (3-5%)
The project overview is apparent,
detailed, and comprehensively
understands the project's context
and scope.
The PBI mostly follows the user
story format, with minor deviations.
Provide the timeline for all the
sprints which includes (from sprint
start to sprint end) , actions, people
involve and user stories assigned
for the sprint.
Able to explain the differences
between plan and executed gantt
chart
Clearly identified the risks involved
in the project and able to provide
clear assessment and response
matrix.
Provide the sprint tracking for all
sprint and compare the team
efficiency from one sprint to another
using velocity chart.
Comprehensively covers all the
modules as stated in the PBI
Clear and actionable
recommendations based on the
lessons, with well-defined action
items and responsible parties.
Marks Obtained / 35
Excellent (3-5%)
The presentation was well-structured,
visually appealing, and free from
distracting elements.
Good understanding of Agile
principles, with clear explanations and
practical application.
Responds to questions confidently,
providing thorough and accurate
answers.
Marks obtained/ 15 * 10
END OF INSTRUCTION
Needs Improvement (1-2%)
The project overview is unclear,
lacks detail, and fails to provide a
complete understanding of the
project.
The PBI deviates from the user
story format, causing confusion or
misinterpretation.
Provide the timeline for at least
one sprints including the general
timeline and user stories assigned
for the sprint.
Satisfactory development of risk
mitigation strategies, but may lack
some details or clarity.
Provide the sprint tracking for at
least one sprint. Tracking for a
sprint using appropriate chart.
Covers at least 50% of modules
from the PBI
Lack of clear, actionable
recommendations.
Needs Improvement (1-2%)
The presentation lacked
organisation, visual aids, or
professionalism.
Limited understanding of Agile
principles, with explanations
needing more depth and clarity.
Struggles to respond to questions
and may need more complete or
accurate answers.
13