f I,;!
' ,
• I
Software Project
Management Plan:
The MSG Foundation
Case Study
The plan presented here is for development of the MSG product by a small software
organization consisting of three individuals: Almaviva. the owner of the company. and two
software engineers. Bartolo and Cherubini.
1 Overview.
1.1 Project Summary.
1.1.1 Purpose, Scope, and Objectives.
The objective of this project is to develop a software product that will assist the Martha Stockton Greengage (MSG) Foundation in making
decisions regarding home mortgages for married couples. The product will allow the client
to add. modify, and delete information regarding the Foundation's investments. operating expenses, and individual mortgage information. The product will perform the required
calculations in these areas and produce reports listing investments. mortgages. and weekly
operating expenses.
1.1.2 Assumptions
and Constraints.
The deadline must be met.
The budget constraint must be met.
The product must be reliable.
Constraints include the following:
• I ,
I I It'
Software Project Management
Plan: The MSG Foundation
, , I
Case Study
The architecture must be open so that additional functionality may be added later.
The product must be user-friendly.
1.1.3 Project Deliverables.
The complete product, including user manual, will be delivered 10 weeks after the project commences.
1.1.4 Schedule and Budget Summary.
The duration, personnel requirements, and budget
of each workftow are as follows:
Requirements workftow (I week, two team members, $3740)
Analysis workftow (2 weeks, two team members, $7480)
Design workftow (2 weeks, two team members, $7480)
workftow (3 weeks, three team members, $16,830)
Testing workftow (2 weeks, three team members, $11,220)
The total development time is 10 weeks, and the total internal cost is $46,750.
1.2 Evolution of the Project Management Plan.
All changes in the project management plan must be agreed to by Almaviva before they are implemented. All changes
should be documented in order to keep the project management plan correct and up
to date.
2 Reference Materials.
All artifacts will conform to the company's programming, documentation, and testing standards.
3 Definitions and Acronyms.
Stockton Greengage; the MSG Founda-
tion is our client.
4 Project Organization.
. and two
4.1 External Interfaces.
All the work on this project will be performed by Almaviva,
Bartolo, and Cherubini. Almaviva will meet weekly with the client to report progress and
discuss possible changes and modifications.
4.2 Internal Structure.
The development team consists of Almaviva (owner), Bartolo,
and Cherubini.
)p a softn making
the client
4.3 Roles and Responsibilities.
Bartolo and Cherubini will perform the design workftow.
Almaviva will implement the class definitions and report artifacts, Bartolo will construct
the artifacts to handle investments and operating expenses, and Cherubini will develop the
artifacts that handle mortgages. Each member is responsible for the quality of the artifacts
he or she produces. Almaviva will oversee integration and the overall quality of the software
product and will liaise with the client.
;. operat: required
.d weekly
5 Managerial Process Plans.
5.1 Start-up Plan.
5.1.1 Estimation Plan.
As previously stated, the total development time is estimated to
be 10 weeks and the total internal cost to be $46,750. These figures were obtained by expert
judgment by analogy, that is, by comparison with similar projects.
, I I
• I
APPENDIX E Software Project Management
Plan: The MSG Foundation
Case Study
5.1.2 Staffing Plan.
Almaviva is needed for the entire 10 weeks, for the first 5 weeks
in only a managerial capacity and the second 5 weeks as both manager and programmer.
Bartolo and Cherubini are needed for the entire 10 weeks, for the first 5 weeks as systems
analysts and designers, and for the second 5 weeks as programmers and testers.
5.1.3 Resource Acquisition Plan.
All necessary hardware, software, and CASE tools
for the project are already available. The product will be delivered to the MSG Foundation
installed on a desktop computer that will be leased from our usual supplier.
5.1.4 Project Staff Training Plan.
No additional staff training is needed for this project.
5.2 Work Plan.
5.2.1-2 Work Activities and Schedule Allocation.
Week I.
(Completed) Met with client, and determined requirements artifacts.
Inspected requirements artifacts.
Weeks 2, 3.
(Completed) Produced analysis artifacts, and inspected analysis artifacts. Showed artifacts to client, who approved them. Produced
software project management plan, and inspected software project
management plan.
Weeks 4,5.
Produce design artifacts, inspect design artifacts.
Weeks 6-10.
Implementation and inspection of each class, unit testing and documentation, integration of each class, integration testing, product testing,
and documentation inspection.
5.2.3 Resource Allocation.
The three team members will work separately on their assigned artifacts. Almaviva's assigned role will be to monitor the daily progress of the
other two, oversee implementation, be responsible for overall quality, and interact with
the client. Team members will meet at the end of each day and discuss probl~ms and
progress. Formal meetings with the client will be held at the end of each week to report progress and determine if any changes need to be made. Almaviva will ensure that
schedule and budget requirements are met. Risk management will also be Almaviva's
Minimizing faults and maximizing user-friendliness will be Almaviva's top priorities.
Almaviva has overall responsibility for all documentation and has to ensure that it is up to
5.2.4 Budget Allocation.
The budget for each workftow is as follows:
Requirements workftow
Analysis workftow
Design workftow
Implementation workftow
Testing workftow
5.3 Control Plan.
$ 3,740
Any major changes that affect the milestones or the budget have to
be approved by Almaviva and documented. No outside quality assurance personnel are
5 weeks
I , I
Software Project Management
Plan: The MSG Foundation
Case Study
involved. The benefits of having someone other than the individual who carried out the development task do the testing will be accomplished by each person testing another person's
work products.
Almaviva will be responsible for ensuring that the project is completed on time and
within budget. This will be accomplished through daily meetings with the team members .
At each meeting, Bartolo and Cherubini will present the day's progress and problems. AImaviva will determine whether they are progressing as expected and whether they are following the specification document and the project management plan. Any major problems
faced by the team members will immediately be reported to Almaviva.
gram mer.
> systems
•SE tools
s project.
5.4 Risk Management
The risk factors and the tracking mechanisms are as follows.
There is no existing product with which the new product can be compared. Accordingly,
it will not be possible to run the product in parallel with an existing one. Therefore, the
product should be subjected to extensive testing.
The client is assumed to be inexperienced with computers. Therefore, special attention
should be paid to the analysis workflow and communication with the client. The product
has to be made as user-friendly as possible.
Because of the ever-present possibility of a major design fault, extensive testing will be
performed during the design workflow. Also, each of the team members will initially test
his or her own code and then test the code of another member. Almaviva will be responsible
for integration testing and in charge of product testing.
The information must meet the specified storage requirements and response times. This
should not be a major problem because of the small size of the product, but it will be monitored by Almaviva throughout development.
There is a slim chance of hardware failure, in which case another machine will be leased.
If there is a fault in the compiler, it will be replaced. These are covered in the warranties
received from the hardware and compiler suppliers.
s artilect
ocut testing,
their asss of the
ract with
[ems and
ek to resure that
5.5 Project Close-out Plan.
Not applicable here.
6 Tec/mical Process Plans.
6.1 Process Model.
The Unified Process will be used.
6.2 Methods, Tools, and Techniques.
The workftows will be performed in accordance
with the Unified Process. The product will be implemented in Java.
.t is up to
6.3 Infrastructure Plan. The product will be developed using ArgoUML running under
Linux on a personal computer.
6.4 Product Acceptance Plan. Acceptance of the product by our client will be achieved
by following the steps of the Unified Process.
7 Supporting Process Plan
7.1 Configuration
7.2 Testing Plan.
t have to
mnel are
7.3 Documentation
Process .
CVS will be used throughout for all artifacts.
The testing workftow of the Unified Process will be performed.
will be produced as specified in the Unified
Software Project Management
I ,
I I ,
Plan: The MSG Foundation
Case Study
7.4-5 Quality Assurance Plan and Reviews and Audits Plan. Bartolo and Cherubini
will test each other's code, and Almaviva will conduct integration testing. Extensive product testing will then be performed by all three.
7.6 Problem Resolution Plan. As stated in 5.3, any major problems faced by the team
members will immediately be reported to Almaviva.
7.7 Subcontractor Management Plan.
Not applicable here.
7.8 Process Improvement Plan.
All activities will be conducted in accord with the company plan to advance from CMM level 2 to level 3 within 2 years.
8 Additional Plans.
Additional components:
A password will be needed to use the product.
Training will be performed by Almaviva at time of delivery. Because the product is straightforward to use, I day should be sufficient for training. Almaviva will answer
questions at no cost for the first year of use.
Corrective maintenance will be performed by the team at no cost for a
period of 12 months. A separate contract wi 11be drawn up regarding enhancement.