PERSONAL MANAGEMENT APPLICATION
PROJECT MANAGEMENT PLAN
stakeholdermap.com
PROJECT MANAGEMENT PLAN
DOCUMENT CONTROL
DOCUMENT INFORMATION
Information
Document Id EXP-APP-2025-01
Document Owner Vo Huu Truong
Issue Date 30/05/2025
Last Saved Date 30/05/2025
File Name Personal-management-application.docx
DOCUMENT HISTORY
Version Issue Date Changes
Initial release, including feature list, architecture, and key
[1.0] 30/05/2025
requirements.
DOCUMENT APPROVALS
Role Name © Signature Date
Project Sponsor Nguyen Van A Văn a 30/05/2025
Project Review Group Tran Thi B Thị B 30/05/2025
Project Manager ©
Vo Huu Truong Hữu Trường 30/05/2025
stakeholdermap.com i
PROJECT MANAGEMENT PLAN
Quality Manager
Le Thi C Thị C 30/05/2025
(if applicable)
Procurement Manager
Vo Van D Văn D 30/05/2025
(if applicable)
Communications Manager
Nguyen Van D Văn D 30/05/2025
(if applicable)
Project Office Manager
Pham Nhat V Nhật V 30/05/2025
(if applicable)
stakeholdermap.com ii
PROJECT MANAGEMENT PLAN
Table of Contents
<PROJECT NAME> .................................................................................................... ERROR! BOOKMARK NOT DEFINED.
<PROJECT REFERENCE> ........................................................................................... ERROR! BOOKMARK NOT DEFINED.
PROJECT MANAGEMENT PLAN ..................................................................................................................... I
DOCUMENT CONTROL................................................................................................................................. I
DOCUMENT INFORMATION ....................................................................................................................................... I
DOCUMENT HISTORY .............................................................................................................................................. I
DOCUMENT APPROVALS ......................................................................................................................................... I
TEMPLATE GUIDE ....................................................................................... ERROR! BOOKMARK NOT DEFINED.
PROJECT LIFE CYCLE: ............................................................................................................................... 1
DEVELOPMENT APPROACHES: .................................................................................................................... 4
SUBSIDIARY MANAGEMENT PLANS: ............................................................................................................. 4
VARIANCE THRESHOLDS: ........................................................................................................................... 5
BASELINES: ............................................................................................................................................... 6
stakeholdermap.com iii
PROJECT MANAGEMENT PLAN
DOCUMENT USER GUIDE
This is a detailed guide to help you build a Project Management Plan for the
Personal Expense Management Application project. This is an application
development project on the Android platform, with the aim of helping users manage
their personal finances more effectively, conveniently and scientifically.
The application allows users to:
• Track daily income and expenses.
• Plan weekly and monthly budgets.
• View detailed financial reports to make appropriate decisions.
• Support a friendly, easy-to-use interface on Android phones.
1. Purpose of the document:
• Support the development team: Help members of the development team have a
detailed, scientific and comprehensive project management direction and plan.
Thereby, helping to divide work clearly and control progress better.
• Provide a standard structure: Helps ensure that all important elements are
identified and managed throughout the project development process, including
scope, schedule, cost, quality, risk and personnel.
Help stakeholders: Allow project participants (management, development, QA,
testers) to clearly understand their roles and responsibilities in each stage, thereby
coordinating effectively and minimizing project risks.
Ensure consistency and quality: Helps maintain uniformity and easily track the
project implementation process, supporting the final testing and acceptance process.
2. Project introduction:
Project name: Personal expense management application
Version: 1.0
Release date: 01/06/2025
stakeholdermap.com 1
PROJECT MANAGEMENT PLAN
Brief description: This is a personal finance management application that helps
users record and track income and expenses, plan budgets, and provide detailed
reports to help users make smart financial decisions.
Main features:
Tracking daily expenses, income, and bills
• Support users to record daily income and expenses such as salaries, bonuses,
living expenses, shopping, etc.
• Integrated electronic invoice entry feature, helping to store and manage invoices
easily, convenient for searching and paying.
Plan weekly and monthly expenses
• Allow users to set a budget for each week/month, manage spending categories by
type (food, entertainment, study, etc.).
• Automatically alert if spending exceeds the set budget.
View visual financial reports
• Integrate detailed income and expenditure reports in the form of charts (columns,
circles) and data tables.
• Support users to easily track spending trends and make reasonable adjustments to
financial plans.
Support multiple Android platforms
• The application is optimized to run smoothly on most Android devices.
• Friendly interface, easy to use, suitable for all users, from students to working
people.
Integrated security and data backup
• Support secure login with password or fingerprint.
• Integrated data backup and restore feature to avoid information loss
stakeholdermap.com 2
PROJECT MANAGEMENT PLAN
PROJECT LIFE CYCLE
.
Phase Key Activities Key Deliverables
Initiation - Identify key projects - Project Charter
- Analyze user needs - Project Proposal
- Allocate additional resources
Planning - Develop detailed project plan - Project Management Plan
(PMP)
- Define scope, schedule,
budget - Risk Management Plan
- Test Plan
Execution - Software development (code, - Alpha/Beta App Versions
UI/UX)
- Progress Reports
- Regular testing and validation
- User Manuals
- Functional refinement
Closure - Product acceptance - Project Summary Report
- Product deployment - Final Deliverables
- Project evaluation - Lessons Learned
Phase Reviews Entry Criteria Exit Criteria
Initiation - Review Project - Have preliminary - Project proposal
Initiation Documents user requirements approved
document
- Approve Initial Scope - Resources allocated
- Have planned
resources
Planning - Review project plan - Project initiation - Project management
document completed plan approved
- Identify project risks
and scope - Project team - Risks assessed
established
stakeholdermap.com 3
PROJECT MANAGEMENT PLAN
Execution - Evaluate - Approved project - Complete main
development progress management plan modules
- Check product - Resources available - Test report meets
quality requirements
Closure - Final product - Complete application - Complete main
evaluation version modules
- Lessons learned - Complete - Test report meets
evaluation documentation requirements
DEVELOPMENT APPROACHES:
Deliverable Development Approach
Application Interface (UI) Agile approach – Develop each screen in
sprints, get early user feedback.
Expense/income/bill tracking function Iterative approach – Build each major function,
test and improve through iterations.
Spending planning feature Agile approach – Prioritize development
according to backlog, update flexibly according
to feedback.
financial report Waterfall method – Collect requirements at the
beginning, analyze and build complete at the
end.
Deployment Iterative approach – Continuous testing and
optimization on real devices after each release
cycle.
SUBSIDIARY MANAGEMENT PLANS:
Name Comment
Scope The project scope includes developing an
Android application with features such as
expense tracking, budgeting, and financial
reporting.
Time The project is divided into 5 sprints, each lasting
2 weeks. Total duration: 10 weeks.
stakeholdermap.com 4
PROJECT MANAGEMENT PLAN
Cost Minimal cost since the project is developed by
students using free tools. Effort and time are the
main investments
Quality Unit and integration testing are performed in
each sprint. Each function is validated using a
predefined quality checklist
Resources Team includes 4 members: project manager,
lead developer, UI/UX designer, and tester.
Communications Weekly meetings via Google Meet. Progress
and tasks are managed using Trello and
updated through Google Sheets.
Risk Risks include delayed progress, lack of
technical expertise, and software bugs. Risk
mitigation strategies are planned.
Procurement No procurement needed. Open-source and free
tools like Android Studio and Firebase are used.
Stakeholder Key stakeholders include the supervising
lecturer, test users, and the development team.
Other Plans Post-demo plans include maintenance and
feature enhancement.
VARIANCE THRESHOLDS:
Document the allowable variances for each aspect of the project. Include the baseline from which
variances will be measured.
Scope Variance Threshold Scope Baseline Management
• The application must include core • Project scope is defined in the
features: income/expense tracking, bill requirements specification (Project
management, budgeting, and reporting. Charter).
• Acceptable variance: one non-critical • Any changes to the scope must be
feature (e.g., report sharing via social evaluated for impact and go through a
media) may be missing. change control process.
• Unacceptable variance: missing a core • Minor adjustments (e.g., UI
feature like transaction recording or improvements) may be accepted
summary reports. without formal change control.
stakeholdermap.com 5
PROJECT MANAGEMENT PLAN
Schedule Variance Threshold Schedule Baseline Management
• Total planned duration for the project is • Schedule will be monitored weekly.
12 weeks. • If variance exceeds warning thresholds,
a team meeting will be held to revise
• Acceptable variance: delay of up to 5% (≤ the plan.
4 working days). • Significant delays will require
reassessment of scope or reallocation
• Warning level: delay of 6–10% (5–8 of resources, and initiate the change
control process.
working days).
• Unacceptable variance: delay greater
than 10% triggers corrective action
Cost Variance Threshold Cost Baseline Management
• Total estimated budget is 100 million • Costs will be tracked across project
VND. phases (analysis, design, development,
testing).
• Acceptable variance: within ±5% of the
planned budget. • If variance exceeds warning thresholds,
a cost analysis report must be created
• Warning level: variance between ±6–10% with mitigation proposals (e.g., feature
requires investigation and documentation. reduction, tech changes).
• Unacceptable variance: variance greater • Major overruns require re-approval by
than ±10% will trigger corrective action. project stakeholders.
BASELINES:
Note: To be defined
stakeholdermap.com 6
