ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Software Project Management Plan
Project: PS Movers e-commerce website
December 13, 2013
Version 1.2
Monika Saini
Tejinder Kaur
Yousef Alqahtani
1
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Change History
Version
Release Date
Change
SPMP Version 1.1
13/12/2013
Monika Saini
SPMP Version 1.2
20/12/2013
Monika Saini
Fig1: Change History
2
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Table of Content
Contents
......................................................................................................................................................................................................... 1
Software Project Management Plan ................................................................................................................................. 1
Project: PS Movers e-commerce website....................................................................................................................... 1
Change History ......................................................................................................................................................................... 2
Table of Content .................................................................................................................................................................. 3
Table of Figures ........................................................................................................................................................................ 8
1.
Overview............................................................................................................................................................................ 9
2.
References......................................................................................................................................................................... 9
3.
Documentation ............................................................................................................................................................... 9
3.1
Business Case: A structured proposal for business change that is justified in terms of costs
and benefits................................................................................................................................................................................ 9
3.2 Project Charter: ............................................................................................................................................................ 9
3.3 Team Contract: ........................................................................................................................................................... 10
3.4 Scope Statement: ....................................................................................................................................................... 10
3.5 Communication Management Plan: ................................................................................................................... 10
3.6 Work Breakdown Structure (WBS): .................................................................................................................. 10
3.7 Quality Assurance Plan (QAP): ............................................................................................................................ 10
3.8 Risk Management Plan (RMP): ............................................................................................................................ 10
3.9 Status Report: ............................................................................................................................................................. 10
3.10 Milestone Report: ................................................................................................................................................... 10
3.11 Final Project Presentation (FPP): .................................................................................................................... 10
3.12 Final Project Report (FPR): ................................................................................................................................ 10
4.
Definition/ Acronyms ................................................................................................................................................ 11
4.1 PMP- Project Management Plan .......................................................................................................................... 11
4.2 Blog.................................................................................................................................................................................. 11
4.3 WBS- Work Breakdown Structure ..................................................................................................................... 11
4.4 Project ............................................................................................................................................................................ 11
4.5 Scope- ............................................................................................................................................................................. 11
4.6 SDLC- .............................................................................................................................................................................. 11
3
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
4.7 PM- .................................................................................................................................................................................. 11
4.8 SPMP- ............................................................................................................................................................................. 11
4.9 QAM................................................................................................................................................................................. 11
4.10 DBA- ............................................................................................................................................................................. 11
4.11SRS- ................................................................................................................................................................................ 11
4.12 WAMP- ........................................................................................................................................................................ 11
4.13 PPT- .............................................................................................................................................................................. 11
4.14 MySQL- ........................................................................................................................................................................ 11
4.15 PHP-.............................................................................................................................................................................. 11
4.16 HTML- .......................................................................................................................................................................... 11
4.17 XML- ............................................................................................................................................................................. 11
4.18 CSS- ............................................................................................................................................................................... 11
5.
Elements of the software project management plan .................................................................................... 12
5.1 Project Name:................................................................................................................................................................... 12
5.2 Project Overview:........................................................................................................................................................... 12
5.3 Project Purpose:......................................................................................................................................................... 12
5.4 Project Description:.................................................................................................................................................. 13
5.5 Client Information: ................................................................................................................................................... 13
5.6 Project Team: (Internal Structure) .................................................................................................................... 13
5.7 Project Deliverable: ..................................................................................... Error! Bookmark not defined.
5.8 References:................................................................................................................................................................... 14
No. ........................................................................................................................................................................................... 14
Documents ......................................................................................................................................................................... 14
References ......................................................................................................................................................................... 14
Work Break down Structure ........................................................................................................................................ 14
4. .............................................................................................................................................................................................. 14
Gantt chart ........................................................................................................................................................................... 14
Fig3. Document Referencing ........................................................................................................................................ 14
5.9 Assumptions:............................................................................................................................................................... 14
6. Definitions....................................................................................................................................................................... 15
6.1
Project Organization: ........................................................................................................................................ 15
6.1.1
Introduction:............................................................................................................................................... 15
4
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
6.2 Process Model:............................................................................................................................................................ 15
6.3 Organisational Structure: ....................................................................................................................................... 17
6.4 Roles and Responsibilities: ................................................................................................................................... 18
6.4.3 Tester (Tejinder Kaur).................................................................................................................................... 18
6.4.4 Developer (Monika Saini).............................................................................................................................. 19
6.4.5 Designer (Yousef Alqahtani) ........................................................................................................................ 19
6.4.6 DBA (Yousef Alqahtani) ................................................................................................................................. 20
6.4.7 Documenter (Monika, Tejinder, Yousef Alqahtani) ............................................................................ 20
6.4.8 Researcher (Monika, Tejinder, Yousef Alqahtani) .............................................................................. 20
6.5 Team Rules and Processes: ................................................................................................................................... 20
7. RISK MANAGEMENT ....................................................................................................................................................... 20
7.1 Introduction................................................................................................................................................................. 20
7.2Risk management plan ............................................................................................................................................. 21
7.2.1 Security risks for Users ....................................................................................................................................... 21
7.2.2 New risks and Risk Management Chart........................................................................................................ 22
8. TECHNICAL PROCESS ..................................................................................................................................................... 23
8.1Process Model .............................................................................................................................................................. 23
8.2 Methods, Tools, and Techniques ......................................................................................................................... 23
Tools and technologies below can be used for the project. ........................................................................ 23
8.2.1Tools ............................................................................................................................................................................. 23
8.2.1.1Desktop Development .................................................................................................................................. 23
8.2.2 Project Management............................................................................................................................................. 23
8.2.3 Programming/Core Development .................................................................................................................. 23
8.3 Online Deployment ................................................................................................................................................... 24
8.4Document distribution ............................................................................................................................................. 24
9.1Control Plan ....................................................................................................................................................................... 24
9.1.1 Requirement control plan .................................................................................................................................. 24
9.2 Scheduler Plan ............................................................................................................................................................ 24
9.3 Reporting plan ............................................................................................................................................................ 24
9.4 Matrix Collection Plan ............................................................................................................................................. 25
10.0 Infrastructure Plan...................................................................................................................................................... 25
11.0 File Naming Conventions ......................................................................................................................................... 25
5
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
12.0 Backup Procedure ....................................................................................................................................................... 25
12.1 External Hard Drive ............................................................................................................................................... 25
12.2 Dropbox ...................................................................................................................................................................... 25
13.0 TESTING PROCEDURES ............................................................................................................................................ 25
13.1 Testing Team ............................................................................................................................................................ 26
13.2 Testing Area .............................................................................................................................................................. 26
13.3 Website Testing ....................................................................................................................................................... 26
13.4 Database Testing..................................................................................................................................................... 26
13.5 Software Testing ..................................................................................................................................................... 26
14.0 Support Process Plan ................................................................................................................................................. 27
14.1.1 Configuration Management Plan .................................................................................................................. 27
14.1.2 Controlling Releases .......................................................................................................................................... 27
14.1.3 Versioning .............................................................................................................................................................. 27
15.0 Status Reporting and Change Requests.............................................................................................................. 27
15.1 Evaluation .................................................................................................................................................................. 28
15.2 Notification Changes ............................................................................................................................................. 28
16.0 Validation and Verification Plan............................................................................................................................ 28
16.1 Peer Review .............................................................................................................................................................. 28
16.2 Supervisor Review ................................................................................................................................................. 28
16.3 Milestone Review.................................................................................................................................................... 29
16.4 Prototyping ............................................................................................................................................................... 29
17.0 Documentation Plan ................................................................................................................................................... 29
17.1 Deliverable documents......................................................................................................................................... 29
17.2 Non-deliverable ....................................................................................................................................................... 30
17.3 Versioning Standards ............................................................................................................................................ 30
18. Quality Assurance Plan (QAP) .................................................................................................................................. 30
18.1 Reviews and Audit.................................................................................................................................................. 31
18.2 Problem Resolution Plan ..................................................................................................................................... 31
18.3 Problem Prioritizing .............................................................................................................................................. 31
18.4 Budget Allocation Plan ......................................................................................................................................... 31
18.5 Decision Making Plan ............................................................................................................................................ 31
Refer to Annex I ...................................................................................................................................................................... 32
6
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Refer to Annex II .................................................................................................................................................................... 35
Refer to Annex III................................................................................................................................................................... 37
Refer to Annex IV ................................................................................................................................................................... 40
Refer to Annex V .................................................................................................................................................................... 41
Refer to Annex VI ................................................................................................................................................................... 42
Refer to Annex VII ................................................................................................................................................................. 44
Refer to Annex VIII ................................................................................................................................................................ 46
Refer to Annex IX ................................................................................................................................................................... 48
Refer to Annex X..................................................................................................................................................................... 50
Refer to Annex XI ................................................................................................................................................................... 53
Bibliography ............................................................................................................................................................................ 56
7
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Table of Figures
Fig No.
Description
Page No.
1.
Change History
2
2.
Internal Structure
11
3.
Document Referencing
12
4.
Water Fall Methodology
14
5.
Organisational Chart
15
6.
Role & Responsibilities
16
7.
Risk Management Chart
22
8.
Deliverable Documents
30
8
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
1. Overview
1.1 Purpose of SPMP:
The main goal of behind Software Project Management Plan (SPMP) is plan and manage entire
project in terms of three dimensional constraints such as time, scope and budget. SPMP provide
the detail idea about the starting time and finishing time of project, financial plan for the project
and covers the entire scope of the project. Through planning and managing these three dimensional
constraint of the project we can start our project according to the time and close it. So the main
purpose of the SPMP is to provide the agenda for the project.
2. References
C. McConnell, Steven (IEEE 1987). Software Project Management Plan (SPMP)
Template Retrieved on 9 December 2013, from
http://users.csc.calpoly.edu/~jdalbey/205/Mgmt/SPMP.html
IEEE Computer Society (1063-2001). IEEE Standard for Software User Documentation.
Retrieved on 11 December 2013, from http://home.arcor.de/ca.be/images/1063-2001.pdf
Example IEEE software project management plan (SPMP). (n.d.) Retrieved on 13
December 2013, from
http://www.site.uottawa.ca/~shervin/courses/seg4105/project/SPMP.html
3. Documentation
3.1 Business Case: A structured proposal for business change that is justified in terms
of costs and benefits.
3.2 Project Charter: A document that formally recognises the existence of the
project. The main purpose of project charter is to document:




Reasons why we chose this project
Objectives and constraints of the project
Identities of the main stakeholders
Items whether they are in-scope and out-of-scope
9
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani



High level risk management plan
Communication plan
Project benefits
3.3 Team Contract: A document that is signed by all the team members, defines the
requirements of the team member in terms of code of conduct and communication etcetera.
3.4 Scope Statement: A document used to develop and confirm a common
understanding of the project scope. First version is often called a preliminary scope statement.
3.5 Communication Management Plan: A document that guides the project
communication.
3.6 Work Breakdown Structure (WBS): It is a deliverable oriented decomposition
of a project into smaller components. It is also provides the necessary framework for detailed
budget plan and control along with providing guidance for plan development and control.
3.7 Quality Assurance Plan (QAP): It is a document tells outlining the procedures
and processes in place to ensure that the quality of the end product is at the desired level.
3.8 Risk Management Plan (RMP): A plan that documents the procedures for
managing risk all over the project.
3.9 Status Report: Reports that define where the project stands at a precise point in
time.
3.10 Milestone Report: Reports that outlines the major milestones in the project, and
their status at the point in time.
3.11 Final Project Presentation (FPP): A presentation to key stakeholders at the end
of the project, to determine the final project, and shows how the project went.
3.12 Final Project Report (FPR): A report that outlines how the whole project went,
and defines the end product.
Lessons Learned Report (LLR): Thoughtful statements written y project managers and their team
members to document important things they have learned from working on the project.
10
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
4. Definition/ Acronyms
4.1 PMP- Project Management Plan
4.2 Blog- Blog is an informational site published on the World Wide Web (WWW).A
weblog is a newsletter that is frequently updated and intended for general public consumption.
4.3 WBS- Work Breakdown Structure
4.4 Project- A temporary endeavour undertaken to create a unique product, service or
result
4.5 Scope- Entirely the work involved in creating the products of the project and the
processes used to create them.
4.6 SDLC- Software development life cycle
4.7 PM- Project Manager
4.8 SPMP- Software Project Management Plan
4.9 QAM- Quality Assurance Manager
4.10 DBA- Database Administrators
4.11SRS- Software Requirement Specification
4.12 WAMP- Windows Apache MySQL PHP
4.13 PPT- Power Point Presentations
4.14 MySQL- My Structured Query Language
4.15 PHP- PHP Hypertext Pre-processor
4.16 HTML- Hyper Text Markup Language
4.17 XML- Extensible Markup Language
4.18 CSS- Cascading Style Sheet
11
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
5. Elements of the software project management plan
5.1 Project Name:
The name of the project is “psmovers.com.au” An e-commerce website.
5.2 Project Overview:
The main purpose of the project is to develop the E-commerce website for business. It will
facilitate the business to selling and buying the products. This project will provide the convenient
to customers. It will allow the Customers to do online payments ordering. This project is based on
the emerging computer software to make people life easier and let people know about upcoming
products via clicking their computer and laptops. It will save people time rather than wasting in
standing in queue and also travel time as well. So the main motto of this project is to buy and sell
goods without coming outside by online. It is also save the paper since we do not need to print the
receipt only interested people can print their receipt.
The required deliverables are login system with two types of user’s buyers, sellers. It will take
three months to be completed. The required budget for this project is $0.00. This project will be
completed within five steps of system development life cycle such as Planning, Analysis, Design,
Implementation, and Maintenance.
5.3 Project Purpose:
The main purpose of the project is to develop the E-commerce website for the PS Movers,
Melbourne, and Vic. It will facilitate the business to selling and buying the products. This project
will provide the convenient to customers. It will allow the Customers to do online payments
ordering.
The required deliverables are login system with two types of user’s buyers, sellers. It will take
three months to be completed. The required budget for this project is $500. This project will be
completed within five steps of system development life cycle such as Planning, Analysis, Design,
Implementation, and Maintenance.
12
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
5.4 Project Description:
The main objective of this project is to develop the website for PS Movers within the time period
of 12 weeks, where the people can buy and sell their products online and get information about the
upcoming goods. The budget of the given project is $500. We have to complete the project within
this amount. As this is a uni project there is no much budget factor.
5.5 Client Information:
Holder Name: Parambir Singh Randhawa
Holder Type: Person
ABN: 48603702750
Address: 23 Sainsbury Ave Hillside Vic 3037
Mobile: 0406958268
Email: parambir9singh@yahoo.co.in
5.6 Project Team: (Internal Structure)
Name
Role in Project
Phone
Tejinder Kaur
Quality Assurance
Manager, Tester
0450213524 Money_saini@hotmail.com
Monika Saini
Developer, Project
Manager
0452663412 sainimonika19@gmail.com
Yousef Alqahtani
DBA, Designer
0498099698 Pattrani.222@gmail.com
Fig2. Internal Structure
13
E-mail
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
5.7 References:
No.
1.
Documents
Deliverable milestone
References
Refer to Annex I
2.
Roles and Responsibility
Refer to Annex II
3.
4.
5.
Work Break down Structure
Refer to Annex III
Refer to Annex IV
Gantt chart
Pert Network
Refer to Annex V
6
Assumption and Constraint
Refer to Annex VI
7
Issue Log
Refer to Annex VII
8
Action Items
Refer to Annex VIII
9
Decision Log
Refer to Annex IX
10
Communication Plan
Refer to Annex X
11
Resource Assignment Matrix
Refer to Annex XI
Fig3. Document Referencing
5.8 Assumptions:
5.8.1 Budget Assumption:
This project is based on the part of our university project so there will no requirement of wages
for the team members. There would be expenditures on the stationery material such as
highlighter, file, pencil, paper, pen etcetera. Each team member has their own laptop so there is
no need to buy any hardware. We may need to buy some kind of software for designing and
programming purpose such as Photoshop, Dreamweaver and Microsoft project.
5.8.2 Schedule Assumption:
Since the project will follow a waterfall approach to the SDLC, the schedule has been structured
in that manner. Where no name is assigned with a role in the schedule, whoever is associated to
that role, Where there are employments of greater than hundred percent, it means more than one
14
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
person with those skills will be assigned to the task. No depth explanation of the dependencies
between tasks is required. From side to side observation of the WB and Gantt chart it can be seen
where the dependencies lie, and reason why they exist.
6. Definitions
6.1 Project Organization:
6.1.1
Introduction:
Project Organisation is an important part of the project from where we can figure out the roles
and responsibilities of each group member. It also provides what are the steps to be followed by
the team organisation.
6.2 Process Model:
The project is started on the 21 November, 2013 and will be completed by the twelve weeks of
time and delivered to the client on same week. The project uses and object oriented design
methodology based on the object life cycle process and using unified modelling language for the
development of the website. The development process for our project buying and selling goods
online is organized in team.
Roles and responsibilities are given to each group member as project manager, designer,
developer, dba, tester, quality assurance manager etcetera. For this project there are several other
roles as well. Since the project is not big each group member are given main role as well as
secondary role too. Each and every member is responsible for the duties and they have to submit
their work by time in through proper testing. The individual approved documents produced by
the teams are considered work products and are part of the software documentation. The
software development model which is use in this project will be the waterfall model. As our
client give us full and final requirement. He does not want any change throughout the project.
15
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Requirements
Water Fall Model
Design & Architecture
Development &
Coding
Quality Assurance &
Software Testing
Implementation
Maintence Support
Fig4. Water Fall Methodology
16
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
6.3 Organisational Structure:
Supervisor
Anup Patil
Project Manger
Monika Saini
Developer
Designer
Monika Saini
Yousef Alqahtani
Tester
Quality Assurance Manger
Tejinder Kaur
Tejinder Kaur
DBA
Yousef Alqahtani
Fig5. Organisational Chart
17
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
6.4 Roles and Responsibilities:
This section describes the roles and responsibilities of the project team.
Team Member
Primary Role
Secondary Role
Contact Info.
Monika Saini
Project Manager
Developer
Money_saini@hotmail.com
0450213524
Tejinder Kaur
Yousef Alqahtani
Quality Assurance
Manager
Tester
DBA
Designer
sainimonika19@gmail.com
0452663412
Pattrani.222@gmail.com
0498099698
Fig6. Role & Responsibilities
6.4.1 Project Manager (Monika Saini)
Project Manager is the one who decide all the tasks for the project. The cost of the project, who
will assign it to do, and all the major decisions related to the project. He is the top person in the
industry, means he has most of the control of other managers and employees as well.
6.4.2 Quality Assurance Manager (Tejinder Kaur)
Quality Assurance Manager is the one who taking overall responsibility of the written content
and quality editing to meet standards. He also ensures that the website is as such friendly as
possible. He correlates information from each content writer sources into a coherent one and also
ensuring the accuracy and quality control. The biggest duty is to revise, format and prepare the
final edition of report.
6.4.3 Tester (Tejinder Kaur)
Tester is the one who can understand the software requirements, contributing in test plan
preparation, deriving the test scenarios/outlines, documenting test cases, updating traceability
matrices document, collecting test data, creating test batches, executing test cases, reporting
18
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
defects, tracking defects, collect test matrics, selecting test cases for re & regression testing,
executing regression tests and modifying test cases etc.
6.4.4 Developer (Monika Saini)
Programmer or developer is the one who live underneath the visuals that the designer has
dreamed up. Programmer deals with lines of code integral in communication concepts in
language computers can understand. The computer languages used by programmer differ by
field, for example, with Php being the standard for most video games etc. Programmer build the
ideas of the designer from the ground floor, writing lines of code in computer programs that best
achieve the designer’s goals. The responsible programmer writes consistent code.
Consistency helps other programmers read and understand her code. It lets them know what to
expect. A good programmer always checks the boundaries of their system to make sure that
invalid data doesn't enter into the core of the application. This way he or she can avoid defensive
programming in the core domain where clarity is even more essential than anywhere else.
6.4.5 Designer (Yousef Alqahtani)
A designer is who responsible for creating design solutions that have a high visual impact. The
role involves listening to clients and understanding their needs before making design
decisions. Their designs are required for a huge variety of products and activities, such as
websites, advertising, books, magazines, posters, computer games, product packaging,
exhibitions and displays, corporate communications and corporate identity, e.g. giving
organizations a visual 'brand’. A graphic designer works to a brief agreed with the client, creative
director or account/project manager. They develop creative ideas and concepts, choosing the
appropriate media and style to meet the client's objectives. The work demands creative flair, upto-date knowledge of industry software and a professional approach to time, costs and deadlines.
He (designer) may involve managing more than one design at a time and allocating the relevant
amount of time according to the value of the job. He developing design briefs by gathering
information and data through research and he needs too cleaver thinking for producing new ideas
and concepts, demonstrating illustrative skills with rough sketches; working on layouts and art
working pages ready for print.
19
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
6.4.6 DBA (Yousef Alqahtani)
A database Administrator (DBA) is who has knowledge about installation, configuration,
upgrade, monitoring, maintenance and securing of database in an organisation. The role also
includes the development and design of database strategies, system monitoring and improving
database performance, capacity and planning for upcoming requirements. He may also plan, coordinate and implement security measures to safeguard the database.
6.4.7 Documenter (Monika, Tejinder, Yousef Alqahtani)
One person who prepare all document work in the team, prepare report for SPMP, SRS, SDD
and other kind of writing content. But in our team there is no specific role of a person for this
role. Each person contributes some part in documentation. Thatswhy We didn’t describe any
particular role above (In roles & responsibilities table).
6.4.8 Researcher (Monika, Tejinder, Yousef Alqahtani)
Person, who conduct research based on the material supplied by the client. He also ensures that
research has accurate information provided to the content writer. Also need to talk with content
writer to make sure that the content is at its purpose. At last but not least prepare outlines, specify
software and suggest references.
6.5 Team Rules and Processes:
All team members have been specified with certain tasks. To avoid conflicts between group
members staffing plan has to be organised. These tasks are to be started accordingly with the
staffing plan table and make sure that each member of the team completes it within the limited
time, scope and budget. Each member is responsible for making right decision, respect each
other work and willing to support project objectives, rules and goals. Team members need to
review and revise procedures during team meetings.
7. RISK MANAGEMENT
7.1 Introduction
The risk management is the crucial part of the project. Usually it is habitually ignored in the
project, but as it is the important part it can help to increase the quality of the project. With it we
can choose the project, define the scope of the project, can develop the real assumptions. Basically
20
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
it is the process where we need to think about the risks which can occur during the development
of the project. In it we need to define the type of the risk, their priority like likelihood and severity
of the risk. After it we will have to design the contingency plan for the risks. Our project is related
to e-commerce website where we will look into the possible risks which can be act as obstacle in
the project.
7.2Risk management plan
For the risk management plan we will conduct a brainstorming session among the team at the
starting of the project. We will do this session based on the form. Form will be on the website from
where team members can fill the form and submit their answers related to the possible risks
according to the think. The document will have the checklist and the names of the risks, source an
environment. Risks need attention whether it is internal or external. We have found several risks
which can be related to our project like:
7.2.1 Security risks for Users

Malware

Unapproved Data Access

Denial of Service

Browser Security
21
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
7.2.2 New risks and Risk Management Chart
Consequences
Almost
Trivial
Minor
Moderate
Major
Tragic
1
2
3
4
5
Security Issue
certain
1
Malware
Expected
likelihood
2
Unauthorized
Potential
Data Access
3
Denial
Not likely
Service
4
Browser
Assured
Security
5
Fig7. Risk Management Chart
The given chart illustrates the likelihood and consequences of risk plan. The description of this
chart is given below:

Security issue falls under 1 in consequence and 1 likelihood. That mean the risk is
moderate and will significant the business.
22
of
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani

Malware falls under 3 in consequence and 2 likelihood. That’s mean the risk is High and
its mean we need to attention and find out solution.

Unauthorized access data falls under 4 in consequence and 3 likelihood which mean the
risk is high soon need it to be fixed.

Denial of Service falls under 5 in consequence and 4 likelihood. Which means the risk is
high. We should significantly increase the level of security.

Browser Security falls under 4 in consequence and 5 likelihood. Which means the risk is
high. In that case user and customer would not trust in this site.
8. TECHNICAL PROCESS
8.1Process Model
Waterfall is the most preferred methodology to use for our project development because it is
heavy methodology and it is preferable for building the heavy projects. We will be going to
target towards simplicity as according to, Extreme Programming philosophy. In the project there
will be two developers are responsible for coding parts. Also there is a weekly team meeting and
we will produce small deliverables every week.
8.2 Methods, Tools, and Techniques
Tools and technologies below can be used for the project.
8.2.1Tools
8.2.1.1Desktop Development

Microsoft Windows 7 /XP/Vista: These platforms will be used while the development
System
8.2.2 Project Management
MS Project: it can be used to make Gantt chart, network diagram.
8.2.3 Programming/Core Development
Adobe Dreamweaver and notepad: These editors can be used for coding.
23
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
8.3 Online Deployment
Server: local via TCP/IP
Server Type: MySQL
Server Version: 5.6.12
Protocol Version: 10
User: root@ local host
8.4Document distribution
All the documents will be formed in Microsoft Word 2010 and distributed electronically. All the
documents will be available in Google docs, drop box.
9.1Control Plan
9.1.1 Requirement control plan
For the requirement control plan the team members will do the task according to the checklist and
the planning. For this we will generate a control plan to keep the status of the project updated and
to be on the right track. It will be helpful for the team to understand the things clearly it will tell
about the restrictions, documentations the needs which we need to change in the project according
to the plan.
9.2 Scheduler Plan
For the schedule plan we have 3 months’ time duration to complete the project. We will work for
20 hrs. per week. We will be in contact to know about the team member’s contribution to complete
the project on the time. We will organize weekly meeting and we will discuss about the purpose
of the project. We will look at each and every part of the task we will also look at the team’s work
so we can give the feedback among team for their work.
9.3 Reporting plan
In the reporting plan we will give the notice to the team members for the reporting on time. There
will be the discussion on the project like what is the status of the project, how much work is done,
how much work is left and we will generate the reports based on that. The final report will be
24
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
presented to the project manager and if there will be any issue we will inform to our project
manager.
9.4 Matrix Collection Plan
The matrix plan will be created if there will be postponements and wrong presentations in the real
process. If we will start underlining the collections. Information about the working time, accuracy
will be collected. Testing outcomes will run correct accuracy matrix.
10.0 Infrastructure Plan
All team members will be in ATMC campus or outside for working on project. ATMC services
will be accessible for all team members via username and password.
Making all the required tasks available to the team members by communicating with the project
manager personally or via email.
11. File Naming Conventions
Successful file naming is the foundation for building an effective paperless office. It is also
important for effective cooperation between individuals working on our project. The names we a
given to our documents create for the good management of our documents. A document that is
given a well-organized name based on a file naming convention is easy to search for, identify and
regain.
12. Backup Procedure
We will regularly backup our documents, folders and file each week. Backup is crucial way to
ensure that our data is safe and secure for the future recovery. We backup our documents in the
following different places.
12.1 External Hard Drive
12.2 Dropbox
13. TESTING PROCEDURES
25
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
13.1 Testing Team
For the Testing there are two team members who has been assigned to test the website. Testing
members are selected according to their knowledge and skills. They are qualified in Web
technologies and software needed to make the E-website. They are expert in HTML, DHTML,
Java, JavaScript, PHP, and MySQL database. Apart of that they are up to date with server
applications, shopping cart functionality, Transaction functionality and so on. They have
developed an E-commerce website already for another client also.
13.2 Testing Area
While Testing time the team will have to cover many area’s which are given:-
13.3 Website Testing
In this area the team needs to perform test for the website. While testing the website they have to
test the browser compatibility, design & layout of the website, content accuracy. It will contains
the grammatical teat and spelling errors on content, reliability of information , compatibility of
most browser and visual appearance.
13.4 Database Testing
In the database testing section team will look at the database. Basically the E-commerce website
contains the information and data records of users, information about the products, transaction
records, orders etc. In this testing the team will check the data integrity, data validity. It will cover
the security of information, data recovery and safety.
13.5 Software Testing
In this section the software which is used in the system is checked to be ensuring performance of
the software according to the operational specifications provided by the client.
26
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
14. Support Process Plan
14.1.1 Configuration Management Plan
In the configuration plan we will manage the communication process.
14.1.2 Controlling Releases
In this section we will take care of the creation of the documents which we create. It will look after
the unnecessary documentation because of uncontrolled versions of the documents.
14.1.3 Versioning
We will keep the version control of each document. If any document will require any changes in
plan. Then we are required to provide the version control document for each document which will
get any changes. Version control document will help to understand the project more deeply or its
plan. If in future due to the client requirements the project require the updated information then
there will be the versions of the document with the updated information.
15. Status Reporting and Change Requests
The status reporting and change request is required to tell the status of task. If any task will be
done by any of the team member then he/she will have to tell the status of each task. To keep the
track of work completed information. In the whole process it will give the status of the project. It
will also tell the current status of the work of the project. If the person who is assigned to a task
to be completed in the given time or like in 3 weeks the every week the status report will be
generated with the name of responsible person. It will be useful for the client to get to know about
the status of the current stage of the project. The status reporting is usually notified by the updating
the milestone with the current status report of the week.
When the scope and specifications of the project is defined then each team member will be required
to complete the work in the given time frame but if there would be any changes or internal or
external changes or else, If the project work will required to get change then the changes will be
27
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
updated in the version control document of the related document. First of all the Project manager
will observe the change request and then process the change which is required.
15.1 Evaluation
In this section the evaluation is required to do the assessment of each phase of the project. In the
end evaluation of database relations, design phase, user interfaces will be done in order to check
the operations and client requirements to be working well. The planning phase and requirements
assessments will be done in the end to be ensure that each requirement is covered or not.
15.2 Notification Changes
In the notification changes the entire project will be get to know if the project will require any
changes via team meeting or email.
16. Validation and Verification Plan
Validation and verification plan tells about the validation and verification process approach of the
project.
16.1 Peer Review
The peer review is to have review on the completed work by the whole team. With this review so
the other team members can comment or compliment on that. With the peer review document the
team members can judge whether project is developing in a right way. This Approach will be
helpful to make the high quality system. The meeting with client will be organized to be ensure
about the requirements in other way the client is also responsible to verify the system according
to his/her requirements.
16.2 Supervisor Review
Supervisor can also review the documents to measure the quality of the project whether is it correct
or not according to the desirable system. Supervisor is also responsible to give comment or
28
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
compliments. It will make the project more competitive or effective because supervisor’s feedback
is also very crucial for the project. In this way the client can get the desirable project or system.
16.3 Milestone Review
Actually the milestone review helps to define the deliverables and the versions of documents. It
can cause to do the work again if the quality of work is not good but accomplishment of the
milestone is done. It can also encourage the team members if the milestone accomplished and the
quality of work is good. So milestone can enhance the work load and it can also provide success.
16.4 Prototyping
Prototyping is a dummy model of the system. In other words prototyping helps to define the system
which will be developed. It shows that the requirements can be achieved or not. It just describes
the non-functional system and it also indicate what to be done and how.
17. Documentation Plan
The Documentation plan helps to know about the software which is used to make the system. It
has particular standard or approach like investigation, Analysis, Design, implementation and
maintenance. It follows the IEEE (Institute of electrical and electronics engineering) standard for
the documentation plan or documents and fulfill the requirements. It contains the information
about the Author, purpose of the document, Meta data, date of creation, table of content and so on.
There would be deliverable and non-deliverable documents.
17.1 Deliverable documents
Project Proposal
5- Dec-2013
Work Breakdown Structure (WBS)
18- Dec-2013
Software project management plan
18- Dec-2013
Draft SRS & SDD Submission Link
28- Dec-2013
Final documents for Requirements (SRS) and Design (SDD)
29
2- Jan-2013
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Project Presentation
4- Jan-2013
Project Testing
4- Jan-2013
Process, Teamwork and Initiative: Doc. Maintenance, Project
11- Feb-2013
Management, Participation and Research
Final System/Prototype- Implementation, Test Reports and User
11- Feb-
Documentation
2013
Fig8. Deliverable Documents
17.2 Non-deliverable
Documents will be the meeting plans, Meeting minutes, design summaries, web page design
plan, project closure checklist. We will create every document will be according to the IEEE
(institute of electrical and electronics engineering) standards.
All the deliverable documents will be discussed with supervisor and improved before delivery.
17.3 Versioning Standards
Versioning is the standard where we can generate the numbers or different numbers to the
documents. It helps to control the versions of the documents. It is helpful to know about the
changes in the documentation. It helps to manage the quality of the product and the versioning of
the document. With the versioning standard the software developer can enhance the numbers
easily. Our team members or team will follow this strategy to maintain the documentation and to
provide the high quality product to the client.
18. Quality Assurance Plan (QAP)
The quality assurance plan helps to maintain the quality of the product. This plan will have the
information about the method and activities which we will use to produce the high quality product
for the client. The Quality assurance plan will help to specify the link between quality assurance,
testing, review, audit and configuration management. At the end of the project the quality
assurance will have to check the product for the desirable outputs. While the testing phase if there
30
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
will be any issues or problems with the product then the quality assurance manager will be
responsible for the product. Then the person has to provide or generate the solution for that.
18.1 Reviews and Audit
The reviews will be done by the time or by the fixed time. The review will help to know whether
the project is in right direction, is it getting the milestones on a time on not. The reviews has to
make the reports on the project like is it progressing. With that the team can come to know that
how they can increase the progress and the quality of the project.
18.2 Problem Resolution Plan
During the project if any problem occurred or found then the person who found the error or the
problem has to write or make the note of the problem like what the problem is, when it occurs,
what activity is leading to the problem, what is the type of problem is: like managerial, technical.
Then that person should inform the project manager about the problem then the project manager
will be responsible for the solution. The project manager then can assign the responsible person to
generate the solution for that.
18.3 Problem Prioritizing
In this section we will prioritize the issues or problems. The standard of the prioritizing the problem
will be by the high, medium, low based on the risk. Then the problems will be solved based on the
prioritizing problem or prioritizing matrix of the problem.
18.4 Budget Allocation Plan
The Budget Allocation Plan is not required for this project because this project is the part of the
academic course.
18.5 Decision Making Plan
The Decision making plan helps to make the decisions on some situations. The decision making
plan is really difficult in the project. For this project we will take decision with the help of team
meetings. We will look each and every part of the project. We will think or keep in mind about the
triple constraints cost, time, money. We will take decisions based on the risk and cost, time, quality.
We will manage the planning, change control, version control, tracking the status of the project.
31
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
While taking the decisions the whole team will contribute and in the last the project manager will
decide about the best decision.
Refer to Annex I
Deliverable milestone
Deliverable milestones
Project
PS Movers ecommerce website
Project #
32
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Project
manager
Monika Saini
Sponsor
0
Project
artifacts
PS Movers ecommerce website
Updated
13/12/2013
ID
1
2
3
4
Actual
Completi
on
Objectives
Assumptio
ns
Constraints
-
-
Milestone
Description
Forming
Group
Find the
team
member to
do the
proper
project.
21-Nov13
27-Nov13
To make a
group of the
project.
Select
project
Select the
suitable
project for
the group.
28-Nov13
29-Nov13
Select project
which team
want to.
-
-
5-Dec13
6-Dec13
Project
proposal
Objective
and scope
of the
project.
Making
objective and
scope of the
project.
-
-
WBS
PERT
5
Planned
Completi
on
Network,
SPMP
9-Dec13
9-Dec13
To control
the time of
project and
the
deliverable of
project.
Team
can
follow all
project
milestone
s.
Have a
shot time
to do
project(12
weeks)
12-Dec13
13-Dec13
Finalise
software
project
management
plan
-
-
Project
time
managemen
t method.
Method for
analysis
time of the
project.
33
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
6
7
SRS
Draft
Draft of
Software
Requiremen
t
Specificatio
n.
SDD
Draft
Draft of
Software
Design
Developme
nt.
19-Dec13
Find the need
of the system
the clients
need.
-
-
26-Dec13
Description
of the
software.
-
-
2-Jan-13
Find the
need of the
system the
clients need.
-
-
2-Jan-13
Description
of the
software.
-
-
-
The group
have just
one
designer
Make the
database
according to
client
requirement
-
The group
have just
one dba
Code the web
pages
No
problem
with the
test.
The group
have just
one
Developer
Software
Requiremen
t
8
9
SRS
Specificatio
n
SDD
Software
Design
Developme
nt.
9-Jan-14
10
11
12
Design
Story
board
Draw the
design of
website
Get idea
about website
look likes
14-Jan14
Design
Database
Design the
database
according to
client
requirement
18-Jan14
Implemen
t Web
Pages
Testing the
code and
connecting
with data
base.
34
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
30-Jan14
13
Connect
Database
Test database
No
problem
with the
test.
-
Test All
function.
No
problem
with the
test.
-
Make the 7-Feb-14
code
document to
program it
work.
Make user
more
understand
about the
code.
-
-
Submit all
project
documents.
Finish all
project
documents.
-
-
To submit
the final
website.
Compare
the final
product
on time
-
Link to
database
5-Feb-14
14
Test All
function
15
Test
Report
16
All
Documen
t
18
Final
product
Test web
service
Submit the
website
11-Feb14
13-Feb14
Refer to Annex II
Roles and Responsibilities
Roles and Responsibilities
Project
PS Movers ecommerce
website
Project #
35
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Monika Saini
Sponsor
0
Project artifacts
PS Movers ecommerce
website
Updated
13/12/2013
Name
Core/
Extend
ed
Team
% Assigned
Project manager
Deliverable
s Leading
Deliverable
s
Participatin
g On
Project
Role
Monika
Responsibility
Project
Assignment
s
Lead the team
Core
100
-
-
Tejinder
Core
100
-
Project
Manager
&
Develope
r
And also
develop
overall
webpages,
integrates all
development
functions.
-
Quality
Assuranc
e
Manager
& Tester
Check all
documentatio
n and test all
functions
-
Designer
& DBA
Designs
overall web
pages such as
User Interface
and Story
boards. And
also connect
database as
well.
-
Yousef
Core
100
-
-
36
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Refer to Annex III
Work Break down Structure
Work Break down Structure
Project
PS Movers e-commerce
website
Project #
Project
manager
Monika Saini
Sponsor
37
0
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
ID
1
2
3
4
Task
Dependencies
PS Movers e-commerce
website
Project
artifacts
Forming
group
Select
project
Project
proposal
WBS
Actual
Status
competed
1
2
3
competed
competed
competed
Effor
t
Days
Start
Cos
t
SPMP
6
Gather
requireme
nt
7
8
SRS
SDD
3
5
6
7
Date
Planned
Completio
n
Estimate to
Completio
n
Completio
n
27Nov-13
27Nov-13
-
21Nov
-13
29Nov-13
-
28Nov
-13
4-Dec13
-
2Dec13
6-Dec13
-
5Dec13
13Dec-13
13Dec-13
5
9Dec13
17Dec-13
17Dec-13
2
16Dec13
20Dec-13
20Dec-13
3
18Dec13
27Dec-13
27Dec-13
5
23Dec13
5
2
3
2
completed
5
13/12/2013
Updated
38
27Nov-13
Resourc
e
29Nov-13
29Nov-13
-
4-Dec13
4-Dec13
-
6-Dec13
6-Dec13
13Dec-13
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Slack time
9
Design
Story
board
10
Design
Database
11
Implement
Web
Pages
12
13
14
15
16
Connect
Database
Test All
function
Test
Report
User
Document
Final
Report
7
9
9,10
10,1
1
11,1
2
12,1
3
1-Jan14
1-Jan14
3
30Dec13
8-Jan14
8-Jan14
5
2Jan14
13-Jan14
13-Jan14
5
9Jan14
24-Jan14
24-Jan14
9
14Jan14
27Jan14
29-Jan14
29-Jan14
4-Feb14
4-Feb14
4
30Jan14
6-Feb14
6-Feb14
2
5Feb14
10-Feb- 10-Feb14
14
2
7Feb14
13-Feb- 13-Feb14
14
3
11Feb14
3
39
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Refer to Annex IV
Gant chart (By using Microsoft Project)
40
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Refer to Annex V
Pert Network(By using Microsoft Project)
41
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Refer to Annex VI
Assumptions and Constraints
42
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Assumptions and Constraints
Project
PS Movers ecommerce website
Project #
Project manager
Monika Saini
Sponsor
0
Project artifacts
PS Movers ecommerce website
Updated
13/12/2013
ID
Description
Comments
Type
Status
Date Entered
1
$130 cost for
developing this
project(Domain
and hosting)
Based on
requirements
&
development
plan(Client
paid)
Cost
Confirmed
7/Dec/2013
2
Initial
estimates for
the project as
provided in the
SPMP are +/20%
SPMP can
be changed if
needed
Scope
Open
7/Dec/2013
Customer can
buy and sell
products
online.
The team
will know
when it will
be finished
and have
some
experience
for develop
e-commerce
websites.
Scope
Open
7/Dec/2013
No any other
hardware
required for
this project. As
Client
require that
only used on
Computer
3
4
43
7/Dec/2013
Cost
Confirmed
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
everyone has
their own
laptop.
5
7
8
9
and laptop
device.
Whole team
arrange a
training
session.
Based on the
requirement
of client,
since all are
freshers and
uni students
Work process
as follow the
schedule.
Work
process are
monitor by
tutor &
project
manager
Non-authority
users cannot
access into the
system.
Team
members
have skills
to develop &
this is the
important
feature
All required
features are
meet in the ecommerce
website
All code &
development
are
monitored &
controlled on
weekly basis
7/Dec/2013
Scope
7/Dec/2013
Time
Confirmed
7/Dec/2013
Cost
Open
7/Dec/2013
Time
Refer to Annex VII
Issue log
44
Open
Open
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Issue Log
Project #
Project manager
Monika Saini
Sponsor
0
Project artifacts
PS Movers e-commerce
website
Updated
13/12/2013
ID
1
Issue
Description
Project
Impact
Action
Plan/Resolution
Owner
Miss
team
meeting
Miss
some
update
of the
project
Call to him
and update
the project
via Google
doc
Yousef
Alqahtani
2
3
4
5
6
7
8
9
10
11
12
13
14
45
Importa
nce
Project
PS Movers e-commerce
website
L
Date
Entered
Date to
Review
Date
Resolved
5-Dec13
5-Dec13
5-Dec13
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
15
Refer to Annex VIII
Action Items
Action Items
46
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Project
PS Movers ecommerce website
Project #
Project
manager
Monika Saini
Sponsor
0
Project
artifacts
PS Movers ecommerce website
Updated
13/12/2013
Owner
Status
Date
Planned
Actual
Entered Completion Completion Comments
Monika
5-Deccompeted 13
ID
Action
Item
1
Project
proposal
2
3
WBS
PERT
4
SRS Draft
5
SDD
Draft
6
SRS
10-Dec-13
10-Dec-13
11-Dec-13
11-Dec-13
Monika
11-Deccompeted 13
12-Dec-13
12-Dec-13
Monika
12-Deccompeted 13
Tejinder
19-Dec13
Tejinder
26-Dec13
Monika
1-Jan14
Tejinder
1-Jan14
Yousef
6-Feb14
Yousef
every
week
7
SDD
8
Test
Report
9
Meet
Report
10
All
documents Tejinder
10-Feb14
47
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
11
User
document
12
Final
report
Yousef
11-Feb14
Monika
12-Feb14
Refer to Annex IX
Decision Log
Decision Log
48
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Project
PS Movers ecommerce website
Project #
Project manager
Monika Saini
Sponsor
0
Project artifacts
PS Movers ecommerce website
Updated
13/12/2013
ID
1
Decision
Description
Make an ecommerce
website for
PS Movers
Comments
Owner
Parambir
Singh
-
2
3
4
5
6
7
8
9
10
11
12
13
14
49
Status
Date
Entered
Compete
decision
4-Dec-2013
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
15
Refer to Annex X
Communication Plan
Communication Plan
50
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
PS Movers eProject
commerce website
Project #
Project manager
Monika Saini
Sponsor
0
Updated
13/12/2013
PS Movers eProject artifacts
commerce website
Recipient/
ID
Communication Description
Frequency
Format
Owner
Attendees
document
Monika
All
Meeting
All
All
All
All
All
All
Update work
1
Update the
tasks from
report
each member
Online
Every day
Work
together &
2
Group meeting
solve problem
2 times a
internal
week
Meet tutor to
ensure the
3
Tutor program
process of the
Meeting
project & find
to review
solution of
a work
issues as
every
need
Weekly
week
Knowledge
gathering &
Review
process
4
Project Class
ensure
Weekly
51
and
update
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
the
project
5
Requirements
Meeting
Change of
changed from
and e
requirement
client
As need
mail
Yousef
All
Monika
All
Hardcopy to
be handed to
supervisor
6
and client
Meeting
Milestone
when
and e
report
requested.
Once
mail
Describe
risks, manage
7
Meeting
Risk
strategies &
Weekly
and e
management
work plan
As need
mail
Tejinder
All
As need
Meeting
Tejinder
All
Monika
All
Soft copy to
team for
further
development
& hard copy
to client when
8
Testing report
required
Describe
9
WBS
activities need
Meeting
to meet
to review
project goals
weekly
52
& plan
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Refer to Annex XI
Resource Assignment Matrix
Resource Assignment Matrix
53
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
Monika Saini
Sponsor
0
Project
artifacts
PS Movers ecommerce
website
Updated
13/12/2013
Tester
Programmer
Project Task
System analyst
Project
manager
Secretary
Project #
Project Manager
Project
PS Movers ecommerce
website
Project Management and Requirements
Initiation
1
Develop Preliminary Project Scope
c1
c2
c2
c2
c2
2
Identify Business Need
c2
c2
c1
c2
c2
3
Complete Project Charter
c1
c2
c2
c2
c2
Planning
1
Establish Project Identity
c1
c2
c2
c2
c2
2
Identify Project Team/Resources
c1
c2
c2
c2
c2
3
Conduct Stakeholder Analysis
r
l
c1
c2
l
4
Prepare Draft Project Schedule
c1
c2
l
l
l
54
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
5
Conduct Project Kick Off Meeting
c2
c1
l
l
l
6
Gather Detailed User Requirements
r
l
l
c2
l
7
Define Current Business Processes
r
l
c1
c2
l
8
Revise Project Schedule
c1
l
l
l
l
9
Develop Project Communication Plan
c2
c1
c2
c2
l
10
Develop Project Organizational
Structure
r
l
c1
c2
l
11
Develop Project Quality Plan
c1
c2
c2
c2
c2
12
Develop Scope Management Plan
c1
c2
c2
c2
c2
13
Develop Risk Management Plan
c2
c1
r
r
c2
14
Develop Change Management Plan
r
c2
c2
c1
c2
15
Develop Schedule Management Plan
c1
c2
c2
c2
c2
16
Develop Technical Specifications
r
l
c2
c1
l
17
Develop Technical Architecture
r
l
c2
c1
I
18
Ongoing Project Management
c1
c2
c2
c2
c2
Execution
1
Develop Training Materials
r
c2
c2
c1
l
2
Execute Communication Plan
r
c1
l
l
l
3
Develop Software
r
c2
c2
c1
l
4
Deploy New Software
r
c2
c2
c1
l
Closing
1
Get deliverable acceptance
r
l
c2
c1
l
2
Close out contracts
r
l
c2
c1
l
3
Conduct closure survey
c2
c1
c2
c2
c2
55
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
4
Conduct/document lessons learned
c2
c1
c2
c2
c2
5
Archive project
c2
c1
c2
c2
c2
Creates The Deliverable
c1: primary creator; c2: contributor
Input Required
l
Reviews The Deliverable
r
Approves The Deliverable
a
Notified When The Deliverable Is
Complete
n
Owns The Deliverable Upon
Completion
o
Legend
Bibliography
56
ITECH-7602
SPMP (Software Project Management Plan)
Monika Saini
Tejinder Kaur
Yousef Alqahtani
C. McConnell, Steven (IEEE 1987). Software Project Management Plan (SPMP)
Template Retrieved on 3 December 2013, from
http://users.csc.calpoly.edu/~jdalbey/205/Mgmt/SPMP.html
IEEE Computer Society (1063-2001). IEEE Standard for Software User Documentation.
Retrieved on 3 December 2013, from http://home.arcor.de/ca.be/images/1063-2001.pdf
Example IEEE software project management plan (SPMP). (n.d.) Retrieved on 9
December 2013, from
http://www.site.uottawa.ca/~shervin/courses/seg4105/project/SPMP.html
Hodge, Becky (2003). IEEE Software Project Management Plans. Retrieved on 9
December 2013, from
https://cs.uwaterloo.ca/~apidduck/CS846/Seminars/Becky/Slides.pdf
Terasoft (2004). Software Project Management Plan (SPMP) for Nirvana National Bank
ATM Software Project. Retrieved on 13 December 2013, from http://www.buckleygolder.com/papers/mbg_SPMP_ProjectManagement.pdf
Software project management plan JAMES project (1997). Carnegie Mellon University.
Pittsburgh. Retrieved on 13 December 2013, from
http://undergraduate.csse.uwa.edu.au/units/CITS4401/practicals/James1_files/SPMP1.pdf
57