Professional Documents
Culture Documents
This assignment consists of three (4) sections: a written project plan, revised business
requirements document, project plan PowerPoint presentation, and a finalized project
plan. You must submit the four (4) sections as separate files for the completion of this
assignment. Label each file name according to the section of the assignment it is written
for. Additionally, you may create and / or assume all necessary assumptions needed for
the completion of this assignment.
While taking all business and project parameters into consideration, make quality
assumptions to support the following requirements.
Section 1: Written Project Plan
You are now in the final stage of the project plan development. All previous
documentation should be combined into one document that will serve as the statement
of work for the project. Your goal is to have the project approved by the executive team.
The project plan should be very detailed, which is designed to accomplish the
monumental task of implementation; however, the executive team is only interested in a
30-minute summation. Therefore, you also must create a compelling executive summary
that is supported by your detail that convinces the executive team that they should move
forward with your solution.
Develop a thirty to forty (30-40) page project plan in which you:
Write a five to ten (5-10) page executive summary that provides a high-level technical
overview of your project in which you:
Describe the scope of the project and control measures.
Describe the goals and objectives of the project.
Include a high-level overview of all project deliverables.
Give a detailed, realistically estimated cost analysis of the entire project, including
human capital.
Relate the value of the project plan solution to the competitive advantage that
information technology will afford your organization.
Recommend solution providers who can assist with development and implementation.
Combine all previous documentation for Project Deliverables 1-5 in which you:
Provide all aspects of the information technology implementation into the project plan.
Revise the documentation based on feedback from the earlier evaluation of your
deliverable.
Use at least five (5) quality resources in this assignment. Note: Wikipedia and similar
Websites do not qualify as quality resources.
Section 1 of this assignment must follow these formatting requirements:
Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins
on all sides; citations and references must follow APA or school-specific format. Check
with your professor for any additional instructions.
Include a cover page containing the title of the assignment, the students name, the
professors name, the course title, and the date. The cover page and the reference page
are not included in the required assignment page length.
Include charts or diagrams created in MS Visio or Dia as an appendix of the project plan.
All references to these diagrams must be included in the body of the project plan.
Table of Contents
1. Project Plan Overview
1.1 Background
1.2 Project Description
1.3 Goals and Objectives
1.4 Scope
1.5 Roles and Responsibilities
1.6 Constraints and Assumptions
1.7 Risks
1.8 Project Deliverables
2. Project Work Plan
2.1 Work Breakdown Structure
2.2 Staffing Plan
2.3 Project Schedule
Background
Project Description
Business and project goals and objectives
Scope
The policies and procedures generally define the technique for managing all (software
and hardware) modifications made to the information systems and technical infrastructure
of an organization.
In a globalized market of today, companies are faced with challenges in each and every
step of their business. Our analytics and research services are geared towards giving those
companies that extra edge over the competition. We process and analyze terabytes of data
and break down all the fuzz and chatter around it to give our customers meaningful
insights about their competition and the market they are engaged in.
By leveraging our data collection, processing, and research and analytics expertise and by
focusing on operational excellence and an industry standard delivery model, we help the
leading companies making insightful business decisions.
The project will make use of methodology which is designed to build, test and assess a
practical approach, constructing on existing tools.
done for office area (ERP) and Horizontal integration where archival of data of various
archival system takes place.
Databases include the open SQL database where process values, batch data and messages
are stored.
displaying of data, user can also evaluate data, analysis data and generate reports
The goal of this project is to support the vision, mission, and goals of organization,
helping people realize their visions through the use of information technology.
The project should help firm to achieve its goal of outstanding customer service.
The framework deliverable of project should avoid excess of detail to ensure mutual
understanding, adoption and flexibility.
1.4 Scope
Applications - In order to achieve its goals, company uses following tools:
a) Data collection tools
b) Web Analytics tool
c) Resource tracking application
Information System specialist will be responsible for carrying out these tasks.
Sites - At offshore, data collection is being carried. Data processing and analysis is done
at onsite. Project managers at both sites will prepare the project plan for their respective
sites.
Process Re-engineering - IT Re-engineering implementation can be divided into three
phases: before the process is defined, during process designing and after the process is
designed. Re-engineering will include defining new business opportunities by re-defining
the processes, proficient database utilization and data mining. Information System
Specialist will be responsible for it.
Customization - Customizations will be limited to improvement of old hardware with
new infrastructure. Network engineer along with Information System Specialist will be
responsible for this task.
Interfaces - The companys IS has interfaces for evaluating data i.e. reports defined by
users with MS Office (Excel and Microsoft word), standard components of software like
Crystal reports and Business Objects. Licensed software will deal by the human resource
team.
Technical architecture:
Conversion - Since company is not very old, so all of the online data will need to be
converted in new format as per the upgraded infrastructure.
Testing - It will include integration testing, load testing, tuning and network testing
Data collection
a) SP-based data - It is the data collected over network traffic. It provides data to
tool vendor. It does not collect secure data.
b) Panel based data - It collects internet user data.
c) Tool-monitoring data - It is installed at user end. Alexa is one of the examples in
this category.
d) Online monitoring data - Here user takes survey and provides data to company.
Finance & Marketing activities for the training organization are out of scope of
this engagement.
Organization will allocate key project roles and sufficient budget for the
development and implementation of this project.
Efficient, ample, and proper levels of communication exist between the sponsor,
management, and the project team during all project phases.
The timeline is feasible and reasonable. The phased rollout provides support to
early achievement and sustained improvement. The project involves a detailed
implementation as modules are developed and implemented, followed by
continued competency and enhancements in the component areas.
Economic conditions like land & infrastructure prices are relatively stable
Functional lead, technical lead, database administrator are already been recruited.
Signoff for the various project artifacts happen within 4 working days to ensure
the project is complete on time. And if there are any recommended changes in the
artifacts then those are been notified
The upper limit for the expected budget should not be exceeded by 10%. In case
of overshooting of budget within 10% range, the additional capital will be raised
through loans or VC funding.
The upper limit for the expected time should not be exceeded by 60 days. The
assumptions of stable government policies, economic conditions may not hold
true after 60 days.
1.7 Risks
The following risks have been identified as possibly affecting the project during its progression:
#
1
2
3
4
#
1
Risk Area
Economic
Downturns
2 Technology
Risk
Probability**
Impact**
Probability*Impact
Fluctuating
real estate
prices
Hardware
Low
High
High
High
High
Critical
Changes
& Software
Upgrades
3 Technology Decreasing
Changes
IT Infra
Cost
4 Governme
Delay in
nt
Company
Processes
Registratio
n
5
Project
Vendors not
Schedule
meeting
deadlines
Med
High
High
High
Med
Medium
Low
High
High
These are some risks that can occur during all phases of development
SOFTWARE REQUIREMENT RISKS
Lack of analysis for change of requirements
Change extension of requirements
Lack of report for requirements Poor definition of requirements
Ambiguity of requirements Change of requirements
Inadequate of requirements Impossible requirements
Invalid requirements
SOFTWARE COST RISKS
Lack of good estimation in projects Unrealistic schedule
The hardware does not work well Human errors
Lack of testing and monitoring
Lack of monitoring
Complexity of architecture Large size of architecture
Extension of requirements change The tools does not work well
Personnel change Management change
Software/Hardware
It is a predictable suite of hardware and software that will be required to successfully run
the information system.
Web-based Mapping
One of the major predictable component of IS will be a web based application, or some
sort of connectivity that makes this information system available over the web.
Connectivity with the server is required.
Standards/Procedures
Promoting standards will ensure reliability, consistency and quality of the information
system. Promoting procedures will also ensure a consistent approach.
Information Systems data maintenance and application development will reduce overall
costs in the long run.
Types of standards and procedures generally comprise of software standards, metadata
standards,
application
development
environment
standards
and
data
development/maintenance standards.
Application Development Capability
It will not be possible to fulfill all IS needs through commercial off-the-shelf(COTS)
applications; hence, it will be required to develop an application development
environment to tackle additional needs as new systems are developed and requirements
are updated.
Initiate Project
Develop Project
Charter
Define Scope
Define
Requirements
Develop Work
Plan
Develop
Work
Breakdow
n
Develop
Project
Staffing
Plan
Develop
Project
Schedule
Develop
Project
Budget
Finalize Charter
Execute and
Control Project
Plan Project
Develop Project
Control Plan
Develop
Communicatio
n Plan
Develop
Quality
Management
Plan
Finalize Project
Plan and Gain
Approvals
Design the
Framework
Build the
Framework
Close the
Project
Test the
Framework
Define
stages
and
activities
Write the
content
Test
web tool
usability
Design
Content
formats
Review
content for
quality
Test
content
usability
Design
web
Delivery
Tool
Build web
tool
prototype
Adjust tool
and
content
based on
feedback
Implement the
Framework
Conduct
post
project
review
Move web
tool to
production
Celebrate
environment
Announce
Tool
availability
Role Requirements
The following table is a comprehensive breakdown of the roles needed to deploy the
project. It includes: the project role, skills required, the project responsibility of the role,
the estimated start date, number of staff needed to fulfill the role, and the anticipated
duration the staff resource will be required on the project.
Role
Project Responsibility
Skills Required
Number of
Staff Required
Project Team
System Analyst
To analyze requirements,
interaction with client and team
Good Communication
and Analytical Skills
Project Manager
Project Management
Core Team
Project Management
Content Developer
Web Designer
Web Developer
DBA
System Administrator
Administration and
Management
Review Team
Project Management
experience
20
Name
Requested
FTE
FY12-13
Acquired
FTE
FY12-13
Rate
Rate
Unit
Source
Project Team
System
Analyst
Name1
Project
Manager
Name2 Project
Manager
Core Team
1.00
1.00
1.00
1.00
Name3
.10
.10
Name4
.10
.10
Name5
.10
.10
Name6
.10
.10
Name7
.90
.90
.05
.05
Web
Developer
Name9
.05
.00
DBA
Name 10
1.00
1.00
Content
Developer
Role
Name
System
Name 11
Administrator
Review Team
Total
Various
Project
Managers
Requested
FTE
FY12-13
1.00
Acquired
FTE
FY12-13
1.00
Rate
Rate
Unit
Source
.10
.10
5.5
5.45
Management
Organization
Office
Stakeholder
Round Table
Stakeholder
Operations
Directors
Project Sponsor
Name1 - Project
Sponsor/Analyst
Stakeholder
Tech
Directors
Project Manager
Name 2 - Project
Manager
Stakeholder
MTeam
Project Team
Core Team
Name 3: Network
Services
Name 4:
Enterprise
Internet
Services
Name5/Name6:
Resource
Management
Technologies
Content
Developer
Name7
Data Resource
Management
Technologies
and Web
Academic
Technology
Solutions
Web
Designer
Name8
Academic
Technology
Solutions
Web
Developer
Name9
Data
Management
DBA
Name 10
Network and
Security
Management
System
Administrator
Name 11
Manage
and
Review
Project
Reviewers
Project Management
Improvement Project Phase 1
1
1.1
1.1.1
Define Requirements
1.1.3
1.1.4
1.1.5
1.1.6.2
1.1.6.3
1.1.6.4
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.2
2.2.1
2.2.2
2.3
3
3.1
3.1.1
3.1.2
3.1.3
3.2
3.2.1
3.2.2
Planned
Start
Date
Planned
End
Date
4.00
7/12/12
11/12/12
3.00
12/12/12
14/12/12
0.25
14/12/12
14/12/12
1.00
14/12/12
15/12/12
0.50
2.00
1512/12
16/12/12
15/12/12
17/12/12
1.00
0.50
0.50
0.50
18/12/12
19/12/12
19/12/12
20/12/12
18/12/12
19/12/12
19/12/12
20/12/12
2.00
2.00
3.00
3.00
21/12/12
23/12/12
25/12/12
28/12/12/
22/12/12
24/12/12
27/12/12
31/12/12
1.50
1.50
1/1/13
2/1/13
2/1/13
3/1/13
5.00
4/1/13
6/1/13
5.00
1.00
2.00
7/1/13
12/1/13
13/1/13
11/1/13
12/1/13
14/1/13
5
3
15/1/13
20/1/13
19/1/13
22/1/13
Name7
Name1 - Project Manager, core
Initiate Project
Develop Project Charter
Define Scope
1.1.2
1.1.6
1.1.6.1
Effort
Estimate in
Days
Plan Project
Develop Work Plan
Develop Work Breakdown Structure
Develop Project Staffing Plan
Develop Project Schedule
Develop Project Budget
Develop Project Control Plan
Develop Communication Plan
Develop Quality Management Plan
Finalize Project Plan and Gain
Approvals
Execute and Control Project
Design Framework
Define framework stages and
activities
Design framework content formats
Design web framework delivery tool
Build the Framework
Write the framework content
Review framework content for
Resource
Project Management
Improvement Project Phase 1
3.2.3
3.3
3.3.1
3.3.2
3.3.3
3.4
3.4.1
3.4.2
4
4.1
4.2
quality
Build web tool prototype
Test the Framework
Test usability of web tool
Test usability of content
Adjust framework based on user
feedback
Implement Framework
Move framework to production
environment
Announce availability of framework
Close the Project
Conduct Post-Project Review
Effort
Estimate in
Days
Planned
Start
Date
Planned
End
Date
5.00
23/1/13
27/1/13
2.00
1.00
28/1/13
30/1/13
29/1/13
30/1/13
1.00
31/1/13
31/1/13
Name7, Name8
1.00
0.50
1/2/13/
2/12/13
1/12/13
2/12/13
1.00
2/12/13
2/12/13
0.50
3/12/13/
3/12/13
Celebrate
Resource
Line Item
FY12-13
Labor
Phase I
1. Initiate Project
1.1 Develop Project Charter
2. Plan the Project
2.1 Develop Work Plan
2.2 Develop Project Control Plan
2.3 Finalize Project Plan
3. Execute and Control Project
3.1 Design Framework
3.2 Build Framework
3.3 Test the Framework
3.4 Implement the Framework
4. Close the Project
Total
$172,100
FY12-13
Material
Other
FY Total
Labor
Material
Other
FY Total
$8,600
$0
$8,600
$0
$0
$0
$0
$15,000
$5,000
$0
0
$15,000
$5,000
2,000
$0
$0
$0
$0
$0
$2,000
$0
$5,000
$65,000
$30,000
$0
$0
$0
$0
$0
$0
$0
$2000
$0
$0
$0
$5,000
$67,000
$30,000
$0
$0
20,000
10,000
$4,500
$5,000
$0
$0
$0
$0
$0
$0
$0
$0
$20,000
$10,000
$4,500
$5,000
$128,600
$0
$2,000
$130,600
$41,500
$0
$0
$41,500
Comments: Other is the budget estimate for a training class: Effective Writing for the Web
3. Solution Provider
IBM - Smarter Analytics is one of the most renowned analytical tools available in the
market today. It is developed and maintained by IBM and also has proven track record in
the market. It is suitable for various types of industries and can integrate in nearly all
business operations.
Tools based on CMOS technology should be used, so that the data can be analyzed at a
faster rate. These tools are very compact in size.
The system can be integrated with cloud computing techniques. In this technique the data
is stored at a remote server which is managed by the third party service providers. So
there is no need to manage the data. It is the responsibility of the service providers. So it
helps in saving the cost. The charges are Pay per use. So there is no need to pay for the
complete service.
Classification of Data
Any companys user having authoritative access to data of the company may, modify
datas classification. The user may be in a position to change classification of data if there
are sufficient and justifiable reasons of doing so. Resources doing so will be held strictly
responsible for their changes. When a new data is created, it should be classified as
Company Only data till it user reclassifies it as per ones modifications. Users are held
strictly for any change in classification they do.
Classifications for existing company data are given below:
Know ones own clearance level and to understand what are the rights
and limitations associated with that clearance
Ensure one is familiar with the restrictions associated with the data
ones working on and
Compliance
Appendix
References:
1. Ferris, B. (n.d.). Why Do We Need a Project Schedule. Retrieved from
http://cobaltpm.com.
2. Haughey, D. (n.d.). Project Planning a Step by Step Guide. Retrieved from
http://www.projectsmart.co.uk/.
3. John Baker, A. E. (n.d.). Cost - Benefit analysis essential to IT projects . Retrieved
from http://www.gisdevelopment.net/.
4. rff.com. (n.d.). Gantt Charts and Project Schedules. Retrieved from
http://www.rff.com/ganttcharts.htm.
5. sei.cmu.edu. (n.d.). Cost Benefit Analysis Method. Retrieved from
http://www.sei.cmu.edu.