PMG201c - Final PE #1 (Fall 2024)

Request 1 (20%): provide project name and give detailed descriptions for the
project in which you mention clearly its key characteristics:
purpose/objectives (unique), timeframe (temporary), project milestones
(time constraints), customer/sponsor (clearly defined), success criteria, and
other project constraints (cost, resources, or quality)

Project Name: Cosmotopia – Cosmetics E-commerce Website with Affiliate

Feature

Project Purpose/Objectives:

The purpose of the Cosmotopia platform is to create an online cosmetic store

with an integrated affiliate system that allows individuals to earn
commissions by promoting products. Key objectives include:

1. Developing a user-friendly online store for cosmetic products with

an easy-to-navigate interface.

2. Implementing an affiliate system that allows users to register as

affiliates, get unique referral links, and track their sales commissions.

3. Providing detailed analytics and reports for both affiliates and the
shop owner to track performance, sales, and commissions.

4. Enabling efficient product management and order processing for

the shop owner, ensuring smooth transactions and customer
satisfaction.

Success Criteria:

Smart goal 1: Increase the number of affiliate sign-ups by 30% within the
first 3 months of launch.
Smart goal 2: Achieve a 25% increase in online sales from affiliate-driven
traffic within 6 months.
Smart goal 3: Ensure at least 90% of affiliates have made at least one sale
within the first quarter.
Smart goal 4: Increase customer retention rate by 15% within the first
6 months after launching the affiliate program.
Project Timeframe:

The project is scheduled to span 4 months, from March 1, 2025 to June

30, 2 025, covering all phases of development, from gathering requirements
to the final deployment.

Project Milestones: Waterfall Model

1. Requirements Gathering and Analysis (Week 1-2)

Collecting all project requirements, meeting with the customer (shop
owner) to define features, and setting up project scope.

2. System Design (Week 3-4)

Designing the website layout, user interface (UI), affiliate management
system, and overall architecture of the platform.

3. Development and Unit Testing (Week 5-10)

Coding the website, implementing product listings, affiliate systems,
order management, and testing each feature.

4. Testing (Integration Testing, System Testing, User Acceptance

Testing) (Week 11-12)
Testing the full platform, including affiliate registration, product
purchase flow, commission calculations, and overall user experience.

5. Deployment (Week 13-16)

Deploying the platform, ensuring it is fully operational, and providing
training for the shop owner on using the admin dashboard.

Customer/Sponsor (Clearly Defined):

The primary customer and sponsor of the project is Hana Beauty, a local cosmetic shop
in HCM City. The potential customers of the project are other cosmetic shops or online
retailers who want to sell their products online and use affiliate marketing to increase
sales.

Other Project Constraints:

 Cost: The project budget is $5,000.

 Resources: The project team consists of 2 developers, 1 tester, 1

designer,1BA and 1 project manager. The team must work together
efficiently to meet project deadlines.
  Technology Stack:

o Backend: .NET

o Frontend: React.js

o Database: MySQL

 Deployment Environment: DigitalOcean

Request 2 (20%): 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 neutral? Are they supportive? Are
they leading?

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

Stakeholder 1: Shop Owner (Owner of Hana Beauty)

 Power: High

 Interest: High

 Attitude: Leading

 Awareness: Aware

 Management Strategy:
The shop owner holds a high level of power and interest
because she sponsors the project and makes critical decisions.
She is aware of the project and plays a leading role. Therefore,
the project team should engage her closely by organizing
regular meetings, providing frequent progress updates, and
involving her in major decision-making processes.

Stakeholder 2: Affiliate Marketers

 Power: Low

 Interest: High

 Attitude: Supportive (after launch)

  Awareness: Unaware (during development)

 Management Strategy:
Affiliate marketers have low power but high interest because
they will benefit from promoting products after the system is
launched. During the project development phase, they are
unaware of the project. The team should plan post-launch
training sessions, create detailed user guides, offer responsive
support, and send regular communications to keep them
informed and motivated once they begin using the platform.

Stakeholder 3: Customers (Website Buyers)

 Power: Low

 Interest: Medium

 Attitude: Supportive (after launch)

 Awareness: Unaware (during development)

 Management Strategy:
Customers have low power and medium interest. They are
unaware of the project during the development phase. The
team should focus on improving the user experience, providing
clear product information, offering customer support, and
gathering feedback after launch to ensure customer
satisfaction and loyalty.

Request 2 (20%): what type of organization you think the project using and
what type of organization you think that should apply or should have applied
along with the reasons for this? Provide relevant reasons for your answers

Considering the need to finish the project fast and work closely together, a
projectized organization should be used. In this structure, everyone works
only for the project. This helps the team focus better and make faster
decisions. It will be very good for completing the cosmetics affiliate website
in just 4 months.

Reasons for Choosing a Projectized Organization:

 Clear Focus: Team members only do project work, so they can focus
well on their tasks.
  Easy Communication: Everyone reports to one project manager, so
it’s easy to talk and solve problems.

 Fast Changes: The team can quickly change plans if needed.

 Clear Jobs: Everyone knows exactly what they need to do.

By using a projectized structure, the team can work faster, avoid problems,
and finish the website on time.

Request 2 (20%): 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

 Manage the overall project schedule, ensuring tasks are completed on

time.

 Communicate with stakeholders to provide updates and handle

feedback.

 Full-stack Developer (Backend + Frontend)

 Develop the website, integrating both frontend and backend

functionalities.

 Build and manage the database to store product, order, and customer
data.

 Tester (Quality Assurance)

 Conduct tests on the website to identify bugs and ensure the features
work as expected.

 Perform user acceptance testing (UAT) to ensure the product meets

requirements.

 Designer

 Design the website layout, including the user interface and user
experience.
  Create graphics, banners, and other visual elements for the website.

 Business Analyst (BA)

 Gather and analyze requirements from stakeholders (shop owners,

affiliates, etc.).

Request 2 (20%): create a Responsibility Assignment Matrix (RAM) in which

you need to create 10 work packages or activities which can be assigned to
the team and you need to come up with specific team members or roles who
will complete this work (R-Responsible, A-Accountable, C-Consult, or I-Inform)

 Create Project Charter: PM (R), BA (C), Dev (C), Tester (C), Customer (C)

 Create SRS: PM (A), BA (R), Dev (C), Tester (C), Customer (C/R)

 Create BD (Business Design): PM (A), BA (R), Dev (C), Tester (I/C),

Customer (C)

 Create DD (Design Document): PM (A), BA (C), Dev (R), Tester (I/C),

Customer (I)

 Implement Coding: PM (A), BA (C), Dev (R), Tester (C), Customer (I)

 Create Test Scenario/Test Case: PM (A), BA (R), Dev (C), Tester (R),
Customer (C)

 Perform Testing: PM (A), BA (I), Dev (C), Tester (R), Customer (I)

 Internal Review of Test Results: PM (A), BA (I), Dev (C), Tester (R),
Customer (I)

 Fix Bugs: PM (I), BA (I), Dev (R), Tester (C), Customer (I)

 Prepare Internal Report: PM (A), BA (R), Dev (C), Tester (C), Customer
(I)

Request 3 (20%): Go back to the three stakeholders you identified in the

Request 2. Create a communication plan that includes each of these
stakeholders and the communications you believe they should receive. Each
communication needs to include following information: information, purpose,
frequency, method or format, responsible, review by.
1. Stakeholder: Shop Owner

 Information: Project progress updates, feature decisions, milestone

achievements

 Purpose: Keep the shop owner informed and involved in key decisions

 Frequency: Weekly

 Method or Format: Online meetings and email reports

 Responsible: BA

 Review by: Project Manager

2. Stakeholder: Affiliate Marketers

 Information: New feature announcements, user guides, promotional

opportunities

 Purpose: Support affiliates with updated tools and encourage active

participation

 Frequency: Monthly and when major updates are released

 Method or Format: Email newsletters and announcements on affiliate

dashboard

 Responsible: Marketing Team

 Review by: Project Manager

3. Stakeholder: Customers

 Information: Website updates, new promotions, customer satisfaction

surveys

 Purpose: Inform customers about changes and gather feedback for

improvements

 Frequency: After key updates or promotional events

 Method or Format: Website banners, notification emails, short

surveys
  Responsible: Customer Support Team

 Review by: Project Manager

Request 3 (20%): 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: Project delay

 Possibility: Medium

 Impact: Medium

 Mitigation Plan: Set clear goals for each task and assign
responsibilities properly to avoid delays.

 Contingency Plan: If delays occur, work overtime or add more team

members to speed up the work.

 Risk: Budget overruns

 Possibility: Medium

 Impact: Medium

 Mitigation Plan: Create a detailed budget and monitor spending

closely to prevent going over budget.

 Contingency Plan: If costs exceed the budget, reduce unnecessary

features or postpone non-essential tasks.

 Risk: Poor team cooperation

 Possibility: Medium

 Impact: Medium

 Mitigation Plan: Hold regular team meetings to improve

understanding and coordination.
  Contingency Plan: If cooperation doesn't improve, reorganize the
team or bring in additional help to keep the project on track.

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

đề trên hỏi mỗi out of scope thui nhưng soạn sẵn source lun nè
Project Deliverables

 Cosmotopia Cosmetics Website: A complete website for customers

to buy cosmetics online.

 Admin Management Page: An admin panel for store owners to add

products, manage orders, and track customers.

 Affiliate Program System: A system that allows users to register as

affiliates and earn commissions.

 Online Payment Integration: Connect the website with online

payment gateways.

 Product Review Feature: Customers can leave reviews and ratings

for products they purchased.

 Order Notification System: Send order confirmation and order

updates to customers via email.

 Mobile-Friendly Design: The website will be optimized for mobile

phones and tablets.

 Basic Sales Reports: Generate simple reports about sales, orders,

and affiliate earnings.

 Customer Support Contact Page: A contact form for customers to

send questions or feedback.

 User Authentication and Security: Login/logout features with basic

security to protect user accounts.

In-Scope Items
  Building the website for cosmetics sales and affiliate marketing.

 Developing a basic admin system to manage products, orders, and

affiliates.

 Connecting with online payment gateways like PayPal, Stripe, or local

providers.

 Testing the website for main browsers and mobile devices.

 Setting up cloud hosting for the website (e.g., AWS, Azure).

 Providing basic training documents for admin users.

 Customer support and maintenance for 6 months after the website is

launched.

 Basic SEO optimization for search engines.

 Setting up email notifications for orders and affiliate signups.

 Collecting feedback from users for future improvements.

Out-of-Scope Items

 Building a Mobile App: Only a mobile-friendly website will be

created, not a separate mobile app.

 Adding Advanced AI Features: No AI-based product

recommendations or chatbots in this phase.

 Integrating with Other E-commerce Platforms: No connection to

Shopee, Lazada, etc.

 Multi-language Support: The website will only support Vietnamese

and English.

 Manual Data Migration: Not transferring old sales/customer data

from previous systems manually.

 Providing Hardware: No delivery of servers, laptops, or devices.

 Customized Affiliate Rules per User: Only one general rule for all
affiliates.

 Offline Access: The website needs an internet connection to use.

  Extending Support Beyond 6 Months: Support longer than 6
months will need a new contract.

 Handling Complex Tax Calculations: Only basic tax settings will be

included (no special rules for different countries).

Request3 : List out and describe 2 project SMART goals

Request 3 (20%): define at least 5 quality assurance (QA) or quality control

(QC) activities for the project. For each activity, you need to classify it to QA
or QC + clearly describe the purpose, when and how to do it.
SMART Goal 2:

"Achieve a 25% increase in online sales from affiliate-driven traffic

within 6 months."

 Specific (S): Boost sales generated by affiliate traffic.

 Measurable (M): Target a 25% increase in online sales.

 Achievable (A): Through affiliate training and promotional support.

 Relevant (R): Higher sales align with the core objective of the affiliate
program.

 Time-bound (T): Reach the goal within 6 months after launch.

🎯 SMART Goal 3:

"Ensure at least 90% of affiliates have made at least one sale within
the first quarter."

 Specific (S): Make sure most affiliates achieve their first sale.

 Measurable (M): At least 90% of affiliates must complete one sale.

 Achievable (A): By providing selling resources and onboarding

support.

 Relevant (R): Motivated affiliates will stay active and engaged.

 Time-bound (T): Within the first 3 months (1 quarter) after launch.

Request 4 You are requested to do the critical path analysis by providing all
the paths (from the start to the end of the project) with duration for each
path, the critical path and project duration, the early start value (the first
activity has an early start of zero), and the float for each task/activity of the
project.

Request 4 You are requested to do the critical path analysis to

Provide all the paths (from the start to the end of the project) with duration
for each.

Specify at least 3 solutions (with detailed explanation) to shorten this

schedule 3 weeks.

Request 4
a) Use the critical path analysis technique to identify the minimum duration
to complete this project

b) In the 8th week, you are executing the activity B and found that you need
to speed up the project schedule to recover 3-week delay. Define 2 solutions
with relevant explanation and assumptions (if needed) to achieve that (how
it would help and difficulties/impacts to the project).

Request 4 (20%): identify at least 4 project phases/iterations and 2 main

deliverables in each phase/iteration. You need to provide the description for
each of the identified deliverables about its content/purpose.
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: Affiliate Dashboard Page

1. Design UI/UX for affiliate dashboard → Create wireframe for

dashboard layout (FS)

2. Create wireframe for dashboard layout → Create database

schema for affiliate data (FS)

3. Create database schema for affiliate data → Create API to get

affiliate stats (FS)
 4. Create API to get affiliate stats → Develop frontend page to
display affiliate stats (FS)

5. Develop frontend page to display affiliate stats → Connect

frontend to affiliate stats API (SS)

6. Connect frontend to affiliate stats API → Perform unit test for

affiliate stats API (FS)

7. Perform unit test for affiliate stats API → Perform frontend unit
test for dashboard (SS)

8. Perform frontend unit test for dashboard → Perform integration

test for affiliate dashboard (FS)

9. Perform integration test for affiliate dashboard → Deploy on

staging server (FS)

10. Deploy on staging server → UAT the affiliate dashboard on

staging (FS)

11. UAT the affiliate dashboard on staging → Deploy to

production (FS)

Các bước chi tiết:

1. Design UI/UX for affiliate dashboard: Thiết kế giao diện người dùng
và trải nghiệm người dùng cho trang dashboard của affiliate. Đảm bảo
bố cục, màu sắc, và các yếu tố trực quan dễ sử dụng.

2. Create wireframe for dashboard layout: Tạo wireframe (bản phác

thảo) cho cấu trúc của trang dashboard, xác định các mục cần hiển thị
như số liệu thống kê, biểu đồ, và các công cụ lọc.

3. Create database schema for affiliate data: Xây dựng cơ sở dữ liệu

để lưu trữ dữ liệu liên quan đến affiliate như số lượt click, doanh thu,
hoa hồng, v.v.

4. Create API to get affiliate stats: Tạo API để lấy dữ liệu thống kê của
các affiliate từ cơ sở dữ liệu.

5. Develop frontend page to display affiliate stats: Phát triển trang

frontend để hiển thị thông tin từ API, bao gồm các số liệu và biểu đồ
thống kê.

6. Connect frontend to affiliate stats API: Kết nối trang frontend với
API để lấy dữ liệu thống kê của affiliate và hiển thị trên dashboard.
 7. Perform unit test for affiliate stats API: Kiểm tra các API đã phát
triển để đảm bảo chúng hoạt động chính xác và không có lỗi.

8. Perform frontend unit test for dashboard: Kiểm tra các phần tử
frontend, như các bảng, biểu đồ, và các công cụ lọc, đảm bảo rằng
chúng hiển thị đúng thông tin.

9. Perform integration test for affiliate dashboard: Kiểm tra tích

hợp toàn bộ hệ thống từ frontend đến backend, đảm bảo rằng dữ liệu
từ API hiển thị chính xác trên giao diện người dùng.

10. Deploy on staging server: Triển khai trang dashboard lên môi
trường staging để kiểm tra thực tế.

11. UAT the affiliate dashboard on staging: Thực hiện kiểm thử
chấp nhận của người dùng (UAT) trên môi trường staging, thu thập
phản hồi từ người dùng và điều chỉnh nếu cần.

12. Deploy to production: Sau khi kiểm tra xong trên staging và
mọi thứ đều ổn, triển khai lên môi trường sản xuất để người dùng cuối
có thể sử dụng.

FS Finish to start Task nay finish thi task kia moi start

SS start to start task nay start thi task kia moi start

SF start to finish task nay start thi task kia moi finish

FF finish to finish task nay finish thi task kia moi finish

Request 5 (20%): The project was expected to cost $6 million for three
months. At the end of one month, you use earned value management as a
performance management technique and get the following information:

VD 1 dự án có buget là 10000$ trong 10 ngày

Earn value Plan value actual cost ( số tiền

thực tế)
Dự án đi qua 3 ngày 3000 - 3 ngày 3 ngày có thể chi 5000
nhưng đạt đc 40$ thì là => đã đội quá 4000
4000 over r .
3000-3 ngày
từ 3 con số đó có thể tính được 4 cái :
CV (cost varient) : chênh lệch chi phí = EV – AC

SV (schuduel varient ): chênh lệch tiến độ = EV – PV

CPI : EV / AC : giống cái trên => tương đối %

SPI : EV /PV

EAC = BAC / CPI (buget / CPI) ước lượng chi phí

EDAC = DAC /SPI (Duration / SPI) ước lượng thời gian

VAC : chênh lệch khi hoàn thành = BAC – EAC

ETC : Ước lượng thời gian hoàn thành = EAC – AC

Over the budget , on the budget , under the budget

Ahead of schedule , on the schedule , behind the schedule

EV = $2.3 million; PV = $2.8 million; AC = $2.1 million

Calculate and give your comments (current status, forecast and

recommended adjustment) on the schedule and cost performance of the
project
Request 5 (20%): Assuming that your project was reported with the following
status:

AC = $120,000;

PV = $125,000;

CV = -10,000.

Calculate and give your comments (current status, forecast and

recommended adjustment) on the schedule and cost performance of the
project

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 need 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
Request 5 (20%): provide at least 5 main cost items, description and
estimation for each cost item to complete the project. The estimation should
be in effort (man-days, man-hours)

1. Requirement Analysis:
Analyze and gather business and system requirements.
Estimation: 5 man-days.

2. UI/UX Design:
Design the website layout and the affiliate dashboard.
Estimation: 6 man-days.

3. Frontend Development:
Develop the customer-facing website and affiliate dashboard interfaces.
Estimation: 12 man-days.

4. Backend Development:
Develop APIs, database structures, and implement affiliate business logic.
Estimation: 14 man-days.

5. Testing and Deployment:

Perform unit tests, integration tests, and deploy the website to the
production environment.
Estimation: 8 man-days.

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 MH

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. Internal Failure Costs

4.1. Rework Due to Defects Found in Testing

 Description: Performing rework and adjustments after defects are

found during internal testing.

 Estimation: 60 man-hours (e.g., 3 hours per defect fix, with an

estimated 20 defects found during internal testing).