VIETNAM NATIONAL UNIVERSITY HO CHI MINH CITY

HO CHI MINH UNIVERSITY OF TECHNOLOGY



PROJECT MANAGEMENT FOR ENGINEERS (IM1025)

GROUP ASSIGNMENT

AGILE PROJECT MANAGEMENT

Class: CC03 – Group: 5 – Semester: 232

Lecturer: Dr. Lê Phước Luông

Student names Student IDs

Trương Tuấn Kiệt 2252411
Lý Tuấn Lộc 2252456
Lê Hoàng Minh 2052595
Phan Quang Minh 2252486
Huỳnh Trung Nghị 2152799
Đặng Khôi Nguyên 2010457

Thành phố Hồ Chí Minh – 2024

 Table of Contents
1. PROJECT OVERVIEW.....................................................................................3
1.1 Objectives and Main results.............................................................................3
1.1.1 The objective.....................................................................................................3
1.1.2 The result..........................................................................................................3
1.2 Technical requirements:...................................................................................3
1.3 Limitations and exclusions................................................................................3
2. PROJECT INFORMATION..............................................................................4
2.1 Identify tasks......................................................................................................4
2.2 Responsibility matrix........................................................................................4
3. PROJECT PLANNING USING MS PROJECT..............................................4
4. CONCLUSION & LESSON LEARNED..........................................................5
4.1 Definition............................................................................................................5
4.2 Comparison........................................................................................................6
4.3 Key principles....................................................................................................7
4.4 Scrum Framework.............................................................................................9
5. REFERENCE....................................................................................................10
 1. PROJECT OVERVIEW

1.1 Objectives and Main results:

1.1.1 The objective:

The main purpose of this report is to learn and apply Agile Project Management to
appropriate projects. In addition, focusing on learning and applying the Scrum
methodology of Agile Project Management. And to achieve that, the team needs to learn
the definition and applications of Agile Project Management.

1.1.2 The result:

Through that research, our team decided to create an attractive video to convey the
information the team had achieved and answer the requirements posed.

Through the video, the team wants everyone to be able to understand and apply
the advantages of Agile Project Management to projects.

1.2 Technical requirements:

-The video outlines the definition of Agile Project Management.

-The video highlights the strengths and weaknesses of applying Agile Project
Management.

-The video highlights cases where Agile Project Management can be applied.

-Video explains and supports Scrum methodology application.

-Video is 3-5 minutes long.

-Includes illustrations that are easy to understand for viewers.

 1.3 Limitations and exclusions

The information is limited to A guide to the Project Management Body of

Knowledge (6th ed.) and Project management: The managerial process (7th ed.)
books.

Through research, the team has identified Agile Project Management

methodologies: Scrum, Kanban, Extreme Programming (XP), Lean Software
Development, Dynamic Systems Development Method (DSDM), etc...

For the team, because Scrum methodologies are easily applied and most widely
used for projects, it has become the topic of research and development in the video. In
addition, offering too many options can make it difficult to decide to proceed with Agile
Project Management application.

2. PROJECT INFORMATION

2.1 Identify tasks

2.2 Responsibility matrix

T.Kiệt T.Lộc H.Minh Q.Minh T.Nghị K.Nguyên

 Scenario R R

Script S R R

Reseach R R R R R R

Prepare equipment R S S

Divide script R

Filming R S

Assemble footage R S

Add subtitle R S

Effect + color grading R S

Audio editor S R

Quality Review R R R R R R

Responsible (R); Supports/Assists (S)

Estimate time:

-Weeks 1 + 2: project selection has been made

-Weeks 3 +4: determine project products

-Weeks 5 + 6: research about the project, complete script and scenario for video.

-Week 7: prepare and start recording video

-Weeks 8 + 9: edit video and quality review before submitting

Estimate cost:

Resources for research, filming is already available so there are no costs incurred.

Buy some online courses about Agile. For example: Coursera’s course about Agile
project management,…
Buy video editing software. Our team use Adobe.

3. PROJECT PLANNING USING MS PROJECT

 4. CONCLUSION AND LESSON LEARNED

4.1 Definition.

Agile project management

Agile project management is a set of methodologies for handling projects that

require flexibility and speed. It contrasts with traditional methods that emphasize detailed
planning and fixed requirements. The core principle of agile is to work iteratively,
delivering value in small increments and continually adapting to feedback.
 There are some of framework of Agile project management like Extreme
programming (XP), Feature-driven development, the Scrum …

Extreme programming is an Agile project management methodology that targets

speed and simplicity with short development cycles and less documentation. Feature-
Driven Development is a framework in the Agile methodology. As the name suggests, it
focuses on developing working software with features that satisfy client needs. FDD aims
to ensure regular and on-time delivery to customers. But Scrum is still the most popular
Agile framework because of its simplicity, flexibility, teamwork focus, empirical process
control, and widespread adoption.

The Scrum methodology

The Scrum methodology was developed in the 1990s based on a Harvard Business
Review article titled “The New Product Development Game.” Most project managers
would name Scrum as the most popular Agile framework.

As with other Agile frameworks, Scrum entails an iterative approach to project

management. The Scrum methodology prescribes breaking a project down into sprints
that typically only last one to four weeks. Each sprint ends with the completion of a
workable version or draft of the final project deliverable.

The Scrum approach’s short iterations enable your team to continuously deliver a
working version of the final product.

Scrum was initially designed using a software model that follows a set of roles,
responsibilities, and meetings. It’s flexible enough to be used for any complex project in
any industry but works best when your project results in a concrete product rather than a
service.

4.2 Comparison

Waterfall Model Agile Project Management

Methodology Linear approach with Incremental approach focuses on

 predefined order of tasks flexibility and adaptability

Fixed requirement from the

Requirements can be changes
Flexibility start, changes are costly
according to the customer needs
and time consuming

Strict control and planning, Focuses on collaboration,

Project control project is measured against communication, project is
a plan measured by customer needs

At the beginning and the

Customer involvement Throughout the project
end of the project

Identify and manage Manage iteratively throughout

Risk management
upfront the project

4.3 Key principles

 Agile framework has 3 main roles

Project Owner:

-The project owner oversees the scope because they represent the clients, users,
sponsors. The scope is the client's needs or requirements.

-Schedule and manage apriority tasks.

- Acts as a communication node with customers to inform about progress and

costs.

Subject Matter Expert (SME)

-Deep knowledge and expertise in the subject of the project, the main role to
execute the tasks.

-Guidance, leadership, quality control

-Risk management

Scrum Master

- Protect the agile framework

- Remove blocker(issue) for the team

- Promote healthy team behavior

- Sprint planning, daily scrum, sprint review

- Monitor and measure progress like backlog (list of deliverable/activities)

 4.4 Scrum Framework

Feature

Before starting the project we usually have pre-project phase usually come up with
initiation and scope definition (use WBS - A work breakdown structure is a project
management tool that breaks down a project into smaller, more manageable components)
so we can come up with the concept product backlog – the complete list of
deliverables/activities have to be done.

A sprint is execution cycle that has fixed duration (1 to 4 weeks)

Next step is to select some of the activities in product backlog to execute in that
working cycle. Sprint backlog is the to-do list to be executed in the sprint that cycle of
execution. In sprint planning we don’t plan for the whole project but just on activities for
that sprint. In most cases 1 scrum team is working for that list for two weeks and having
daily 15 mins and do daily scrum to check if everything is fine.

After 2 weeks they stop and do the sprint review. When the job is finished go back
the product backlog and do the next sprint. In sprint review and sprint retrospective team
is receiving feedback in which they can input and change work for the next sprint.
 5. REFERENCES

1. Project Management Institute. (2017). A guide to the Project Management Body

of Knowledge (PMBOK guide) (6th ed.). Project Management Institute.
2. Larson, E., & Gray, C. (2017). Project management: The managerial
process (7th ed.). McGraw-Hill Education.
3. Google Career Certificates. (2021, June 2). Agile Project Management.
Coursera. https://www.coursera.org/learn/agile-project-management#modules