Report on Development of Information System
VerifiedAdded on 2020/04/21
|27
|3521
|42
AI Summary
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: PROJECT MANAGEMENT
Project- Design and development of Information System for a company “AAW”
Name of the Student
Name of the University
Author’s Note
Project- Design and development of Information System for a company “AAW”
Name of the Student
Name of the University
Author’s Note
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1
PROJECT MANAGEMENT
Executive Summary
The report mainly focuses on the design and development of information system for the
company “AAW”. It is identified that the information system that is developed within the
company helps in managing and storing data accurately. In addition to this, it is identified
that the information system assists in providing proper as well as efficient way of managing
different operations of the organizations. In this report, the scope, objective, duration as well
as budget of the project is illustrated so that the information system development can be
completed within the estimated time as well as budget. It is analyzed that during the
development of information system, the company faces number of challenges that needs to be
resolved. The paper provides number of mitigation plan for resolving the issues as well as
challenges. The paper also illustrates the importance of monitoring and controlling strategy,
implementation strategy as well as pricing strategy within the project.
PROJECT MANAGEMENT
Executive Summary
The report mainly focuses on the design and development of information system for the
company “AAW”. It is identified that the information system that is developed within the
company helps in managing and storing data accurately. In addition to this, it is identified
that the information system assists in providing proper as well as efficient way of managing
different operations of the organizations. In this report, the scope, objective, duration as well
as budget of the project is illustrated so that the information system development can be
completed within the estimated time as well as budget. It is analyzed that during the
development of information system, the company faces number of challenges that needs to be
resolved. The paper provides number of mitigation plan for resolving the issues as well as
challenges. The paper also illustrates the importance of monitoring and controlling strategy,
implementation strategy as well as pricing strategy within the project.
2
PROJECT MANAGEMENT
Table of Contents
1. Introduction............................................................................................................................4
2. Business case..........................................................................................................................4
3. Project scope and objectives..................................................................................................5
3.1 Project scope....................................................................................................................5
3.2 Objectives of the project..................................................................................................5
4. KPI of project deliverable......................................................................................................5
5. Strategy for reducing uncertainties and risk management.....................................................6
6. Resource planning..................................................................................................................8
7. Estimation planning...............................................................................................................9
8. Communication planning.....................................................................................................10
9. Project schedule...................................................................................................................11
9.1 Task List.........................................................................................................................11
9.2 Summary task.................................................................................................................12
9.3 WBS...............................................................................................................................13
9.4 Predecessor Linkage.......................................................................................................14
9.5 Resource allocation........................................................................................................17
9.6 Gantt chart......................................................................................................................18
9.7 Network Diagram...........................................................................................................18
10. Project monitoring and control...........................................................................................19
10.1 Milestones....................................................................................................................19
PROJECT MANAGEMENT
Table of Contents
1. Introduction............................................................................................................................4
2. Business case..........................................................................................................................4
3. Project scope and objectives..................................................................................................5
3.1 Project scope....................................................................................................................5
3.2 Objectives of the project..................................................................................................5
4. KPI of project deliverable......................................................................................................5
5. Strategy for reducing uncertainties and risk management.....................................................6
6. Resource planning..................................................................................................................8
7. Estimation planning...............................................................................................................9
8. Communication planning.....................................................................................................10
9. Project schedule...................................................................................................................11
9.1 Task List.........................................................................................................................11
9.2 Summary task.................................................................................................................12
9.3 WBS...............................................................................................................................13
9.4 Predecessor Linkage.......................................................................................................14
9.5 Resource allocation........................................................................................................17
9.6 Gantt chart......................................................................................................................18
9.7 Network Diagram...........................................................................................................18
10. Project monitoring and control...........................................................................................19
10.1 Milestones....................................................................................................................19
3
PROJECT MANAGEMENT
10.2 Baseline........................................................................................................................19
10. 3Critical Path..................................................................................................................20
10.4 Slack view....................................................................................................................21
11. Strategy for implementation Change.................................................................................22
12. Critical Evaluation.............................................................................................................24
13. Reflection & Conclusion...................................................................................................25
References................................................................................................................................26
PROJECT MANAGEMENT
10.2 Baseline........................................................................................................................19
10. 3Critical Path..................................................................................................................20
10.4 Slack view....................................................................................................................21
11. Strategy for implementation Change.................................................................................22
12. Critical Evaluation.............................................................................................................24
13. Reflection & Conclusion...................................................................................................25
References................................................................................................................................26
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
4
PROJECT MANAGEMENT
1. Introduction
The paper reflects on the design and development of information system within a
company named AAW that is one of the department of clothing, & Shoe Stores in Oman. The
organization faces number of challenges in storing as well as managing the data related with
sales of the company and therefore the higher authority of AAW suggested development of
information system. With the development of information system, the issues as well as
challenges associated with data management will be resolved easily.
The report illustrates the steps of information system design and development with
proper schedule. The paper also elaborates the process of resource planning, estimation
planning as well as communication planning. In addition to this, the report also focuses on
the strategies that assist in reducing the uncertainties of the project.
2. Business case
It is identified that the company “AAW” faces number of challenges in managing as
well as storing data related with the business as utilization of manual data entry system
creates problem like redundancy. The chances of data loss are also high when the company is
using data entry system. As the business is growing the company find it difficult to cope with
its competitors as they have latest technical set up for managing as well as storing data (Lock
2014). In order to resolve the issues that the company faces due to the use of manual data
entry system and for remaining competitive in the market the higher authority of the company
wants to develop an information system.
PROJECT MANAGEMENT
1. Introduction
The paper reflects on the design and development of information system within a
company named AAW that is one of the department of clothing, & Shoe Stores in Oman. The
organization faces number of challenges in storing as well as managing the data related with
sales of the company and therefore the higher authority of AAW suggested development of
information system. With the development of information system, the issues as well as
challenges associated with data management will be resolved easily.
The report illustrates the steps of information system design and development with
proper schedule. The paper also elaborates the process of resource planning, estimation
planning as well as communication planning. In addition to this, the report also focuses on
the strategies that assist in reducing the uncertainties of the project.
2. Business case
It is identified that the company “AAW” faces number of challenges in managing as
well as storing data related with the business as utilization of manual data entry system
creates problem like redundancy. The chances of data loss are also high when the company is
using data entry system. As the business is growing the company find it difficult to cope with
its competitors as they have latest technical set up for managing as well as storing data (Lock
2014). In order to resolve the issues that the company faces due to the use of manual data
entry system and for remaining competitive in the market the higher authority of the company
wants to develop an information system.
5
PROJECT MANAGEMENT
3. Project scope and objectives
3.1 Project scope
The project scope is divided into in-scope and out scope which are elaborated below:
In-scope: The in scope of the project includes:
Design and development of information system
Up gradation of available technical setup
Enhancing competition of the organization in global market
Data storage as well a management must be done efficiently as well as
accurately
Out scope: The out scope of the project is as follows:
Training facility should not be provided to the team members
The changes in organizational strategies due to development of information
system are not included in the project scope
3.2 Objectives of the project
The objective of the project includes:
To design and develop information system for a company “AAW”
To store as well as manage important information and data of the company
To use proper licensed software within the information system of the company
4. KPI of project deliverable
The KPI of project deliverables are as follows:
PROJECT MANAGEMENT
3. Project scope and objectives
3.1 Project scope
The project scope is divided into in-scope and out scope which are elaborated below:
In-scope: The in scope of the project includes:
Design and development of information system
Up gradation of available technical setup
Enhancing competition of the organization in global market
Data storage as well a management must be done efficiently as well as
accurately
Out scope: The out scope of the project is as follows:
Training facility should not be provided to the team members
The changes in organizational strategies due to development of information
system are not included in the project scope
3.2 Objectives of the project
The objective of the project includes:
To design and develop information system for a company “AAW”
To store as well as manage important information and data of the company
To use proper licensed software within the information system of the company
4. KPI of project deliverable
The KPI of project deliverables are as follows:
6
PROJECT MANAGEMENT
Project time: Designing as well as development of information system for the
company “AAW” can be completed in 31 days.
Budget creation cycle time: In order to estimate the budget of the project, the project
manager spends two days with other stakeholders of the project.
Number of errors: The project faces number of problems due to errors that are
associated with software, hardware, budget, time as well as due to improper management
(Cheeseman and Garvey 2014). All the issues or errors needs to be resolved properly n time.
Need of training: In this project, the team members require proper training facility
for handling the information system of the company easily.
5. Strategy for reducing uncertainties and risk management
Risk Risk
identification
Risk
categorization
Impact Risk
management
with plan
Faulty hardware The hardware
which is utilized
within the
information
system is not
proper as a result
the system may
fail in providing
proper outcome
as expected
(Cicmil et al.
High High The hardware
system must be
tested before
utilizing it within
the information
system
PROJECT MANAGEMENT
Project time: Designing as well as development of information system for the
company “AAW” can be completed in 31 days.
Budget creation cycle time: In order to estimate the budget of the project, the project
manager spends two days with other stakeholders of the project.
Number of errors: The project faces number of problems due to errors that are
associated with software, hardware, budget, time as well as due to improper management
(Cheeseman and Garvey 2014). All the issues or errors needs to be resolved properly n time.
Need of training: In this project, the team members require proper training facility
for handling the information system of the company easily.
5. Strategy for reducing uncertainties and risk management
Risk Risk
identification
Risk
categorization
Impact Risk
management
with plan
Faulty hardware The hardware
which is utilized
within the
information
system is not
proper as a result
the system may
fail in providing
proper outcome
as expected
(Cicmil et al.
High High The hardware
system must be
tested before
utilizing it within
the information
system
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
7
PROJECT MANAGEMENT
2017).
Cyber Security
Threats
Cyber security
threats create
negative impact
on the system. It
can cause loss of
important as well
as confidential
information
High High The company
must use proper
licensed software
as well as proper
security system
in order to keep
confidential
information as
well as data safe
(Fleming, Q.W.
and Koppelman
2016).
Improper
estimation of
budget
If the project
managers re
unable to
estimate the
budget of the
project proper
due to improper
analysis then the
budget of the
project changes
and the chances
of facing
financial
problems by the
Medium High Proper analysis
must be done
before estimating
the budget of the
project.
PROJECT MANAGEMENT
2017).
Cyber Security
Threats
Cyber security
threats create
negative impact
on the system. It
can cause loss of
important as well
as confidential
information
High High The company
must use proper
licensed software
as well as proper
security system
in order to keep
confidential
information as
well as data safe
(Fleming, Q.W.
and Koppelman
2016).
Improper
estimation of
budget
If the project
managers re
unable to
estimate the
budget of the
project proper
due to improper
analysis then the
budget of the
project changes
and the chances
of facing
financial
problems by the
Medium High Proper analysis
must be done
before estimating
the budget of the
project.
8
PROJECT MANAGEMENT
company
increases
(Flyvbjerg 2013).
Inexperienced
project managers
If the project
managers are not
experienced then
it will be quite
difficult for them
to manage the
project
effectively and as
a result the
chances of
completing the
project on time
and budget
reduce.
Medium Medium Experienced
project managers
must be hired in
the project so that
the entire project
must be managed
properly (Grunig
2013).
6. Resource planning
The resources that are needed for the project are as follows:
Deliverables Resources
Software Windows, licensing software and more
Communication system Telephones as well as subscription on social
media
Business portal Different programming languages like Java and C
Training of the employees Information system for training
PROJECT MANAGEMENT
company
increases
(Flyvbjerg 2013).
Inexperienced
project managers
If the project
managers are not
experienced then
it will be quite
difficult for them
to manage the
project
effectively and as
a result the
chances of
completing the
project on time
and budget
reduce.
Medium Medium Experienced
project managers
must be hired in
the project so that
the entire project
must be managed
properly (Grunig
2013).
6. Resource planning
The resources that are needed for the project are as follows:
Deliverables Resources
Software Windows, licensing software and more
Communication system Telephones as well as subscription on social
media
Business portal Different programming languages like Java and C
Training of the employees Information system for training
9
PROJECT MANAGEMENT
Data ware house Big data as well as proper configuration
Hardware The hardware include printer, CPU as well as
mobile phones.
7. Estimation planning
The budget that is required for completing the project is around $120,000.00. The
budget that is required for completing the project activities is around $81,680 however the
remaining budget is utilized on different resources or materials of the project (Heldman
2015). The table below reflects the budget that is needed for the project.
Task Name Cost
Design and Development of Information System in
organization AAW
. .ر ع8,168.00
Project initiation phase . .ر ع480.00
Analyzing project needs . .ر ع200.00
Development of project plan . .ر ع160.00
Feasibility testing . .ر ع120.00
Milestone 1: Completion of project initiation phase . .ر ع0.00
Project planning phase . .ر ع1,208.00
Task scheduling . .ر ع120.00
Estimation of resources . .ر ع120.00
Resource allocation . .ر ع336.00
Development of communication plan . .ر ع504.00
Project team allocation . .ر ع128.00
Milestone 2: Completion of project planning phase . .ر ع0.00
PROJECT MANAGEMENT
Data ware house Big data as well as proper configuration
Hardware The hardware include printer, CPU as well as
mobile phones.
7. Estimation planning
The budget that is required for completing the project is around $120,000.00. The
budget that is required for completing the project activities is around $81,680 however the
remaining budget is utilized on different resources or materials of the project (Heldman
2015). The table below reflects the budget that is needed for the project.
Task Name Cost
Design and Development of Information System in
organization AAW
. .ر ع8,168.00
Project initiation phase . .ر ع480.00
Analyzing project needs . .ر ع200.00
Development of project plan . .ر ع160.00
Feasibility testing . .ر ع120.00
Milestone 1: Completion of project initiation phase . .ر ع0.00
Project planning phase . .ر ع1,208.00
Task scheduling . .ر ع120.00
Estimation of resources . .ر ع120.00
Resource allocation . .ر ع336.00
Development of communication plan . .ر ع504.00
Project team allocation . .ر ع128.00
Milestone 2: Completion of project planning phase . .ر ع0.00
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
10
PROJECT MANAGEMENT
Execution Phase . .ر ع6,248.00
Deployment Device . .ر ع320.00
Prototype Project . .ر ع320.00
Accounting software testing . .ر ع80.00
Creation of database for accounts department . .ر ع280.00
Database Connection with the device . .ر ع320.00
Time testing device response . .ر ع560.00
Testing of database system . .ر ع504.00
Real time data transfer testing . .ر ع520.00
User acceptance testing . .ر ع1,176.00
Testing of the software . .ر ع768.00
Data Warehouse Testing . .ر ع896.00
Testing of connectivity . .ر ع504.00
Milestone 3: Completion of execution phase . .ر ع0.00
Closing Phase . .ر ع232.00
Stakeholder sign off . .ر ع120.00
Review of entire project . .ر ع112.00
Milestone 4: Completion of closure phase . .ر ع0.00
8. Communication planning
Stakeholder Outcome Key message Channel Frequency
Project manager Reviews the
project progress
Manages the
It assists the tea
m members to
utilize resources
E-mail and
meeting
Monthly basis
PROJECT MANAGEMENT
Execution Phase . .ر ع6,248.00
Deployment Device . .ر ع320.00
Prototype Project . .ر ع320.00
Accounting software testing . .ر ع80.00
Creation of database for accounts department . .ر ع280.00
Database Connection with the device . .ر ع320.00
Time testing device response . .ر ع560.00
Testing of database system . .ر ع504.00
Real time data transfer testing . .ر ع520.00
User acceptance testing . .ر ع1,176.00
Testing of the software . .ر ع768.00
Data Warehouse Testing . .ر ع896.00
Testing of connectivity . .ر ع504.00
Milestone 3: Completion of execution phase . .ر ع0.00
Closing Phase . .ر ع232.00
Stakeholder sign off . .ر ع120.00
Review of entire project . .ر ع112.00
Milestone 4: Completion of closure phase . .ر ع0.00
8. Communication planning
Stakeholder Outcome Key message Channel Frequency
Project manager Reviews the
project progress
Manages the
It assists the tea
m members to
utilize resources
E-mail and
meeting
Monthly basis
11
PROJECT MANAGEMENT
resources required
for change
management
properly and
execute the
project changes
within the
assumed time
(Hwang and Ng
2013).
Finance manager Analyzes the
budget utilized
It helps the team
members of the
organization to
utilize resources
properly avoid
wastage of
resources
E-mail and
meeting
Weekly basis
9. Project schedule
9.1 Task List
Task Name Duration
Design and Development of Information System for a
company "AAW"
31 days
Project initiation phase 9 days
Analyzing project needs 5 days
Development of project plan 4 days
Feasibility testing 3 days
Milestone 1: Completion of project initiation phase 0 days
PROJECT MANAGEMENT
resources required
for change
management
properly and
execute the
project changes
within the
assumed time
(Hwang and Ng
2013).
Finance manager Analyzes the
budget utilized
It helps the team
members of the
organization to
utilize resources
properly avoid
wastage of
resources
E-mail and
meeting
Weekly basis
9. Project schedule
9.1 Task List
Task Name Duration
Design and Development of Information System for a
company "AAW"
31 days
Project initiation phase 9 days
Analyzing project needs 5 days
Development of project plan 4 days
Feasibility testing 3 days
Milestone 1: Completion of project initiation phase 0 days
12
PROJECT MANAGEMENT
Project planning phase 10 days
Task scheduling 5 days
Estimation of resources 3 days
Resource allocation 6 days
Development of communication plan 7 days
Project team allocation 4 days
Milestone 2: Completion of project planning phase 0 days
Execution Phase 20 days
Deployment Device 8 days
Prototype Project 8 days
Accounting software testing 5 days
Creation of database for accounts department 7 days
Database Connection with the device 8 days
Time testing device response 7 days
Testing of database system 7 days
Real time data transfer testing 5 days
User acceptance testing 7 days
Testing of the software 8 days
Data Warehouse Testing 8 days
Testing of connectivity 7 days
Milestone 3: Completion of execution phase 0 days
Closing Phase 8 days
Stakeholder sign off 3 days
Review of entire project 2 days
PROJECT MANAGEMENT
Project planning phase 10 days
Task scheduling 5 days
Estimation of resources 3 days
Resource allocation 6 days
Development of communication plan 7 days
Project team allocation 4 days
Milestone 2: Completion of project planning phase 0 days
Execution Phase 20 days
Deployment Device 8 days
Prototype Project 8 days
Accounting software testing 5 days
Creation of database for accounts department 7 days
Database Connection with the device 8 days
Time testing device response 7 days
Testing of database system 7 days
Real time data transfer testing 5 days
User acceptance testing 7 days
Testing of the software 8 days
Data Warehouse Testing 8 days
Testing of connectivity 7 days
Milestone 3: Completion of execution phase 0 days
Closing Phase 8 days
Stakeholder sign off 3 days
Review of entire project 2 days
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
13
PROJECT MANAGEMENT
Milestone 4: Completion of closure phase 0 days
9.2 Summary task
ID WBS Task Name % Complete Duration Start Finish PredecessorsCost
0 0 Design and Development of Information System in
organization AAW after change
22% 45 days Wed 11/1/17 Tue 1/2/18 11,760.00 .ع.ر
1 1 Project initiation phase 80% 10 days Wed 11/1/17 Tue 11/14/17 512.00 .ع .ر
6 2 Project planning phase 72% 12 days Mon 11/13/17 Tue 11/28/17 1,440.00 .ع .ر
13 3 Execution Phase 6% 34 days Thu 11/16/17 Tue 1/2/18 9,568.00 .ع .ر
27 4 Closing Phase 0% 7 days Thu 12/7/17 Mon 12/18/17 240.00 .ع .ر
B E M B E M B E M B E
September November January March
Figure 1: Summary Task
(Source: Created by Author)
9.3 WBS
Task Name Duration Start Finish
Design and Development of Information
System in organization AAW
31 days Wed 11/1/17 Wed 12/13/17
Project initiation phase 9 days Wed 11/1/17 Mon 11/13/17
Analyzing project needs 5 days Wed 11/1/17 Tue 11/7/17
Development of project plan 4 days Wed 11/8/17 Mon 11/13/17
Feasibility testing 3 days Wed 11/8/17 Fri 11/10/17
Milestone 1: Completion of project
initiation phase
0 days Mon 11/13/17 Mon 11/13/17
Project planning phase 10 days Mon 11/13/17 Fri 11/24/17
Task scheduling 5 days Tue 11/14/17 Mon 11/20/17
Estimation of resources 3 days Mon 11/13/17 Wed 11/15/17
PROJECT MANAGEMENT
Milestone 4: Completion of closure phase 0 days
9.2 Summary task
ID WBS Task Name % Complete Duration Start Finish PredecessorsCost
0 0 Design and Development of Information System in
organization AAW after change
22% 45 days Wed 11/1/17 Tue 1/2/18 11,760.00 .ع.ر
1 1 Project initiation phase 80% 10 days Wed 11/1/17 Tue 11/14/17 512.00 .ع .ر
6 2 Project planning phase 72% 12 days Mon 11/13/17 Tue 11/28/17 1,440.00 .ع .ر
13 3 Execution Phase 6% 34 days Thu 11/16/17 Tue 1/2/18 9,568.00 .ع .ر
27 4 Closing Phase 0% 7 days Thu 12/7/17 Mon 12/18/17 240.00 .ع .ر
B E M B E M B E M B E
September November January March
Figure 1: Summary Task
(Source: Created by Author)
9.3 WBS
Task Name Duration Start Finish
Design and Development of Information
System in organization AAW
31 days Wed 11/1/17 Wed 12/13/17
Project initiation phase 9 days Wed 11/1/17 Mon 11/13/17
Analyzing project needs 5 days Wed 11/1/17 Tue 11/7/17
Development of project plan 4 days Wed 11/8/17 Mon 11/13/17
Feasibility testing 3 days Wed 11/8/17 Fri 11/10/17
Milestone 1: Completion of project
initiation phase
0 days Mon 11/13/17 Mon 11/13/17
Project planning phase 10 days Mon 11/13/17 Fri 11/24/17
Task scheduling 5 days Tue 11/14/17 Mon 11/20/17
Estimation of resources 3 days Mon 11/13/17 Wed 11/15/17
14
PROJECT MANAGEMENT
Resource allocation 6 days Mon 11/13/17 Mon 11/20/17
Development of communication plan 7 days Tue 11/14/17 Wed 11/22/17
Project team allocation 4 days Tue 11/21/17 Fri 11/24/17
Milestone 2: Completion of project
planning phase
0 days Mon 11/20/17 Mon 11/20/17
Execution Phase 20 days Thu 11/16/17 Wed 12/13/17
Deployment Device 8 days Thu 11/16/17 Mon 11/27/17
Prototype Project 8 days Tue 11/21/17 Thu 11/30/17
Accounting software testing 5 days Thu 11/23/17 Wed 11/29/17
Creation of database for accounts
department
7 days Thu 11/23/17 Fri 12/1/17
Database Connection with the device 8 days Mon 11/27/17 Wed 12/6/17
Time testing device response 7 days Tue 11/21/17 Wed 11/29/17
Testing of database system 7 days Tue 11/28/17 Wed 12/6/17
Real time data transfer testing 5 days Tue 11/28/17 Mon 12/4/17
User acceptance testing 7 days Fri 12/1/17 Mon 12/11/17
Testing of the software 8 days Thu 11/30/17 Mon 12/11/17
Data Warehouse Testing 8 days Mon 12/4/17 Wed 12/13/17
Testing of connectivity 7 days Mon 12/4/17 Tue 12/12/17
Milestone 3: Completion of execution
phase
0 days Wed 12/6/17 Wed 12/6/17
Closing Phase 8 days Wed 11/29/17 Mon 12/11/17
Stakeholder sign off 3 days Thu 12/7/17 Mon 12/11/17
Review of entire project 2 days Thu 11/30/17 Fri 12/1/17
PROJECT MANAGEMENT
Resource allocation 6 days Mon 11/13/17 Mon 11/20/17
Development of communication plan 7 days Tue 11/14/17 Wed 11/22/17
Project team allocation 4 days Tue 11/21/17 Fri 11/24/17
Milestone 2: Completion of project
planning phase
0 days Mon 11/20/17 Mon 11/20/17
Execution Phase 20 days Thu 11/16/17 Wed 12/13/17
Deployment Device 8 days Thu 11/16/17 Mon 11/27/17
Prototype Project 8 days Tue 11/21/17 Thu 11/30/17
Accounting software testing 5 days Thu 11/23/17 Wed 11/29/17
Creation of database for accounts
department
7 days Thu 11/23/17 Fri 12/1/17
Database Connection with the device 8 days Mon 11/27/17 Wed 12/6/17
Time testing device response 7 days Tue 11/21/17 Wed 11/29/17
Testing of database system 7 days Tue 11/28/17 Wed 12/6/17
Real time data transfer testing 5 days Tue 11/28/17 Mon 12/4/17
User acceptance testing 7 days Fri 12/1/17 Mon 12/11/17
Testing of the software 8 days Thu 11/30/17 Mon 12/11/17
Data Warehouse Testing 8 days Mon 12/4/17 Wed 12/13/17
Testing of connectivity 7 days Mon 12/4/17 Tue 12/12/17
Milestone 3: Completion of execution
phase
0 days Wed 12/6/17 Wed 12/6/17
Closing Phase 8 days Wed 11/29/17 Mon 12/11/17
Stakeholder sign off 3 days Thu 12/7/17 Mon 12/11/17
Review of entire project 2 days Thu 11/30/17 Fri 12/1/17
15
PROJECT MANAGEMENT
Milestone 4: Completion of closure
phase
0 days Wed 11/29/17 Wed 11/29/17
9.4 Predecessor Linkage
Task Name Duration Start Finish Predecessors
Design and Development of
Information System in organization
AAW
31 days Wed 11/1/17
Wed
12/13/17
Project initiation phase 9 days Wed 11/1/17
Mon
11/13/17
Analyzing project needs 5 days Wed 11/1/17 Tue 11/7/17
Development of project plan 4 days Wed 11/8/17
Mon
11/13/17
2
Feasibility testing 3 days Wed 11/8/17 Fri 11/10/17 2
Milestone 1: Completion of
project initiation phase
0 days
Mon
11/13/17
Mon
11/13/17
3
Project planning phase 10 days
Mon
11/13/17
Fri 11/24/17
Task scheduling 5 days
Tue
11/14/17
Mon
11/20/17
3
Estimation of resources 3 days
Mon
11/13/17
Wed
11/15/17
4
Resource allocation 6 days Mon Mon 4
PROJECT MANAGEMENT
Milestone 4: Completion of closure
phase
0 days Wed 11/29/17 Wed 11/29/17
9.4 Predecessor Linkage
Task Name Duration Start Finish Predecessors
Design and Development of
Information System in organization
AAW
31 days Wed 11/1/17
Wed
12/13/17
Project initiation phase 9 days Wed 11/1/17
Mon
11/13/17
Analyzing project needs 5 days Wed 11/1/17 Tue 11/7/17
Development of project plan 4 days Wed 11/8/17
Mon
11/13/17
2
Feasibility testing 3 days Wed 11/8/17 Fri 11/10/17 2
Milestone 1: Completion of
project initiation phase
0 days
Mon
11/13/17
Mon
11/13/17
3
Project planning phase 10 days
Mon
11/13/17
Fri 11/24/17
Task scheduling 5 days
Tue
11/14/17
Mon
11/20/17
3
Estimation of resources 3 days
Mon
11/13/17
Wed
11/15/17
4
Resource allocation 6 days Mon Mon 4
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
16
PROJECT MANAGEMENT
11/13/17 11/20/17
Development of communication
plan
7 days
Tue
11/14/17
Wed
11/22/17
5
Project team allocation 4 days
Tue
11/21/17
Fri 11/24/17 7
Milestone 2: Completion of
project planning phase
0 days
Mon
11/20/17
Mon
11/20/17
7
Execution Phase 20 days
Thu
11/16/17
Wed
12/13/17
Deployment Device 8 days
Thu
11/16/17
Mon
11/27/17
8
Prototype Project 8 days
Tue
11/21/17
Thu
11/30/17
9
Accounting software testing 5 days
Thu
11/23/17
Wed
11/29/17
10
Creation of database for accounts
department
7 days
Thu
11/23/17
Fri 12/1/17 10
Database Connection with the
device
8 days
Mon
11/27/17
Wed 12/6/17 11
Time testing device response 7 days
Tue
11/21/17
Wed
11/29/17
12
Testing of database system 7 days
Tue
11/28/17
Wed 12/6/17 14
Real time data transfer testing 5 days Tue Mon 12/4/17 14
PROJECT MANAGEMENT
11/13/17 11/20/17
Development of communication
plan
7 days
Tue
11/14/17
Wed
11/22/17
5
Project team allocation 4 days
Tue
11/21/17
Fri 11/24/17 7
Milestone 2: Completion of
project planning phase
0 days
Mon
11/20/17
Mon
11/20/17
7
Execution Phase 20 days
Thu
11/16/17
Wed
12/13/17
Deployment Device 8 days
Thu
11/16/17
Mon
11/27/17
8
Prototype Project 8 days
Tue
11/21/17
Thu
11/30/17
9
Accounting software testing 5 days
Thu
11/23/17
Wed
11/29/17
10
Creation of database for accounts
department
7 days
Thu
11/23/17
Fri 12/1/17 10
Database Connection with the
device
8 days
Mon
11/27/17
Wed 12/6/17 11
Time testing device response 7 days
Tue
11/21/17
Wed
11/29/17
12
Testing of database system 7 days
Tue
11/28/17
Wed 12/6/17 14
Real time data transfer testing 5 days Tue Mon 12/4/17 14
17
PROJECT MANAGEMENT
11/28/17
User acceptance testing 7 days Fri 12/1/17
Mon
12/11/17
15
Testing of the software 8 days
Thu
11/30/17
Mon
12/11/17
16
Data Warehouse Testing 8 days Mon 12/4/17
Wed
12/13/17
17
Testing of connectivity 7 days Mon 12/4/17
Tue
12/12/17
17
Milestone 3: Completion of
execution phase
0 days Wed 12/6/17 Wed 12/6/17 18
Closing Phase 8 days
Wed
11/29/17
Mon
12/11/17
Stakeholder sign off 3 days Thu 12/7/17
Mon
12/11/17
18
Review of entire project 2 days
Thu
11/30/17
Fri 12/1/17 19
Milestone 4: Completion of
closure phase
0 days
Wed
11/29/17
Wed
11/29/17
19
PROJECT MANAGEMENT
11/28/17
User acceptance testing 7 days Fri 12/1/17
Mon
12/11/17
15
Testing of the software 8 days
Thu
11/30/17
Mon
12/11/17
16
Data Warehouse Testing 8 days Mon 12/4/17
Wed
12/13/17
17
Testing of connectivity 7 days Mon 12/4/17
Tue
12/12/17
17
Milestone 3: Completion of
execution phase
0 days Wed 12/6/17 Wed 12/6/17 18
Closing Phase 8 days
Wed
11/29/17
Mon
12/11/17
Stakeholder sign off 3 days Thu 12/7/17
Mon
12/11/17
18
Review of entire project 2 days
Thu
11/30/17
Fri 12/1/17 19
Milestone 4: Completion of
closure phase
0 days
Wed
11/29/17
Wed
11/29/17
19
18
PROJECT MANAGEMENT
9.5 Resource allocation
Figure 2: Resource allocation
(Source: Created by Author)
PROJECT MANAGEMENT
9.5 Resource allocation
Figure 2: Resource allocation
(Source: Created by Author)
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
19
PROJECT MANAGEMENT
9.6 Gantt chart
Figure 3: Gantt chart
(Source: Created by Author)
9.7 Network Diagram
Figure 4: Network Diagram
(Source: Created by Author)
PROJECT MANAGEMENT
9.6 Gantt chart
Figure 3: Gantt chart
(Source: Created by Author)
9.7 Network Diagram
Figure 4: Network Diagram
(Source: Created by Author)
20
PROJECT MANAGEMENT
10. Project monitoring and control
It is identified that the monitoring as well as controlling strategy of the project are
fully based on the tasks project activities that are generally provided in the form of Gantt
chart using slack flow as well as different other methods or procedures.
10.1 Milestones
PROJECT MANAGEMENT
10. Project monitoring and control
It is identified that the monitoring as well as controlling strategy of the project are
fully based on the tasks project activities that are generally provided in the form of Gantt
chart using slack flow as well as different other methods or procedures.
10.1 Milestones
21
PROJECT MANAGEMENT
10.2 Baseline
Figure 5: Baseline
(Source: Created by Author)
PROJECT MANAGEMENT
10.2 Baseline
Figure 5: Baseline
(Source: Created by Author)
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
22
PROJECT MANAGEMENT
10. 3Critical Path
Figure 6: Critical Path
(Source: Created by Author)
PROJECT MANAGEMENT
10. 3Critical Path
Figure 6: Critical Path
(Source: Created by Author)
23
PROJECT MANAGEMENT
10.4 Slack view
Figure 7: Slack view
(Source: Created by Author)
PROJECT MANAGEMENT
10.4 Slack view
Figure 7: Slack view
(Source: Created by Author)
24
PROJECT MANAGEMENT
11. Strategy for implementation Change
The procedure of change management is needed in the project when project outcome
does not resemble with the expected deliverables of the project. During this time, it is quite
important to bring some important changes within the project by keeping the objectives of the
project intact (Kerzner 2013).
In this project, it is identified that the project manager faces difficulty in completing
the entire project within the time that is estimated and as result they want to change the
schedule of the project. Due to the change in the schedule, the budget of the project will also
increase.
11.1 Changes Applied
Schedule and Cost before change
Figure 10: Schedule and cost before change
(Source: Created by Author)
PROJECT MANAGEMENT
11. Strategy for implementation Change
The procedure of change management is needed in the project when project outcome
does not resemble with the expected deliverables of the project. During this time, it is quite
important to bring some important changes within the project by keeping the objectives of the
project intact (Kerzner 2013).
In this project, it is identified that the project manager faces difficulty in completing
the entire project within the time that is estimated and as result they want to change the
schedule of the project. Due to the change in the schedule, the budget of the project will also
increase.
11.1 Changes Applied
Schedule and Cost before change
Figure 10: Schedule and cost before change
(Source: Created by Author)
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
25
PROJECT MANAGEMENT
Schedule after change
Figure 11: Schedule and cost after change
(Source: Created by Author)
11.2 Redrawn baseline and its effect on scheduling
PROJECT MANAGEMENT
Schedule after change
Figure 11: Schedule and cost after change
(Source: Created by Author)
11.2 Redrawn baseline and its effect on scheduling
26
PROJECT MANAGEMENT
11.3 Slack/Float role in change management
12. Critical Evaluation
According to Fleming and Koppelman (2016), management of project is considered
as the art of managing the project and its deliverables with proper view for producing
finished services as well as products. In this project we have utilized proper management
techniques in order to complete the entire project within appropriate time and budget.
Appropriate management techniques are quite useful in developing the information system
within the organization which further helps in resolving all the issues as well as challenges
that the company faces. In addition to this, it is identified that due to successful completion of
project the organization gains huge competitive advantage in the market.
PROJECT MANAGEMENT
11.3 Slack/Float role in change management
12. Critical Evaluation
According to Fleming and Koppelman (2016), management of project is considered
as the art of managing the project and its deliverables with proper view for producing
finished services as well as products. In this project we have utilized proper management
techniques in order to complete the entire project within appropriate time and budget.
Appropriate management techniques are quite useful in developing the information system
within the organization which further helps in resolving all the issues as well as challenges
that the company faces. In addition to this, it is identified that due to successful completion of
project the organization gains huge competitive advantage in the market.
1 out of 27
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.