Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
Software Project Management Plan
Remind Me
Software Development Project for Assisting People with Medication Use
Author: Team Hedgehog
Date: 9/4/2013
Team Hedgehog Members
Alan Vo
Brandt Jones
Chris Kaufman
Jeff Hertzing
Josh Murphy
Keegan Reap
Ken Nakano
Kevin Lin
Kylie Kniep
Michael Bond
Rotan Bosson
Sami Bouaazzi
Tej Gidvani
Thomas Hagos
Team Website
http://utdallas.edu/~kbk090020/
Change History
1
Software Project Management Plan
Remind Me
Version
1.0
Date
9/30/2013
Version 1.0
Date: 9/30/2013
Author
Michael Bond
Description of Changes
Initial Draft
Table of Contents
1. Project Scope Statement
1.1 Project Objective
1.2 Description of Product
1.3 Project Deliverables
1.4 Milestones
1.5 Technical Requirements
1.6 Limits and Exclusions
1.7 Customer Review
2. Project Resource and Schedule
2.1 Resources
2.2 Schedule of Deliverables and Milestones
3. Risk Management
3.1 Probability
3.2 Impact
4. Dependencies & Constraints
4.1 Dependencies
4.2 Constraints
5. Communication Plan
6. Phase Percentage Breakdown Justification
Appendix
1. Project Scope Statement
2
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
1.1 Project Objective
To develop a software solution through a smartphone application within three months that will
assist people with medication use.
1.2 Description of Product
The main purpose of Remind Me is to help its users, which includes the person with difficulty
remembering when to take medication, how much medication they need to take, and when to
refill prescriptions. The software described within this document is an application that can be run
on many of today’s popular smartphones, tablets, and devices running the Google Android
operating system.
1.3 Project Deliverables
●
●
●
Remind Me software (includes installation and configuration that meet minimum system
requirements).
User manual for administrators (digital and print).
User manual for end users (digital).
1.4 Milestones
1.
2.
3.
4.
5.
6.
Requirements Gathered and Project Feasibility Studied - 5/20
Project Plan Reviewed and Signed off by Stakeholder - 6/18
Design Phase Completed - 7/23
Implementation Phase Completed - 9/26
Validation and Integration Testing Completed - 10/21
Product Delivered and End User Training Completed - 10/29
1.5 Technical Requirements
1. End user product must be compatible and fully operational with Android smartphones &
devices.
2. User interface must be touch-friendly.
1.6 Limits and Exclusions
1. Product will operate and perform duties as outlined in the customer’s requirements.
2. Customer will be responsible for any additional costs that run over the agreed budget
due to customer changes to the requirements or customer enhancement requests.
3. The customer must provide the server environment in the cloud services of their choice.
4. Server environment must meet the minimum system requirements for a successful
deployment and operation of the product.
1.7 Customer Review
●
Dr. Lawrence Chung - Professor
3
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
2. Project Resource and Schedule
2.1 Resources
2.1.1 People
4
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
The team will work on this project contain the following personnel. Most of the team members
will be performing multiple jobs.
●
●
●
●
●
Software project manager.
Two software requirement and specification analysts.
Four software unit programmers.
Two software verification and validation testers.
One software product trainer.
2.1.2 Hardware / Equipment
All Android hardware will be emulated with an Android Virtual Machine
2.1.3 Software
● Operating System: Android
● Eclipse
● Android SDK
2.2 Schedule of Deliverables and Milestones
Phases
Phase
Starting
Date
Phase
Completion
Date
Feasibility
TBD
TBD
Deliverable
Deliverables
Completion
date
Requirement
TBD
Milestone
Analysis
Specification
TBD
TBD
Project Plan
TBD
Milestone
Architecture Design
Modules Design
Design
TBD
TBD
Document Design
TBD
Milestone
Unit Coding 1
Unit Coding 2
Implementation
TBD
TBD
Unit Coding 3
TBD
Unit Testing 1
Unit Testing 2
5
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
Unit Testing 3
Coding 4
Milestone
Integration
Validation
TBD
TBD
Milestone
Training
Delivery
TBD
TBD
Milestone
TBD
TBD
3. Risk Management
Identifying and mitigating any possible risks with the project is necessary to ensure the project is
completed within the given time. All possible risks are outlined and managed by the project
team and management. Each major risk will be monitored and updated throughout the life of
the project. Monthly assessments of each risk will be included in the monthly status reports(see
Communications Plan). The probability and impact of occurrence for identified risks are as
follows:
6
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
3.1 Probability
●
●
●
High - Greater than 70% probability of occurrence
Medium - Between 30% and 70% probability of occurrence
Low - Below 30% probability of occurrence
3.2 Impact
●
●
●
High - Risk has the potential to greatly impact the project cost, schedule or performance
Medium - Risk has the potential to slightly impact the project cost, schedule or
performance
Low - Risk has very little impact to project cost, schedule or performance
Risk
Impact
Probability Mitigation Strategy
Estimated Project
Schedule
High
High
Project timeline with monthly
status meetings
Scope Creep
Medium
Medium
Stakeholder review meetings
Cost Estimates
Low
Low
Project plan, stakeholder review
Timeline Estimates
Medium
Medium
Weekly meetings by workgroup,
Monthly status reports
Workgroup
Availability
High
Medium
Project timeline
Workgroup project
experience
Medium
Medium
Communication plan, weekly
meetings
External
components
Low
Low
Review of suppliers
Requirements do
not match
developed
functions
Medium
Medium
Prototyping, weekly meetings
User interfaces do
not fit stakeholder
needs
Medium
Medium
Prototyping, User stories and
cases
7
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
4. Dependencies & Constraints (WIP)
4.1 Dependencies
●
TBD
4.2 Constraints
Project Completion Time:
Software development must be completed, delivered to the customer, and user training
completed within six months from the project start date of May 1, 2013.
8
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
Project Team Staffing and Availability:
● TBD
5. Communication Plan (WIP)
Communicating information about the project is crucial for the project to be successful. Due to
the short development period, efficient communication is necessary to complete the software on
schedule. The workgroup will maintain a schedule of weekly meetings to ensure all tasks are
completed on time. The stakeholders will be kept informed of the progress through their
representatives on the workgroup.
Audience:
Workgroup
Management
Stakeholders
The following table lists the types of communication that will occur during the length of this
project.
Communicatio
n Type
Objective
Mediu
m
Frequenc
y
Audience
Owner
Deliverabl
e
Tool/Forma
t
First Meeting
Introduce
team and
project. Go
-In
Person
Once
-Workgroup
-Management
-Stakeholders
Project
Manager
-Agenda
-Meeting
minutes
MS Word
9
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
over project
objectives
and
approach.
Initial Team
Meeting
Review
development
plan. Assign
roles.
-In
Person
Once
-Workgroup
Team
Leader
-Agenda
-Meeting
Minutes
-Project
Schedule
MS Word
Weekly Team
Meeting
Review
status of the
project
-In
Person
Weekly
-Workgroup
Team
Leader
-Agenda
-Meeting
Minutes
-Project
Schedule
MS Word
Monthly Project
Meeting
Report status
of project to
management
-In
Person
Monthly
-Management
Project
Manager
-Slide
Updates
-Project
Schedule
MS
Word/Power
point
UI Design
Meeting
Review UI
and code
updates
-In
person
Monthly
-Workgroup
Team
Leader
-Agenda
-Meeting
Minutes
MS Word
Project Status
Report
current status
of project.
-Email
Monthly
-Workgroup
-Stakeholders
-Management
Project
Manager
-Status
report
-Project
Schedule
MS Word
Stakeholders will be given time to review content and provide feedback. Notes will be taken of
all stakeholder feedback. The following table is a schedule for stakeholder review dates and is
subject to change.
Communication
Type
Objective
Deliverable
Development
Review
Walk stakeholders through the design of -Slide updates
the software.
-Project
documents
7/23/13
Pretesting Review
Walk stakeholders through visuals of UI. -Slide updates
-Project
documents
9/27/13
Post testing Review
Present stakeholders with testing
results. Give live demo of software.
10/22/13
-Slide updates
-Project
documents
Date
10
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
6. Phase Percentage Breakdown Justification (WIP)
This software project is considerably small based on its scope and features descriptions. And
from our risk management analysis, the scope creeping rate is fairly low. Therefore, the
requirement and specification analysis phase should take small percentage of the overall
development process.
We will spend over 50% of the time to work on the software system design and implementation.
We will be performing unit coding in parallel, however we can not implement unit testing in the
same manner due to the availability of our workstation.
The validation phase is approximately 3 weeks. It is sufficient to integrate the project, and make
sure it meets the requirement and specification.
Finally, the delivery phase will take one week. It is limited by the availability of our assigned
trainer.
The following table shows the percentage distribution of each phase.
Note: Total duration 6 months, 128 workdays.
Phases
Duration
(approx. in days)
Percentage
Feasibility
13
11%
11
Software Project Management Plan
Remind Me
Version 1.0
Date: 9/30/2013
Specification
20
16%
Design
23
19%
Implementation
46
37%
Validation
16
13%
Delivery
5
4%
12