Project Management Plan for Information System Development using C#

This project management plan highlights the project estimations, project scope, project resources, stakeholder, schedule, budget, procurement, and communication for the development and implementation of an information system using C# as the programming language.

Project Management Plan
Information Systems
10/1/2018

Project Management Plan
Table of Contents
Introduction...........................................................................................................................................2
Project Background...........................................................................................................................2
Purpose of the Report........................................................................................................................2
Scope Management Plan.......................................................................................................................2
Project Stakeholders..........................................................................................................................2
Problem Statement.............................................................................................................................2
Project Goals & Objectives...............................................................................................................3
Project Deliverables...........................................................................................................................3
Technical Requirements....................................................................................................................3
Project Milestones.............................................................................................................................4
Project Limitations & Constraints.....................................................................................................4
Project Acceptance Criteria...............................................................................................................4
Project Methodology – Agile Management...........................................................................................4
Project Work Breakdown Structure (WBS)...........................................................................................5
Project Scheduling & Network..............................................................................................................5
Gantt chart........................................................................................................................................8
Project Costing: Cost Management Plan...............................................................................................9
Project Resourcing...............................................................................................................................10
Communication Management Plan......................................................................................................12
Communication & Meeting Guidelines...........................................................................................12
Mediums..........................................................................................................................................13
Ethical & Professional Codes..........................................................................................................13
Stakeholder Management Plan............................................................................................................13
Stakeholder Analysis.......................................................................................................................13
Stakeholder Engagement.................................................................................................................14
Procurement Plan................................................................................................................................15
Procurement Requirements..............................................................................................................15
Solicitation Planning........................................................................................................................16
Risk Management Plan........................................................................................................................18
References...........................................................................................................................................20
1

Project Management Plan
Introduction
Project Background
The project includes the development and implementation of an information system using C#
as the programming language. There is set up that will be required for system deployment. It
will require a server and twenty five personal computers so that the information system is
deployed. The PCs shall be enabled with Windows 10 as the operating system.
Purpose of the Report
The report is a project plan that highlights the project estimations, project scope, project
resources, stakeholder, schedule, budget, procurement, and communication.
Scope Management Plan
Project Stakeholders
 Project Client: The information system will be demanded by an organization to be
deployed in it and the requirements & funds of the information system will be
arranged by the stakeholder.
 Project Subcontractors: The responsibility of developing the software will be on the
subcontractors.
 Vendors: 25 PCs with Windows 10 Operating System, Server, and development tools
will be required (Atkinson, Crawford & Ward, 2006).
 End-User: The information system will be accessed and utilized by the end system
users.
 Project Management Board: The decision-making authority and change approvals will
be done by the board. The stakeholder will also conduct audits and reviews.
Problem Statement
There are issues of data mismanagement in the organization along with the increased
frequency of manual mistakes. The deployment of information system will make sure that
these issues are resolved.
Project Goals & Objectives
 To use C# as the programming language for the development of the information
system.
2

Project Management Plan
 To develop the information system according to the functional requirements defined.
 To include the non-functional requirements in the system.
 To stick to the estimated schedule throughout the lifecycle
 To stick to the estimated costs throughout the lifecycle (Wearne, 2014).
Project Deliverables
 Project Brief: The highlights of the project and the results of the feasibility analysis
will be covered in the document.
 Project Plan: An elaborated description of the project areas and planning activities
will be included.
 System Design: The document will include use case models, ER diagram, data flow
diagram, and UI aspects of the system.
 Information System Code: The lines of code of the system written in C# as the
programming language.
 Defect Report: The details of defects in the system with status, id, resource, and
priority levels.
 Final Report: The last deliverable will be the final closure report on the system.
Technical Requirements
 Server: The information system being developed will be deployed using the server.
 PCs: 25 personal computers with Windows 10 Operating System.
 MySQL Database
 Microsoft Visual Studio as the development tool
 HP Quality Centre
 Microsoft Visio as the design tool
 Microsoft Project for scheduling and tracking
Project Milestones
3

Project Management Plan
Project Limitations & Constraints
 Reliance on the productivity and skills of the subcontractors
 Estimated schedule and budget
 Sets of functional and non-functional requirements
 Information Security and data protection
Project Acceptance Criteria
 Cost Variance: The project will be accepted only when the variance is zero or has a
positive value.
 Schedule Variance: The project will be accepted only when the variance is zero or has
a positive value.
 Open Defects: Absence of open defects in the categories as critical, major, or
moderate defects.
 Acceptance of Deliverables: Sign offs from all the project stakeholders on the
deliverables (Dalcher, 2015).
Project Methodology – Agile Management
The project of information system development will be managed using agile methodology.
Agile methodology is an ad-hoc methodology in which the project management work will be
done in a series of sprints. These sprints will involve the sub-set of the managerial
requirements and will focus upon the management of specific project areas for the overall
project management. For example, in the first sprint, the focus will be on the start-up stage
and management of initial activities. The subsequent sprints will focus upon project resource
planning & management, scope management, scheduling, costing, and likewise. The project
management methodology will be synced with the development process and will make sure
that the element of continuous improvement is always maintained in the project (Juricek,
2014).
The methodology has been selected as the information system that is to be developed may
witness changes in the requirements or technology. The involvement of agile methods will
ensure that the information system is flexible and scalable. The incorporation of the changes
will be easy.
4

Project Management Plan
Project Work Breakdown Structure (WBS)
Project Scheduling & Network
5
Development of
Information
System
Sprint 1
Information System
- Business Case
Analysis
First Project
Meeting with the
Sponsor
Analysis of
Information System
Feasibility
Briefing of the
System
Submission of the
brief to the
Sponsor
Milestone 1:
System Brief
Sprint 2
Data Gathering &
requirements
elicitation
Definition and
assessment of
system scope
Project Costing &
Scheduling
Resourcing and
Risk Assessment
Planning on quality
and
communciations
Procurement
Planning
Milestone 2:
Project Plan
Sprint 3, 4
Procurement of
server and 25 PCs
System Design -
Responsive Web
Design, HCI
NoSQL Database
Networking of
front end and back
end
Source code
development
Unit testing
Milestone 3:
Source Code
Sprint 5
Information System
Testing
Reporting of the
defects using
defect logging tool
System Reviews
Change
Management &
Implementation
Milestone 4:
Change Report
Sprint 6
Beta Testing by
System Users
Organization of
training
Sign-offs on
deliverables
System
Documentation
Closure report
development
Milestone 5:
Closure Report

Project Management Plan
Gantt chart
6

Project Management Plan
7

Project Management Plan
Project Costing: Cost Management Plan
8

Project Management Plan
Project Resourcing
The development of the information system will be done by the subcontractors. There will be
team of subcontractors with varied set of skills needed so that the information system is
developed as per the requirements. The resources involved and the distribution of duties to
each of these resources is indicated in the tables below.
9

Project Management Plan
10

Project Management Plan
Communication Management Plan
Communication & Meeting Guidelines
 Project management board shall facilitate all the internal and external meetings
 The invitations shall be sent before checking the availability of all the members on
their calendars.
 The members must send acknowledgement to the meeting invitations
 The members must display enthusiasm and active participation in the meetings
 The use of polite tone must always be maintained.
Mediums
 Emails: The most common mode of communication will be emails which will be used
by the internal as well as external members and stakeholders for communication.
 Instant Messages: The instant messages will be exchanged internally to receive
prompt reply from the fellow team member.
 SharePoint location: The location will be used to upload all the project reports, files,
and documents.
 Social Media: The end system users of the information system will use social media
networks and channels for information sharing and communication (Koskinen, 2004).
11

Project Management Plan
 Face to Face: The internal members of the project will be interacting with each other
in the meeting rooms.
Ethical & Professional Codes
During all of the project communications and activities, it would be essential to maintain the
organizational ethical and professional codes. The primacy of the public interest will be
necessary to be maintained and the professional development shall also be adhered to.
Stakeholder Management Plan
The information system will be demanded by an organization to be deployed in it and the
requirements & funds of the information system will be arranged by the Project Client. The
responsibility of developing the software will be on the subcontractors. 25 PCs with
Windows 10 Operating System, Server, and development tools will be required and will be
provided by the vendor groups. The information system will be accessed and utilized by the
end system users. The decision-making authority and change approvals will be done by the
project management board. The stakeholder will also conduct audits and reviews (Missonier
& Loufrani-Fedida, 2014).
Stakeholder Analysis
Name of the
Stakeholder
Type Level of Interest Level of
Influence
Level of
Contribution
Project Client Internal
Stakeholder
Very High Very High High
Subcontractors External
Stakeholder
Moderate High Very High
Vendors External
Stakeholder
Low Moderate Moderate
End System
Users
External
Stakeholder
Moderate Very High Low
Project
Management
Board
Internal
Stakeholder
Moderate Very High High
Stakeholder Engagement
Name of the Role Contact Information to be Medium
12

Project Management Plan
Stakeholder Details Shared
Project Client  Business Case
 Funds
Email
address
and phone
number of
the
stakeholde
r
 Progress
reports
 Project
Deliverables
 Information
System
deployed for
the users
Emails,
SharePoint
Subcontractor
s
 Development
of the
information
system along
with its testing,
design, and
deployment
Email
address
and phone
number of
the
stakeholde
r
 Business case
 Change
Requests
 Funds
Emails,
SharePoint,
Face to Face
Communicatio
n
Vendors  Materials and
tools needed
Email
address
and phone
number of
the
stakeholde
r
 Details of
materials and
tools
 Payment for
materials and
tools
Emails,
SharePoint
End System
Users
 User
acceptance
testing
 Feedback
Email
address
and phone
number of
the
stakeholde
r
 Information
system
Emails,
SharePoint,
Social Media
Project
Management
Board
 Approvals in
the change
requests
Email
address
and phone
number of
 Progress
reports
 Project
Emails,
SharePoint
13

Project Management Plan
 Mediator
between the
subcontractors
and clients
the
stakeholde
r
Deliverables
 Information
System
deployed for
the users
Procurement Plan
Procurement Requirements
Requirements Quantity Reason Requirement in
the project
Discharge from
the project
Server 1 It will be
required for
deploying the
information
system
After the
completion of
testing processes
Will be needed
after the
deployment as
well
PCs 25 It will be
required for
deploying and
accessing the
information
system
After the
completion of
testing processes
Will be needed
after the
deployment as
well
MySQL
Database
1 Data storage,
management,
handling, and
organization
After the
planning phase
of the project
Will be needed
after the
deployment as
well
Microsoft
Visual Studio
1 Development of
the source code
After the
planning phase
of the project
Once the system
is successfully
deployed
HP Quality
Centre
1 Test creation
and execution
After the
planning phase
of the project
Once the system
is successfully
deployed
Microsoft Visio 1 System After the Once the system
14

Project Management Plan
designing planning phase
of the project
is successfully
deployed
Microsoft
Project
1 Development of
project schedule,
schedule
tracking,
costing, and
allocation of
duties
From the
beginning of the
planning phase
Once the system
is successfully
deployed
Solicitation Planning
Requirements Quantity Potential
Vendor
Method of
Searching the
Vendors
Method of
Solicitation
Type of
Contractual
Agreement
Server 1 Supplier of
computer
hardware
On the basis of
the results of
market study
On the basis
of Request
for Quotation
Contractual
agreement
and
purchase
order
between
the vendor
and buyer
PCs 25 Supplier of
computer
hardware
On the basis of
the results of
market study
On the basis
of Request
for Quotation
Contractual
agreement
and
purchase
order
between
the vendor
and buyer
MySQL
Database
1 Supplier of
computer
software
On the basis of
the results of
market study
On the basis
of Request
for Quotation
Contractual
agreement
and
purchase
15

Project Management Plan
order
between
the vendor
and buyer
Microsoft
Visual Studio
1 Microsoft
supplier
On the basis of
the results of
market study
On the basis
of Request
for Quotation
Contractual
agreement
and
purchase
order
between
the vendor
and buyer
HP Quality
Centre
1 HP supplier On the basis of
the results of
market study
On the basis
of Request
for Quotation
Contractual
agreement
and
purchase
order
between
the vendor
and buyer
Microsoft
Visio
1 Microsoft
supplier
On the basis of
the results of
market study
On the basis
of Request
for Quotation
Contractual
agreement
and
purchase
order
between
the vendor
and buyer
Microsoft
Project
1 Microsoft
supplier
On the basis of
the results of
market study
On the basis
of Request
for Quotation
Contractual
agreement
and
purchase
order
between
16

Project Management Plan
the vendor
and buyer
Risk Management Plan
The phases involved in the risk management will start with the risk identification process.
The identification of the risks will be done on the basis of the data sets collected. The risks
identified will then be analysed. The evaluation and prioritization of the risks will be done.
The treatment strategy will be applied followed by risk monitoring and closure (Teller, 2013).
Name of the
risk
Description Likelih
ood
Conse
quenc
e
Rank Treatment Strategy
Technical
Failure
The server or any other technical
component may bring up technical
issues.
2 4 8 Transfer of the risk to the
vendor
Information
Security Risks
Malware attacks, data breaches,
denial of service attacks,
eavesdropping attacks, database
injection attacks, data manipulation
issues, man in the middle attacks,
etc.
4 5 20 Use of security controls to
avoid and mitigate
Communicatio
n Issues
The availability of the internal and
external stakeholders may be an
issue.
4 4 16 Development of
communication plan to
avoid
Delay in
Schedule/Over
run of budget
Too many project changes or
operational errors may lead to this
risk.
2 4 8 Reviews and audits to
avoid the risk
Quality Issues The subcontractors may not be aware
of or may fail to adhere to the quality
standards.
1 5 5 Reviews and audits to
avoid the risk
Resource
Issues
The productivity of the resources
may drop at some point in the
1 4 4 Discussion with the
resources to avoid the risk
17

Project Management Plan
project.
Operational
Errors
There may be operational mistakes
committed by the resources.
4 3 12 Trainings and sessions for
risk avoidance
Legal Issues The subcontractors may not be aware
of or may fail to adhere to the legal
standards.
1 5 5 Reviews and audits to
avoid the risk
Ethical Issues The subcontractors may not be aware
of or may fail to adhere to the ethical
standards.
1 5 5 Reviews and audits to
avoid the risk
Requirements
Inflation
Too many changes in the project
requirements.
3 5 15 Reviews and audits to
avoid the risk
18

Project Management Plan
References
Atkinson, R., Crawford, L., & Ward, S. (2006). Fundamental uncertainties in projects and the
scope of project management. International Journal Of Project Management, 24(8),
687-698. doi: 10.1016/j.ijproman.2006.09.011
Dalcher, D. (2015). Going Beyond The Waterfall: Managing Scope Effectively Across the
Project Life Cycle. Project Management Journal, 46(1), e2-e2. doi:
10.1002/pmj.21475
Juricek, J. (2014). Agile Project Management Principles. Lecture Notes On Software
Engineering, 172-175. doi: 10.7763/lnse.2014.v2.117
Koskinen, K. (2004). Knowledge Management to Improve Project Communication and
Implementation. Project Management Journal, 35(2), 13-19. doi:
10.1177/875697280403500203
Missonier, S., & Loufrani-Fedida, S. (2014). Stakeholder analysis and engagement in
projects: From stakeholder relational perspective to stakeholder relational ontology.
International Journal Of Project Management, 32(7), 1108-1122. doi:
10.1016/j.ijproman.2014.02.010
Teller, J. (2013). Portfolio Risk Management and Its Contribution to Project Portfolio
Success: An Investigation of Organization, Process, and Culture. Project Management
Journal, 44(2), 36-51. doi: 10.1002/pmj.21327
Wearne, S. (2014). Evidence-Based Scope for Reducing “Fire-Fighting†in Project
Management. Project Management Journal, 45(1), 67-75. doi: 10.1002/pmj.21395
19