Request 1:
-Project Description Project Title: Tour Booking Website Project
-Purpose/Objectives: The purpose of the Tour Booking Website project is to develop an online
service platform that connects global travelers with a variety of accommodation options,
streamlining the booking process.
-Project Timeframe: The project is scheduled for completion within 6 months, from March 2024 to
September 2024.
-Project Milestones: Project Initiation (Week 1) Development of Core Features (Weeks 2-8)
Integration with Accommodation Providers (Weeks 9-16) Beta Testing and Feedback Incorporation
(Weeks 1-24) Launch and Marketing Campaign (Week 21-24)
-Other Project Constraints:
Cost: Budget is set at $400,000.
Resources: Team of 15, including developers, designers, marketers, and support staff.
Regulations: Compliance with international data privacy laws and accommodation regulations.
-Key objectives include: Providing a reliable, user-friendly platform for travelers to browse and book
accommodations. Integrating with local and global accommodation providers to offer a wide range of
choices. Implementing features that enhance user experience such as reviews, ratings, and easy
navigation. Ensuring secure and fast booking transactions.
Success Criteria: At least 80% customer satisfaction rate in post-booking surveys. Achieve 50,000
bookings within the first three months post-launch. System uptime of 90%, ensuring reliability and
accessibility. Maintain transaction security with zero breaches reported.
-Customer/Sponsor: The project is internally funded by a consortium of venture capitalists interested in
expanding digital solutions in the travel industry.
Request 2: 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 l-Inform)
-Responsibility Assignment Matrix (RAM)
+Requirements Gathering Accountable:
+Project Manager Responsible: Lead Developer
+Consulted: UI/UX Designer, Marketing
+Specialist Informed: Security Analyst Core
-Platform Development
Responsible: Lead Developer
Consulted: Project Manager, UI/UX Designer
-Accommodation Provider Integration
Responsible: Integration
Specialist Consulted: Lead Developer, Legal Advisor Beta
-Testing and Feedback
Responsible: QA Engineer, UI/UX Designer
Consulted: Project Manager Launch and Marketing Campaign
Accountable: Marketing Manager
Responsible: Marketing
Specialist Consulted: Project Manager Security
-Implementation Accountable: Security Analyst
Consulted: Lead Developer Performance Monitoring
Responsible: IT Support
Specialist Consulted: Project Manager
-Customer Support System
Responsible: Customer Support Manager
Consulted: Marketing Specialist Platform Updates and Maintenance
Accountable: Lead Developer
Responsible: IT Support Specialist Project Close-Out and Review
Accountable: Project Manager
Consulted: All Team Leads
Request 3: 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.
-Quality Assurance and Control Activities Code Review (QA)
1.Purpose: Ensure the code is clean, efficient, and error-free.
2.When How: Conducted weekly by the Lead Developer.
-Usability Testing (QC)
1.Purpose: Ensure the platform is intuitive and meets user expectations.
2.When,How: Conducted at the end of each development sprint with a group of beta testers.
-Security Audits (QA)
1.Purpose: Verify compliance with security standards to protect user data.
2.When,How: Monthly audits by the Security Analyst and external consultants.
-Load Testing (QC)
1.Purpose: Ensure the platform can handle the expected number of users and transactions.
2.When,How: Before launch and during low-traffic periods post-launch.
-Customer Feedback Analysis (QA)
1.Purpose: Continuously improve the platform based on user feedback.
2.When,How: Ongoing, with quarterly reviews to implement necessary changes.
Request 4: 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.
-Project Phases and Deliverables
-Phase 1: Project Planning
1.Deliverable 1: Project Charter
2.Deliverable 2: Stakeholder Analysis
-Phase 2: Development
1.Deliverable 1: Functional Requirements Document
2.Deliverable 2: Core Platform Codebase
-Phase 3: Integration and Testing
1.Deliverable 1: Integration Completion Report
2.Deliverable 2: Beta Test Feedback Summary
-Phase 4: Launch and Evaluation
1.Deliverable 1: Marketing and Launch Strategy
2.Deliverable 2: Post-Launch Performance Report
Request 5: 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).
-Cost Estimation Platform Development
1.Description: Labor cost for developers and designers.
2.Estimation: 150 man-days
-Marketing and Launch
1.Description: Advertising, promotional materials, and launch event.
2.Estimation: 40 man-days
-Security Measures
1.Description: Security software and consultant fees.
2.Estimation: 20 man-days
2.Effort: $30,000
-Infrastructure
1.Description: Servers, databases, and necessary software licenses.
2.Estimation: Ongoing
-Customer Support Setup
1.Description: Training and implementation of customer support tools.
2.Estimation: 30 man-days
------------------------------------------------------------------------------------------------------------------------------------------
Request 5.6: 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.
Roles and Responsibilities:
1.Project Manager
-Responsibility 1: Oversee project planning and scheduling.
-Responsibility 2: Ensure compliance with budget and timelines.
2.Frontend Developer
-Responsibility 1: Develop user-friendly interface screens and features.
-Responsibility 2: Collaborate on implementing responsive designs.
3.Backend Developer
-Responsibility 1: Implement secure booking transaction logic.
-Responsibility 2: Integrate APIs for global and local accommodation providers.
4.Quality Assurance Engineer
-Responsibility 1: Perform functional and security testing.
-Responsibility 2: Manage beta testing and ensure feedback incorporation.
5.Marketing Specialist
-Responsibility 1: Develop and execute the launch campaign.
-Responsibility 2: Analyze user feedback and market trends post-launch.
------------
Request 6 : 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.
In-Scope:
1.User account creation and management.
2. Accommodation search and filtering functionality.
3.Secure booking and payment processing.
4.Review and ratings feature.
5.Integration with global providers' APIs.
Out-of-Scope:
1Mobile App Development: Only a web platform will be delivered.
2 Flight or Transport Booking Services: Limited to accommodation booking.
3 Custom Analytics Dashboard: Only standard reporting tools
4 Social Media Integration: No sharing of bookings or reviews to social media.
5 Tour and Activity Booking: Excludes bundling with activities.
6 Custom Review Moderation Tool: Only basic review flagging available.
7 24/7 Live Support: Only email and ticket-based support.
8 Offline Booking Support: Requires internet connectivity.
9 AI Chatbots: No advanced AI-based interactions.
10 Integration with Third-Party Rewards Programs: No loyalty systems.
---------
Request 7 (20%): determine at least 10 activities and relevant relationships (FS, SS, SF, FF) among them
to complete one of the project deliverables Deliverable: Secure Booking Module
1.Design user interface screens (SS).
2 Develop booking logic (FS).
3 Integrate payment gateway API (FS).
4 Implement transaction encryption (FF).
5 Perform unit testing (SF).
6.Conduct user testing (FS).
7.Fix bugs reported during testing (FF).
8.Finalize the booking module (SS).
9Deploy module to staging (FS).
10Review and approval by stakeholders (FS).
--------------------
Request 8: create the project WBS in bullet format with following 4 levels
1.Phase 1: Initiation
Iteration 1: Planning
Project Charter,Stakeholder Register, Budget Plan
2.Phase 2: Development
Iteration 2: Core Features
Booking Module :Search Interface ,Booking Logic//Reviews and Ratings: UI for Reviews :Moderation
Functions
3.Phase 3: Testing
Iteration 3: Beta Testing
User Testing Report ,Bug Fix Reports, Final Feedback Integration
4.Phase 4: Launch
Iteration 4: Deployment
Final Documentation ,Release Notes, Launch Marketing Campaign, Live System Monitoring
---------
Request 9: 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 - mitigation plan
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, add buffer for task
-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
------------
Request 10: Identity 3 stakeholders and decide (with relevant reasons) if they are: High power or low
power, High interest or low interest; Power interest grid
1, Global Accommodation Providers
Power: High Interest, High Status: Supportive Strategy: Engage actively through regular updates.
2, End Users (Travelers)
Power: Low Interest, HighStatus: Neutral Strategy: Inform through marketing and feedback chanels.
3,Investors Power, High Interest: Low Status: Leading Strategy: Provide concise periodic updates on
milestones.
-------------
Request 11: Go back to the three stakeholders you identified in the request 8. 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.
Communication Plan for Stakeholders( KẾ HOẠCH TRUYỀN THÔNG BÊN LIÊN QUAN)
1Global Accommodation Providers
-Information: Updates on platform performance, feature developments, and booking trends.
-Purpose: To keep providers informed and engaged, ensuring smooth collaboration and alignment with
the project’s goals.
-Frequency: Regular updates (monthly or quarterly) through newsletters, virtual meetings, and
performance dashboards.
-Method/Format: Email newsletters, online dashboards, and quarterly virtual meetings.
-Responsible: Product Manager, Partnership Manager.
-Review By: Operations Team, Project Sponsor.
2.End Users (Travelers)
-Information: Information about platform enhancements, promotions, and user feedback opportunities.
-Purpose: To keep travelers informed about new features and ensure they are engaged with the
platform.
-Frequency: Regular updates through marketing emails, social media posts, and in-app notifications.
-Method/Format: Email, social media, in-app notifications.
-Responsible: Marketing Manager, Customer Service Team.
-Review By: Marketing Director, UX Lead.
3.Investors
-Information: Financial performance, project milestones, and risk mitigation strategies.
-Purpose: To keep investors informed about the project’s financial health and overall progress.
-Frequency: Periodic updates, typically quarterly, with an annual in-person meeting for high-level
updates.
-Method/Format: Financial reports, quarterly updates, and annual meetings.
-Responsible: CFO, Project Manager.
-Review By: Board of Directors, CEO.
------------
------------------------------
Request 14 : what type of organization(Tổ chức) you think the project 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 6-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
6-month timeframe.
