Note Description

Tô đậm Những nội dung không thể thiếu

Tô vàng Những nội dung cần thay đổi theo từng project và yêu cầu đề

PE 1:

Request 1: Project Description

Project Purpose/Objectives:
The purpose of the SLM system is to facilitate efficient management and tracking of learning
progress for both professors and students in FPT university . Key objectives include:
1. Providing administrators with tools to configure the system, manage subject information, and
oversee user management.
2. Empowering professors to access assigned classes, monitor student lists, and evaluate
student performance for each class.
3. Enabling students to register, access allocated classes, participate in online testing, submit
assignments, and review evaluations from their trainers.
4. Generating reports on student grades, either by class or subject, to support academic
assessment and decision-making processes.
Project Timeframe:
The project is scheduled to be completed within 4 months, encompassing all phases of the
software development life cycle, from requirements gathering to deployment.
Success criteria:
- Smart goal 1 : Increase student engagement in online courses by 20% within the next
semester.
- Smart goal 2 : Achieve a 95% student satisfaction rate with the online learning platform by the
end of the academic year.
- Smart goal 3 : Reduce the dropout rate in online courses by 15% in the upcoming academic
year.
- Smart goal 4 : Increase the utilization of online assessment tools by 30% in the next quarter.
Customer/Sponsor:
- The primary customer and sponsor of the project is FPT University
- The to-be potential customer of the project is the academic institution or educational
organization that will utilize the Student Learning Management System. This could be a
university, college, or any institution offering academic courses.

Project Milestones: Waterfall model (đổi theo timeline ở trên)

1. Initiating

2. Planning
3. Executing and Monitoring

3.1 Requirements Gathering and Analysis (Week 1-2)

3.2 System Design (Week 3-4)

3.3 Development (Week 5-10)

3.4 Testing (IT, ST, UAT) (Week 11-12)

3.5 Deployment (Week 13-16)

4. Closing

Other Project Constraints:

- Cost: The project budget is 10000 $

- Resources: The project team consists of 3 developers, 1 tester, 1 designer, 1 BA and project
managers who must collaborate efficiently to meet project deadlines.

-Technology Stack: Backend: C#. Front end : NextJS.

Deployment Environment : AWS Cloud

DẠNG 1 CÂU 2: Trích SU24

Request 2: define at least 5 roles you might have in your project team and at least 2
responsibilities (mapped to the project work packages and/or activities) for each role.

Project manager: Internal stakeholder. He has a responsibility to create a project charter and
kick off the meeting. Furthermore, his role includes planning and organizing, managing tasks,
budgeting, controlling costs and other factors. Everything they do helps make sure the project
can be completed on time and on budget, and more importantly, profitable.

BA:Internal stakeholder. He will create the Business Requirement and SRS . He bridges the
gap between external stakeholders and the development team, interpreting business
requirements into understandable development tasks to match a final software product with the
expected business value

Developer team : internal stakeholder , He writes, debugs and executes the source code of a
software application in executing phase

Designer team : internal stakeholder A UI/UX designer’s job is to create user-friendly interfaces
that enable users to understand how to use complex technical products

Tester team : Internal stakeholder. The role of a tester is to test out products for bug and
provide reports to the project teams about any issues or improvements that the product may
require
Customer;.. external stakeholder plays a vital role in providing requirements, feedback, and
validation during the product development or service delivery process. Their satisfaction and
adoption of the product/service are crucial for business success and growth.

DẠNG 2 CÂU 2: Trích ReSP24 (stakeholders) đi kèm với câu 3

identify 3 stakeholders and decide (with relevant reasons) if they are: High power or low power;
High interest or low interest; Are they unaware of the project? Are they resistant to the project?
Are they neutraP Are they supportive? Are they leading?

Based on your findings, design your strategy for how you would manage these stakeholders

unknown

Dạng 3 CÂU 2: Request 2: what type of organization you think the project is using and what
type of organization you think that should or should have used along with the reasons for this?
Provide relevant reasons for your answers

Considering the criticality of timely delivery and the need for close coordination among team
members, a projectized organization structure could be more suitable. In a projectized structure,
resources are dedicated exclusively to the project, leading to a more focused approach and
faster decision-making. This would be beneficial for meeting the tight 4-month timeframe of the
project.

Reasons for Choosing a Projectized Organization:

1. Clear Project Focus: In a projectized structure, team members are solely dedicated to the
project, ensuring undivided attention and focus on meeting project objectives within the
specified timeframe.
2. Streamlined Communication: With a dedicated project team, communication flows more
smoothly, leading to quicker decision-making and problem-solving.
3. Faster Response to Changes: Projectized organizations are more agile and can adapt quickly
to changing project requirements or external factors, which is crucial for meeting deadlines.
4. Accountability: Each team member has clear roles and responsibilities within the project,
enhancing accountability and ownership of tasks.

By adopting a projectized organization structure, the project team can maximize efficiency,
minimize delays, and ensure successful delivery of the Student Learning Management System
within the stipulated 4-month timeframe.

Dạng 1 Câu 3: Nối tiếp với Dạng 2 câu 2:

Request 3: identify at least 3 significant risks that you think the project faces. For each risk
determine how
likely you think it is to occur (the probability) and the impact if it does occur. Create your own
scoring
system for probability and impact. You might use High-Medium-Low; you might use numeric
values or you
might use percentages. Define a response for each of these risks.

Risk title 1 : Wrong budget estimate and cost overruns

Possibility : Medium

Impact: High

Mitigation Plan: add little amount of buffer for the budget (around 10%) , careful
estimation

Contingency Plan: Cut down on the project scope

Risk title 2 : The project schedule is too tight; it’s hard to complete this project on time

Possibility : High

Impact: High

Mitigation Plan: Set The priority for each of the activity

Contingency Plan: negotiate with customer to reschedule

Risk title 3 : Project manager has poor management skill

Possibility : Medium

Impact: Medium

Mitigation Plan: Plan leadership training for manager, provide PM learning material on
Udemy

Contingency Plan: choose another one as a sub PM in order to support management

task

Risk title 4 : A lack of cooperation negatively affects your member productivity

Possibility : Medium

Impact: Medium

Mitigation Plan: Encourage each team member in his task, and inspire them to greater
efforts
Contingency Plan: Encourage each team member in his task, and inspire them to
greater efforts

Dạng 2 Câu 3:
Request 3 (20%): identify at least 10 items that you believe either are or should be out of scope
for the project. Provide classify (in-scope or out-of-scope) and detailed description for each item.

10 out of scope item (tự nghĩ ra cho hệ thống)

1. Integration with Non-Academic Systems (e.g., Payroll, HR Systems)

- Classification: Out-of-Scope

- Description: The SLM system will focus solely on academic management and
tracking. Integrating with non-academic systems like payroll or HR systems is
outside the project's scope.

2. Development of Mobile Applications

- Classification: Out-of-Scope

- Description: The project will develop a web-based SLM system, and the creation of a
mobile application for the system is not included in the current project scope.

3. Social Media Integration

- Classification: Out-of-Scope

- Description: Integrating the SLM system with social media platforms for
announcements or notifications is not part of the project scope.

4. Custom Analytics or Reporting Tools

- Classification: Out-of-Scope

- Description: The project will generate standard reports on student grades and
progress. However, developing custom analytics or specialized reporting tools is
outside the project's scope.

5. Third-Party Software Licensing and Integration

- Classification: Out-of-Scope

- Description: Licensing and integrating third-party software (e.g., advanced plagiarism

detection tools) are not included in this project and must be handled separately.
6. Extensive User Training Programs

- Classification: Out-of-Scope

- Description: While basic training will be provided to users, extensive training

programs, such as workshops or certification courses, are outside the project scope.

7. Multi-Language Support

- Classification: Out-of-Scope

- Description: The SLM system will be developed in a single language (e.g., English or
Vietnamese). Providing multi-language support is not included in the project's scope.

8. Advanced AI or Machine Learning Features

- Classification: Out-of-Scope

- Description: Implementing advanced AI features, such as predictive analytics for

student performance, is not part of the current project scope.

9. Content Creation for Online Courses

- Classification: Out-of-Scope

- Description: The SLM system will provide the framework for managing and tracking
learning progress but will not include the creation of course content.

10. Integration with External Educational Platforms

- Classification: Out-of-Scope

- Description: The system will not integrate with external educational platforms (e.g.,
Coursera, edX). It will focus solely on managing internal academic activities within
FPT University.
Dạng 1 câu 4:
Request 4 (20%): determine at least 10 activities and relevant relationships (FS, SS, SF, FF)
among
them to complete one of the project deliverables
Deliverable: Project management Plan (Risk, Scope, Schedule, Quality, Resource, Stakeholder,
Procurement, Communication, integration, :
Create Cost management plan -> Create time management plan (Start to Start )
Create Resource management plan -> Create procurement management plan (SS)
Create communication management plan -> Create Stakeholder management plan (SS)
Create quality management plan -> Create Risk management plan (SS)
Create Scope management plan -> Create integration management plan (SS)
Deliverable : Codepackage of Module 1
Create Business requirement specification -> Create System requirement specification (FS)
Create Architecture design of module 1 -> Create Detail Design of Module 1 (FS)
Create prototype for module 1 -> Review prototype for module 1 with customer (FS)
Implement coding for module 1 -> executing the UT test for module 1 (SS)
Perform integration testing -> Perform System testing (FS)
Deploy in Staging environment -> UAT the module 1 in staging environment (FS)

Dạng 2 câu 4:

Giải như video bà chi

Answer:

Currently the project is 3-weeks behind the schedule. In order to make a feasible plan to recover, i’
will shorten the project 3 weeks compared to the planned schedule

If you want to shorten the project time by 3 weeks which means the new duration of the project
(assuming no delay) is 16 weeks , none path can exceed this number. First of all, when calculate
the activity to decrease the duration , you have to consider firstly all the task in critical path- the path
that has longest duration , but now 8 weeks have passed, (now you’re in task B ), so we only have a
way to shorten the time in task D, G, I . The appropriate choice is left with task G because a task
with a duration of 5 weeks should be prioritized to shorten the time. So we will have a plan to shorten
task G from 5 weeks to only 2 weeks .

But after the critical path had been reduced to 16 weeks, Path 4 still exceeding this new duration
(path 5’s duration is 17 weeks) . Obviously, we have to reduce path 4 by 1 weeks . Task E should be
prioritized to reduce 1 week as it has a longer duration than task H.

Briefly , in order to reduce the project duration by 3 weeks, we have to shorten task G by 3 weeks
and task E by 1 week.
The shortening method is as follow:

Crashing method

· Solution 1: Add people to join project to complete task G earlier than 3 weeks, task E earlier
than 1 weeks

· Solution 2 Force team to work overtime on task G and E

· Solution 3 Reward team if they can complete task G earlier than 3 weeks, task E earlier than
1 week

Crashing will increase cost.

Apply fast tracking method

Overlap task D and G

Overlap task E and H

Dạng 1 CÂU 5:
Request 5: Given the following information for a one-year project after 2 months since the
project start,
answer the below questions: PV (Planned Value)= 22.000, EV (Earned Value)= 20.000, AC
(Actual Cost)=25.000, BAC (Budget At Completion)= 120.000
a) What are the cost and schedule performance of the project? Show your calculations.
b) How is the project doing in terms of project cost and time (schedule). Explain about those
statuses
c) Use the CPI to calculate the estimate of the rest cost the team would need to complete the
project.
d) Use the SPI to estimate how many months it will take the team to finish this project.
b) Project Status
● Cost Status:
○ The CPI of 0.8 indicates the project is costing more than planned. For every
dollar spent, only $0.80 worth of work is being completed.
● Schedule Status:
○ The SPI of 0.91 shows the project is progressing slower than planned. Only 91%
of the planned work has been completed.

Summary of Results
1. CPI: 0.8, indicating cost overruns.
2. SPI: 0.91, indicating schedule delays.
3. ETC: $125,000 more needed to complete the project.
4. Estimated Time to Complete: 13.2 months (1.2 months delay).

Dạng 2 CÂU 5:
Request 5: Your project team have completed a workload equivalent to $3,000 and has spent
$4,000 to
date. Assume that you were budgeted $5,000 for the work scheduled. At the start, the team has
estimated
project budget of $9.000 and the project needs 12 months to finish. Calculate and give your
calculations
and comments on the project's current status, and the forecasts to complete the project in terms
of cost
and schedule.

EV – 3000

AC – 4000

PV – 5000

BAC – 9000

DAC – 12 months

CV cost variance : EV – AC bằng -1000 < 0 -> over budget

SV Schedule variance : EV – PV bằng - 2000 < 0 -> behind the schedule

CPI Cost performance index EV/AC bằng 0.75 < 1 -> over budget

SPI Schedule performance index EV/PV là 0.6 < 1 -> behind schedule

So the current status of this project is over budget and behind the schedule. My recommendation
is that we should negotiate with customer in order to increase budget and reschedule

Forcast :

EAC : BAC / CPI bằng 9000/0.75 bằng 12000 $

EDAC : DAC/SPI bằng 12/0.6 bằng 20 months

Dạng 3 CÂU 5:
Request 5 (20%): provide at least 5 quality cost items (prevention, appraisal, or external failure
costs), description and estimation for each cost item. The estimation should be effort (man-
days,
man-hours) for labor cost.

1. Prevention Costs

1.1. Quality Training

Description: Providing training to the project team on best practices for software development,
including coding standards, testing methodologies, and quality assurance processes.

Estimation: 20 man-hours (e.g., 2 hours of training for each of the 10 team members).

1.2. Code Review Process

Description: Establishing a formal code review process where developers review each other's
code to identify potential defects early.
Estimation: 40 man-hours (e.g., 4 hours per week for 10 weeks).

2. Appraisal Costs

2.2. Integration Testing

Description: Performing integration tests to ensure that different modules of the software work
together as intended.

Estimation: 50 man-hours (e.g., 5 hours per integration cycle for 10 cycles).

3. External Failure Costs

3.1. Bug Fixes After Deployment

Description: Addressing software bugs reported by end-users after the system has been
deployed.

Estimation: 100 man-hours (e.g., 5 hours per bug fix, with an estimated 20 bugs reported).

4. Ỉntenal Failure Cost

4.1 Rework for the poor quality module

Description : In order to optimize the cost (in cost management plan , fix price contract ) , PM
has recruited 10 freshers to develop module 1 . As a result, we should have a internal failure
cost - rework to cover the poor quality deliverable of freshers if it occur

Estimate : 5 manday - 1 senior dev