Project Management Report

PROJECT MANAGEMENTTable of Contents
1. Scope Statement ……………………………………………………………………………………………………… 1
1.1 In-Scope …………………………………………………………………………………………………………… 1
1.2 Out-Scope ………………………………………………………………………………………………………… 1
1.3 Objectives ………………………………………………………………………………………………………… 2
1.4 Deliverables ……………………………………………………………………………………………………… 2
1.5 Constraints ……………………………………………………………………………………………………….. 2
1.6 Assumptions……………………………………………………………………………………………………… 3
2. Work Breakdown Structure ……………………………………………………………………………………… 3
3. Stakeholder Management Plan …………………………………………………………………………………. 6
Reference ……………………………………………………………………… Error! Bookmark not defined.
PROJECT MANAGEMENT
In this report, Project Management System (PMS) generally refers to Project Management
Software (Technology). The software and the tools needed to plan, co-ordinate and manage
large projects are all part of this system. In addition, general software applications or programs,
like email, spreadsheets, calendars, as well as management applications like Monday.com, fall
under this category.
The following are most common modules that a PMS can consist are as follows:
•
•
•
•
•
Creating activities estimates
Creating, updating and sharing schedules for report
Allocating and tracking resources, costs & budgets
Controlling and recording project risks and cost
Improve team collaboration and co-ordination
Firstly, report explains details on scope statement which includes in-scope, out-scope,
objectives, deliverables, constraints and assumptions. Secondly, it reflects on work breakdown
structure of project with the help of table and graph by using Excel and Visio. Lastly, it explains
all stakeholders and their roles including their power and interest in the project.
1. Scope Statement
1.1
In-Scope
The goal is to undertake the implementation of a Project Management System (PMS). The inscope of the project management system includes:
▪
Establishment of a PMS that comprises of a stakeholder management module,
communication module as well as feasibility module.
▪
Importing data with the help of XML and comma-delimited files.
▪
Installing Window 10 on 20 client PC’s.
▪
Installing server software which is followed by setting up of the 20 client PC within the
same network.
▪
Installing PMS on each PC’s.
▪
User acceptance testing and organizing training for the stakeholders
▪
Live support provided by the end of the PMS installation.
▪
Undertaking project review for ensuring that the project includes all the functionalities
and features that are needed.
1.2
Out-Scope
There are some of the functionalities which are not included within the present PMS, and they
are listed below:
1
PROJECT MANAGEMENT
▪
No security or privacy software was installed during the project to keep the PCs of the
client safe and secure.
1.3
▪
No chat or support facility option was present within the PMS
▪
Cloud Technology is not integrated with PMS.
Objectives
The objectives are:
1.4
▪
To implement a PMS that mainly comprises of different project modules.
▪
To install a server and a software server on the system.
▪
To configure Windows 10 on the 20 client PC’s.
▪
Install PMS on Window PC’s
▪
Integrated PMS with Server Software and client Window 10 PC’s
Deliverables
The various deliverables which will be delivered after implementing the project are mainly
listed below:
▪
A project management plan that includes details of the project, including the project
timeline and budget.
▪
A scope management plan that includes details of the items which will be included in
the project and the items that are excluded from the project.
▪
Work breakdown structure that breakdown tasks for their easy and fast execution by
the project stakeholders.
▪
A stakeholder management plan that includes all the details of the stakeholders who are
involved in the project.
▪
1.5
A project management system that mainly includes different types of project modules.
Constraints
During the project, the project team can experience the following limitations or constraints
during the project.
▪
The establishment of the system will only be possible by successfully importing the
data either with the help of XML or by using comma-delimited files, which is
considered a constraint.
2
PROJECT MANAGEMENT
▪
The staff cannot operate the system properly if they do not have proper knowledge
regarding the different types of project modules, and therefore, it is considered as a
constraint for the project.
▪
The PMS software is built from third party so security, more expenses and extra time
may be taking place.
1.6
Assumptions
The assumptions which the project team made during the progress of the PMS are mainly
elaborated below:
▪
The stakeholders who are involved in the project are quite proactive, and thus they are
capable enough to complete all the responsibilities that are mainly assigned to them.
▪
A proper facility of training will be organized for the staff who do have proper
knowledge regarding the different types of modules that are used during the
implementation of the PMS.
▪
All the resources are accessible for the project team whenever needed, so resourcerelated issues will not obstruct the progress of the project.
2. Work Breakdown Structure
Work breakdown structure (WBS) is one of the visual as well as hierarchical as well as the
deliverable oriented deconstruction of a project which is mainly needed for providing a clear
view of the project so that the stakeholders can easily manage the work of the project (Picciotto,
2020). The WBS that is mainly prepared for the PMS is mainly showcased below.
3
PROJECT MANAGEMENT
Figure 1: Work Breakdown Structure
(Source: Created by Author (Double Click to Open Files))
WBS.xlsx
WBS.vsdx
WBS-Stakeholders.vs
dx
4
PROJECT MANAGEMENT
WBS
Activities
1 Project Management System
1.1 Project Management
1.1.1
Planning
1.1.2
Cost & Schedule Management
1.1.3
Scope Management
1.1.4
Task Management
1.1.5
Project Communication
1.1.6
HR Management
1.1.7
Facilities & Space Planning
1.1.8
Project Risk Management
1.1.9
Procurement Management
1.1.10
Quaility Management
1.1.11
Ethical Responsibilities
1.2 System Engineering
1.2.1
Project Technical Planning
1.2.2
Project Technical Supervision
1.2.3
Business Requirement Definition
1.2.4
System Requirement Definition
1.2.5
System Architecture Design
1.3 Software
1.3.1 Front End
1.3.1.1 Software Design
1.3.1.11 Software Requirement Specification
1.3.1.12 Software Work-Package Definition
1.3.1.13 Software Prototyping
1.3.1.14 Software Unit Detail Design
1.3.1.2 Software Build
1.3.1.2.1 Software Unit-Coding
1.3.1.2.2 Software Unit-Debugging
1.3.1.3 Unit-Testing
1.3.1.3.1 Unit-Test Planning
1.3.1.3.2 Unit-Test Case Preparation
1.3.1.3.3 Unit-Test Conduct
1.3.1.3.4 Unit-Test Records
1.3.2 Back End
1.3.2.1
Server Architecture
1.3.2.2
Database Administration
1.3.2.3
Data Transformation
1.3.2.4
Scaliability, Seurity and Realiabiality Testing
1.3.2.5
Server Backup and Recovery
1.4 Hardware
1.4.1
Hardware Requirement Planning
1.4.2
Hardware System Definition
1.4.3
Hardware Component Selection
1.4.4
Hardware Component Testing
1.5 Deliverable Management & Suppliers
1.5.1
Deliverable Tracking
Supply Hardware, Software & Network
1.5.2
Equipment & other Materials
1.6 System Test
1.6.1
Module & Subsystem Testing
1.6.2
System Integration Testing
1.6.3
Acceptance Testing
1.6.4
Defect Classification, Tracking & Metrices
1.7 Support Services
1.7.1
Configuration Management
1.7.2
Quality Assurance
1.7.3
Development Utilities & Tools
1.7.4
Upkeep Environmental Development
1.7.5
Internal Product Liaison
1.7.6 Technical Training
1.7.6.1
Equipment Training
1.7.6.2
Services Training
1.7.6.3
Hardware & Software Operating Training
1.8 Installation
1.8.1
Installation Planning
1.8.2
User Support Documentation
1.8.3
User Communication & Training
1.8.4
Installation Management with Co-ordination
1.8.5
Installing Testing & Verification
1.8.6
Installation Performance Monitoring
Resources
Duration
Budget
Project Manager
Project Management Team
Project Management Team
Project Manager
Project Management Team
Project Manager
Line Managers and HR Managers
Facility Manager
Project Manager
Project Manager
Quality Manager
All Peoples which take Part in Project
IT Manager & Project Technical Support Team
IT Manager, Networking Manager & Project Technical Support Team
IT Manager, Networking Manager
Businsess Analyts and Project Manager
Project Stakeholders
System Architect
IT Manager , Project Technical Support Team
Software Developers
Software Engineer
System Analyst, Software Developer & Software Engineer
Software Developers, Project Technical Support Team
Software Developers
Software Designer
Software Developers
Programmer
Software Developer & Programmer
Software Developer & Programmer
Software Developer & Programmer
Software Developer & Programmer
Software Developer & Programmer
Software Developer & Programmer
Database Expert Engineer & Project Technical Support Team
Database Expert Engineer
Database Expert Engineer
Database Expert Engineer & Programmer
Software Engineer
Database Expert Engineer & Programmer
Hardware Engineer
IT Manager, Technicians & Project Technical Support Team
Hardware Engineer
Technicians
Hardware Engineer
Line Manager, Project Manager & Supplier
Line Manager, Project Manage
4 Week
4 Day
2 Day
1 Day
3 Day
2 Day
3 Day
3 Day
4 Day
2 Day
2 Day
2 Day
2 Week
4 Day
2 Day
1 Day
3 Day
4 Day
11 Week
8 Week
6 Day
3 Day
2 Day
3 Day
2 Day
4 Day
19 Day
6 Day
5 Day
2 Day
1 Day
2 Day
1 Day
3 Week
6 Day
4 Day
5 Day
4 Day
2 Day
2 Week
7 Day
2 Day
2 Day
3 Day
1 Day
Same Day
$6,000
$1,200
$400
$200
$600
$400
$600
$600
$800
$400
$400
$400
$3,000
$1,000
$500
$100
$200
$1,200
$25,000
$13,700
$3,000
$1,500
$500
$700
$200
$1,000
$5,000
$600
$350
$200
$350
$200
$100
$11,300
$6,000
$2,000
$1,500
$800
$1,000
$5,000
$1,000
$500
$1,000
$2,500
$300
Supplier
Tester
Tester
Tester
Tester
Tester
Sponsors, Stakeholders. IT Manager and Project Manager
Configuration Management Team
Quality Assurance Engineer
IT Manager
Software Developers and Technicians
Business analyst, Product manager & Project manager
Trainer
Trainer
Trainer
Technical Training Manager
Project Management Team
Project Team and Project Manager
Project Team & Resource Manager
Project Team and Project Manager
Project Team and Project Manager
IT Manager and Technicians
IT Manager and Project Manager
till 19 Week
3 Week
1 Week
6 Day
4 Day
4 Day
2 Week
2 Day
2 Day
3 Day
4 Day
3 Day
3 Week
1 Week
1 Week
1 Week
3 Week
2 Day
4 Day
1 Week
2 Day
1 Day
5 Day
30 Week
$20,000
$5,500
$2,200
$1,700
$800
$800
$3,000
$500
$400
$600
$500
$1,000
$1,500
$500
$500
$500
$4,000
$400
$600
$1,400
$300
$200
$1,100
$73,300
5
PROJECT MANAGEMENT
6
3. Stakeholder Management Plan
Stakeholder management is considered as one of the procedures that are important for
maintaining proper relationship among the people who creates an impact on the project. The
stakeholder management plan illustrates the contribution of each of the involved stakeholders
and further helps in showcasing their power as well as interest in the project (Pedrini & Ferri,
2019). The stakeholder management plan for the PMS project is mainly showcased in the table
below.
Stakeholders
Internal/
Interest
Influence
Important goal
Contribution
High
High
Proper
IT
Method
External
IT Manager
Internal
completion
manager
is
Video
of the system on
responsible
for
Conference
time.
managing
the
Emails and
establishment of the
Meeting
project management
system
IT
Network
Internal
High
Low
Manager
Installer
Internal
Low
High
Managing
They
are
Email
network-related task
responsible
for
Meeting
in
project
installing the server
management system
and other software
project.
related to the server.
Their main goal is to
They
install
complete installation
server
and
on
PCs of the client.
the
time
the
without
the
other
Email
&
&
Meeting
creating any type of
operational issues.
Technical
Internal
Low
High
The main goal of the
The
technical
Email
support team,
technical
support
team
Meeting
Technician
team is to configure
responsible
the
configuring
support
Windows
10
is
for
successfully so that
Windows 10 on all
the project team can
the 20 PCs of the
client
that
are
&
PROJECT MANAGEMENT
work successfully on
needed
for
the
the PCs.
project management
system.
Project manager
Internal
High
High
The main goal of the
The
project manager is to
managers
are
Conference
finish the work of
responsible
for
Emails and
the project within the
planning,
assumed time and
managing, directing
budget that are set
the work of the
initially
project.
by
the
project team.
project
Meeting
Additionally,
also
Video
they
take
the
responsibility
of
guiding
the
stakeholders of the
project to complete
the project on time
and
deliverables
tracking.
Sponsors
External
High
High
The main goal of the
The sponsors are
Video
sponsors is to fund
responsible
Conference
that is needed for
funding the project,
Emails and
undertaking
and they also help in
Meeting
the
project.
for
guiding
the
stakeholders so that
the stakeholders can
be able to complete
the work of the
project
on
time
experiencing
any
without
type
of
financial
hurdles
during
project.
Suppliers
External
Low
Low
The main goal of the
The suppliers are
suppliers is to supply
responsible
all the items that are
supplying all the
asked
resources
resource
by
the
manager
for
of
the
project,
including
the
hardware
Email
7
PROJECT MANAGEMENT
within the allocated
software and other
time.
needed materials.
The focus is to keep
This
Management
the entire project on
responsible
Team
track
avoid
tracking the project
problems
like
work on a regular
schedule
slippage
basis so that the
Project
Internal
High
Low
to
and delay etc.
team
is
for
Email
8
&
Meeting
entire work of the
project
gets
completed on time
for
avoiding
schedule
slippage
and budget shortfall
like
problems
during the project.
Technical
External
Low
High
The main goal of the
The
Training
trainers is that the
mainly responsible
Manager &
workers get skilled
for providing the
Trainers
in using the different
proper facility of
types
training to the team
of
project
trainers
so
are
management
members
modules.
they can learn new
Email
&
Meeting
that
techniques.
Testers
Internal
Low
High
The main goal of the
The
testers is to ensure
that
no
technical
testers
are
Email
responsible
for
Meeting
checking
the
glitch is present in
technical errors and
the newly developed
glitches
system.
system
in
&
the
quite
successfully.
Human
Resource
Internal
&
Line Managers
High
Low
Important goal is to
Their
assign
is very impressive
Emails
they
handle
the
Video
team
work
and
conferencin
safety.
duties
and
contribution
support them where
they need help and
their role is also in
assigning duties and
tasks.
Meetings,
g
&
PROJECT MANAGEMENT
Facility
Internal
Low
Low
Manager
Play role in day to
Their role is to
day
maintain
operations
related
to
project
services.
Quality
Internal
High
Low
Manager
9
Meetings
and
upkeep organisation
projects.
Quality
Manager
Important
people
Meetings &
will play role in
because they duties
video
inspecting the final
is to check the final
Conferencin
product
product and to make
g
sure that it built with
legal standards and
Customer
expectations
System
External
Low
High
Their goal is to build
They contribution is
Emails,
Architect,
Project Management
to
well
Meetings &
Software
System
standard
and
video
and
from
make
a
Engineer &
both side Clint and
functional
Project
Developer,
Server
Management
g
Software
System according to
Designer,
the requirement of
Programmer &
Conferencin
organization.
Database Expert
Engineer
Hardware
Internal
Low
High
Engineer
Basic
role
is
to
They
provide
implement hardware
updated
according
equipment
to
Software nature
hardware
to
Meetings,
Emails
&
Video
establish
physical
conferencin
side
run
g
to
the
system.
Configuration
External
High
Low
Management
Team
help
Engineering
Team
They
provide
teams
update information
to build stable and
and tools related to
robust system
new
Meetings
Project
Management
System
Product
Manager
Internal
High
High
Their
contribution
main
is
to
Vital people they
Meetings,
have clear vision
Emails
Video
Project
&
achieve
business
that
strategy
through
Management
conferencin
implement
Project
System will help in
g
future business and
PROJECT MANAGEMENT
Management
they also specify
System.
functional
10
requirements.
Business
Analyst (BA)
Internal
High
High
BA
help
to
They
analyse
advance/improve
external
product,
internal
Video
environment,
conferencin
market research etc.
g
processes
software’s.
services,
&
and
Meetings,
Emails
and helps in report
or
document
generating
which
helps
in
understanding and
decision making.
According to Varvasovszky and Brugha (2000) another why to characterized Stakeholders in
the project is by using matrices form which include the role on the basic of interest and power.
Figure 2: Stakeholders Power-Interest Grid (Source: Created by Author)
&
PROJECT MANAGEMENT
11