PROJECT MANAGEMENT PLANS 1 PROJECT MANAGEMENT PLANS 11 Critical Success Factors in Project Management PM 598 – PM Mgmt. Capstone - Week 3 May 31, 2016 A risk is a probability that loss, liability or a negative occurrence which may be caused by internal or external vulnerability and can be management through its identification, assessment, evaluation, control and monitoring (Cooper & International, 2005). Risk assessment is the phase of risk management which involves evaluating the potential risks that may occur in an activity which has been projected, during risk assessment one comes with a risk matrix by identifying all the possible risk which are then evaluated in terms of probability or likelihood of the risk and the severity of the impact it will have on the project, this is done by assigning rating and numeric figures to get the compounded risk score. The first step in project risk management planning is risk identification; this is where you identify those risks which are likely to occur during the EOS-RSA Authentication Server Upgrade. This is the occurrences which could manifest themselves during the project and affect its performance (Cooper, 2014). The following risks are likely to occur during the EOS-RSA Authentication Server Upgrade project; schedule risks i.e. project wrong time estimation, budget risks i.e. cost overruns, operation failure risks i.e. insufficient resources, technical risks i.e. continuous change of project requirements, programmatic risks, in this case, a good example is running out of fund or resources among others. After the risk are identified to complete the matrix, the risks should be quantified by assigning them numeric ratings depending on the frequency or the likelihood that they can occur and also the severity or the impact they can have on the EOS-RSA Authentication Server Upgrade project if the risks occur. As the project manager, I will use a scale between 1 and 10 to rate the likelihood that the risk can occur, a rating of 1 means that there is a low likelihood that the risk will occur where a rating of 10 means that a risk has a high probability of occurrence to the project. A good example from the identified risk wrong time estimation have a rating of 8 while running out of fund has a rating of 2 this means that wrong time estimation risk have a high probability of occurrence compared to the risk of the project running out of the fund. On the impact or the severity of the risk to the EOS-RSA Authentication Server Upgrade project the small scale have been used to rate the impact the risk will have on the project, a rating of 1 means the risk have less or no impact on the project while a rating of 10 means that the risk will have fatal effects on the project which could mean the project fails to deliver its objectives or takes more time and fund than have been allocated, an example from the matrix table continuous change of requirement have a rating scale of 3 while insufficient resources r.

1. PROJECT MANAGEMENT PLANS
1
PROJECT MANAGEMENT PLANS
11
Critical Success Factors in Project Management
PM 598 – PM Mgmt. Capstone - Week 3
May 31, 2016
A risk is a probability that loss, liability or a negative
occurrence which may be caused by internal or external
vulnerability and can be management through its identification,
assessment, evaluation, control and monitoring (Cooper &
International, 2005). Risk assessment is the phase of risk
management which involves evaluating the potential risks that
may occur in an activity which has been projected, during risk
assessment one comes with a risk matrix by identifying all the
possible risk which are then evaluated in terms of probability or
likelihood of the risk and the severity of the impact it will have
on the project, this is done by assigning rating and numeric
figures to get the compounded risk score.
The first step in project risk management planning is risk
identification; this is where you identify those risks which are
likely to occur during the EOS-RSA Authentication Server
Upgrade. This is the occurrences which could manifest
themselves during the project and affect its performance
(Cooper, 2014). The following risks are likely to occur during
the EOS-RSA Authentication Server Upgrade project; schedule
risks i.e. project wrong time estimation, budget risks i.e. cost

2. overruns, operation failure risks i.e. insufficient resources,
technical risks i.e. continuous change of project requirements,
programmatic risks, in this case, a good example is running out
of fund or resources among others.
After the risk are identified to complete the matrix, the risks
should be quantified by assigning them numeric ratings
depending on the frequency or the likelihood that they can
occur and also the severity or the impact they can have on the
EOS-RSA Authentication Server Upgrade project if the risks
occur. As the project manager, I will use a scale between 1 and
10 to rate the likelihood that the risk can occur, a rating of 1
means that there is a low likelihood that the risk will occur
where a rating of 10 means that a risk has a high probability of
occurrence to the project. A good example from the identified
risk wrong time estimation have a rating of 8 while running out
of fund has a rating of 2 this means that wrong time estimation
risk have a high probability of occurrence compared to the risk
of the project running out of the fund. On the impact or the
severity of the risk to the EOS-RSA Authentication Server
Upgrade project the small scale have been used to rate the
impact the risk will have on the project, a rating of 1 means the
risk have less or no impact on the project while a rating of 10
means that the risk will have fatal effects on the project which
could mean the project fails to deliver its objectives or takes
more time and fund than have been allocated, an example from
the matrix table continuous change of requirement have a rating
scale of 3 while insufficient resources risk have an impact scale
of 8 this means insufficient resources will have fatal effects to
the EOS-RSA Authentication Server project success. The risk
assessment score is calculated by multiplying the risk impact
and its probability numerical scales (Aven, 2015).
Below is a table showing the various risks, probability, impact,
assessment score and the project team response about the risk.
Risk Title
Probability

3. Impact
Assessment score
Response
Wrong time estimation
8
4
32
This risk is the one which is likely to occur to the project and
can bring about the project completion date occurring in later
dates since the project will take more time than what was
initially planned and it can remedied by correct estimation and
duration adjustments.
Cost overruns
5
6
30
This where the project will spend more than what was initially
planned, this risk can be managed by requesting for more
resources from the project sponsor.
Insufficient resources
3
9
27
Project activities are already in progress but there are no
resources to undertake the activities this can be mitigated by
securing the required resources before the project kickoff.
Requirements changes
6
4
24
Bring about failure in project productivity and performance
since the project requirements changes. This can be minimized
by project users involvement and documentation of
requirements specification
Running out of funds
3

4. 8
24
Project uses more than what the sponsor have provided making
it not to run to completion, this can be addressed by setting
aside more funds for the project
Project human resource management plans are required for the
most important resource to the project is its resources. EOS-
RSA Authentication Server Upgrade project requires specific
expertise which may not be available with the current
employees and if it is available the current employees may be
handling multiple projects which cannot do without his or her
expertise. The project also might require specific talents which
can only be acquired through contracting or from other third
party vendors. To fulfill the human resource needs the first is to
document the EOS-RSA Authentication Server Upgrade project
responsibilities and roles for various project stakeholders.
An organization chart is developed for all project teams
members with the main purpose is each member to know his
role and responsibility and what type of staffing requirement is
needed and at when is it needed. A staffing management plan is
developed to determine how the human resources were to be
brought to the project and how it was to be taken out of the
project team. The next step was staff acquisition which was
done by the HR staff which acquires the necessary staff by
considering previous experience, availability, interests,
competencies and proficiency, example Kun Jiang was acquired
through this process because he had more experience in
development in project related to EOS-RSA Authentication
Server Upgrade.
After acquiring the required staff, there was a need for team
development to enhance team’s ability to contribute as a team
and as an individual. The acquired staff will be trained by the
senior stakeholders who have experience with projects similar
to EOS-RSA Authentication Server Upgrade project and also the
staff will be supposed to attend a seminar about the current

5. project for more training, they will also undertake a physical
team building activity. To improve the performance of the
project stakeholders and team the Human Resource Manager
will reward the stakeholders based on the specific goals which
have been achieved, a bonus amount agreed by project team was
to be paid to project members who achieve their objectives and
targets in the agreed time and also a stakeholder who stayed
worked over time will be provided with extra money for the
extra time he had worked.
A project management communication plan is required in every
project, failure to communicate have been a great threat to
project success, strong communication skills are required to
ensure effective flow of information among all the project
stakeholders. To ensure effective communication between all
the project life cycle a communication planning need to done,
the plan should determine the communication and information
needs of the various stakeholders, coming up with ways to
ensure that the needed information by the stakeholders is
available to them in a timely manner, Collecting and
distributing project performance information which includes
progress reports, measured progress and forecasting.
According to (Collins, 2011)stakeholders are those individuals,
organization, group who are directly affected by the project
decision; every project have its own specific stakeholders and
EOS-RSA Authentication Server Upgrade project have the
following project stakeholders; sponsor who is the Bank of
Tokyo who is also the owner of the project, the project manager
who is responsible for planning, coordinating, decision making
for the project, customers and users who will be using the
upgraded EOS-RSA Authentication Server, HR staff who are
responsible for acquiring the extra staff needed for project
completion, Suppliers who will bring the resources for the
project which are not available at the organization, Project team
this include the developers and the designers who perform

6. various activities and tasks in the project, support staff
examples include the procurement officers.
Below is a table showing information produced during project
life cycle
Document/Information
Audience
Availability
Communication mode
Produced by
Project charter
Sponsor
Once
Hardcopy
Project manager
Budget
Sponsor
Once, on Request
Hardcopy
Project manager
Work breakdown Structure
Project team, Sponsor
Weekly
Hardcopy, Email
Project manager
Progress report
Sponsor
On request, Weekly
Hard copy, Email
Project Manager
Status report
Project team
Bi-weekly
Emails, Meetings
Project Manager
Project schedule

7. Sponsor, Project team
Weekly
Email
Project Manager
Change requests
Project Team, Sponsor
On request
Meetings, Hardcopy
Project Manager, Stakeholder
Performance indicators
Project team, Sponsor
Weekly
Email
Project Manager
Project report
Sponsor
Once
Hardcopy
Project Manager
Project procurement means acquiring services and goods that
the organization does not have and are required by the project
(Tracy, 2013). Project procurement has been important to the
project since it allows the project stakeholders to focus on the
core business of the project, it helps the project to access
services and technologies that the organization does not have
currently. Project procurement plan involves the following;
planning purchases and acquisition which is identifying those
services that EOS-RSA Authentication Server Upgrade project
requires, the second step is contract planning where you
identify potential sellers of the project, obtaining quotes, bids
and proposals from the sellers, selecting the sellers by
evaluating and negotiate the contract.
There are various methods, tools and techniques which can be
used manage procurement in the project they include; make-or-
buy analysis this is a method that is used to determine whether

8. an organization should make a particular project inside the
organization or should they buy it from an outside source
(Institute, 2004), this method helps the project management
team to decide whether it is beneficial in terms of quality and
cost to procure a service or produce it within the organization.
The second method to be used in procurement management plan
is market research which includes project team examining the
industry for specific vendors offering a certain product or
service; this information can be got through conferences, online
reviews and other ways to identify the capability of the market.
The other method is expert judgment where experts inside and
outside provide valuable decisions and advice in procuring of
services and products.
A contract is mutual binding agreement that obligates the seller
of a certain product or services to provide and the project's
owners to pay for the services which have been provided; the
contracts ensures there is accountability and responsibilities in
the parties involved. There are various contract vehicles which
project team can use during procurement of product and
services the best one for EOS-RSA Authentication Server
Upgrade would be the firm fixed price contract (FFP) which is a
subdivision of fixed price contract (Fleming, 2003), the main
reason for using Firm Fixed Price Contract is because the fee of
the products are known and the seller has to deliver the products
in the agreed time and money. Any cost incurred by the project
due to the sellers' bad performance will be his responsibility, an
example a seller has to deliver two new servers for $200,000
within two weeks and install them.
REFERENCES
Aven, T. (2015). Risk analysis. Chichester, West Sussex, United
Kingdom: John Wiley & Sons.
Collins, R. J. (2011). Project management. New York: Nova

9. Science Publishers.
Cooper, D. F. (2014). Project risk management guidelines ;
managing risk with ISO 31000 and IEC 62198. Hoboken, New
Jersey: John Wiley and Sons, Inc.
Cooper, D. F., & International, B. C. (2005). Project risk
management guidelines : managing risk in large projects and
complex procurements. West Sussex, England ; Hoboken, NJ: J.
Wiley.
Fleming, Q. W. (2003). Project procurement management :
contracting, subcontracting, teaming. Tustin, California: FMC
Press.
Institute, P. M. (2004). A guide to Project management body of
knowledge(PMBOK) . Newtown Square, Pa.: Project
Management Institute.
Tracy, J. (2013). PMBOK guide. North Charleston, South
Carolina: CreateSpace Independant Publishing Platform.
1[OA] Signature Assignment: Project Management Plan 100%
1Project Risks (10%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
2Project Risk Assessment (10%)

10. Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
3Needs Acquisition (10%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
4Training & Recognition (10%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
5Stakeholder Groups (10%)

11. Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
6Project Communication Plan (10%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
7Procurement Management (5%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
8Contract Vehicle (5%)

12. Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
9The paper is organized in a logical and coherent manner.
Transitions are used to improved flow.(10%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
10Valid research is used to appropriately support the content.
References to sources are used when required. (10%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form

13. 11The author uses correct grammar and spelling. Format and
citations are consistent with APA rules. (10%)
Does Not Meet Expectations
Approaches Expectations
Meets Expectations
Exceeds Expectations
Top of Form
Feedback
Bottom of Form
Break-Even Sales Under Present and Proposed Conditions
Battonkill Company, operating at full capacity, sold 107,100
units at a price of $135 per unit during 2014. Its income
statement for 2014 is as follows:
Sales
$14,458,500
Cost of goods sold
5,130,000
Gross profit
$9,328,500
Expenses:
Selling expenses

14. $2,565,000
Administrative expenses
1,530,000
Total expenses
4,095,000
Income from operations
$5,233,500
The division of costs between fixed and variable is as follows:
Fixed
Variable
Cost of goods sold
40%
60%
Selling expenses
50%
50%
Administrative expenses
70%
30%
Management is considering a plant expansion program that will
permit an increase of $1,350,000 in yearly sales. The expansion

15. will increase fixed costs by $180,000, but will not affect the
relationship between sales and variable costs.
Required:
1. Determine for 2014 the total fixed costs and the total variable
costs.
Total fixed costs
$
Total variable costs
$
2. Determine for 2014 (a) the unit variable cost and (b) the unit
contribution margin.
Unit variable cost
$
Unit contribution margin
$
3. Compute the break-even sales (units) for 2014.
units
4. Compute the break-even sales (units) under the proposed
program.
units
5. Determine the amount of sales (units) that would be
necessary under the proposed program to realize the $5,233,500
of income from operations that was earned in 2014.
units
6. Determine the maximum income from operations possible
with the expanded plant.
$
7. If the proposal is accepted and sales remain at the 2014 level,
what will the income or loss from operations be for 2015?
$ SelectIncomeLossItem 10
8. Based on the data given, would you recommend accepting the
proposal?
In favor of the proposal because of the reduction in break-even
point.
In favor of the proposal because of the possibility of increasing
income from operations.

16. In favor of the proposal because of the increase in break-even
point.
Reject the proposal because if future sales remain at the 2014
level, the income from operations of will increase.
Reject the proposal because the sales necessary to maintain the
current income from operations would be below 2014 sales.
Choose the correct answer.
Selectabcde
EOS-RSA AUTHENTICATION SERVER UPGRADE
1
EOS-RSA AUTHENTICATION SERVER UPGRADE
12
EOS-RSA Authentication Server Upgrade
Project Scope, Schedule, and Budget
PM 598 – PM Mgmt. Capstone - Week 2
May 23, 2016
Project Description
The project End Of Support RSA Authentication servers is a
project by the Bank of Tokyo which has been started so that the
bank client’s and customer can have authentication services
which will enable them access the bank internet applications,
the RSA Authentication will also enable remote access through
a RSA securID token.

17. The project will also have a Helpdesk Administration Portal
which will enable Administrators to efficiently perform support
activities to internal users. Finally, the project will also have a
Standard Operating Procedure which will be used in approving
and deploying RSA securID Soft Tokens which will eliminate
cost associated with mailing or replacement of Hard Tokens to
Internal Users.
Problem & Result Statement
The current version of RSA comes to End-of-Support on
12/31/2016. In the event of an RSA failure that requires
technical support, customers will not be able to access Bank's
Internet-facing systems. Some of the remedy to the problem
statement will be:
· Reduce the RSA SecurID maintenance and RSA
Administration costs
· Enhance and automate the process of deploying RSA SecurID
· Building a RSA Architecture needed to support RSA SecurID
soft and hard token distribution
Project Justification
The Bank End-of-Support upgrade of the RSA environment was
done in order to leverage the Enterprise plus license so as to
reduce the cost of maintenance. The EOS-RSA Authentication
Server Upgrade Project is the best because it will lower the cost
of maintenance and also it will be able complete the activities
which were started by Alternate Web Hosting Project and it has
a RSA Architecture that will allow remote access to the
environment by internal and external customers. As compared to
other alternatives the EOS-RSA Authentication Server Upgrade

18. Project is the best one to minimize the cost and allow support
services to be efficiently performed.
Project Scope Statement
IN SCOPE
The following items are considered to be in scope for this
project:
· Complete the replacement and configurations of the RSA
Authentication Servers so that RSA Enterprise Plus Licenses
can be installed, which will reduce the overall RSA license
annual maintenance cost
· Provide a Self-Service Portal for internal users of the RSA
environment.
· Ensure that the portal can be accessed on all bank owned
devices, and on all bank approved personal devices
· Ensure that the self-service portal can be accessed on all bank
supported browsers and on all supported browser versions.
· Provide an Admin Portal for the Helpdesk to more efficiently
perform remote Internal User support activities
· Create a test environment so that future updates and fixes can
be tested without interrupting Production.
· Ensure no service interruption in the event of either a
Component or Data Center failure
OUT OF SCOPE
The following items are not within scope of this project:

19. · Implementing RSA Enterprise Plus licenses and a self-service
portal for MUB and ISA-West Coast users.
· Providing a self-service portal for external customers.
Out of scope items will be considered in future projects
Major Project Deliverables
· Install the remaining RSA Authentication Servers in both the
Harborside and Sterling Forest Data Centers
· Purchase new hardware and software for hosting a Self-
Service and Helpdesk Portal for Internal Users
· Leverage the Enterprise Plus License structure to reduce
license maintenance costs
· Install new RSA Self-Service Portals to reduce ongoing
administrative and overhead costs, and improve the end-user
experience of Internal Users
· Deploy a Self-Service Portal so that Internal Users working
remotely can reset their RSA Token PIN without having to call
the Helpdesk.
High level Milestones and significant event
The current high level milestones completion dates are as
follows:
Planning
July 6, 2016
Design
August 7, 2016
Build & Configure Portals
September 18, 2016
Testing-Portals
November 13, 2016
Implementation: Portals
December 14, 2016
Build & Configure Soft Tokens

20. January 15, 2017
Testing: Soft Tokens
February 5, 2017
Implementation: Soft Tokens
February 22, 2017
ID
Milestone
Planned Completion
3
Project Initiation Request (PIR) Approved
4/17/2016
4
Kick-Off Security Risk Assessment
04/29/16
6
Obtain Initial Security Assessment Cost Estimations
05/08/16
8
Create BRD
05/04/16
11
BRD Sign-Off
05/15/16
13
Complete Initial Security Risk Assessment Spreadsheet
05/08/16
14
Review initial Security Risk Assessment (RSA)
05/15/16
15
Scope Pentest & Technical Security Standard Requirements
05/29/16
17
Provide Final Security Risk Assessment Cost Estimations and
Quotes
06/05/16

21. 25
Create Project Plan Document
06/12/16
26
Create WBS & Resource Plan
06/11/16
28
RINGI (Budget) Approval
07/22/16
30
EIS Planning Activities for Remaining Project Phases
07/06/16
36
Design Phase
07/06/16
85
Development Phase
07/06/16
146
Testing Phase
05/13/16
180
Pre-Implementation Phase
07/06/16
Items
Amount
Expected Semester Payment Term
2016/1
2016/2
2017/1
Investment
Hardware Purchase
$91,883.23
$91,883.23

22. S/W Development (Ext'l Consultant)
$140,215.00
$107,615.00
$32,600.00
S/W Purchase
$220,524.44
$220,524.44
Other
$16,597.10
$16,597.10
S/W Development (ISA Resources)
$75,446.82
$50,342.09
$25,104.73
S/W Development (ISA Resources Mark-Up)
$6,395.98
$4,262.08
$2,133.90
Sub Total
$551,062.57
$491,223.94
$59,838.63
Expense
Sales Tax
$21,372.49
$21,372.49

23. Sub Total
$21,372.49
$21,372.49
Grand Total
$572,435.06
$512,596.43
$59,838.63
$0.00
Project Schedule
Task Name
Duration
Start
Finish
Resource Names
EOS-RSA Authentication Server Upgrade
55.86 days?
Fri 5/20/16
Fri 8/5/16
Planning Phase
55.86 days?
Fri 5/20/16
Fri 8/5/16
Preview Milestones
10.29 days
Fri 5/20/16
Fri 6/3/16
PIR Approved
0 days

24. Fri 5/20/16
Fri 5/20/16
Kick-off Security
0 days
Sun 5/22/16
Sun 5/22/16
Complete EIS SRE Questionnaire
2 days
Sun 5/22/16
Mon 5/23/16
Kun Jiang
Obtain Initial Security Assessment Cost Estimations
0 days
Thu 6/2/16
Thu 6/2/16
Business & Infrastructure Requirements
10.29 days
Mon 5/30/16
Mon 6/13/16
Create BRD
5 days
Mon 5/30/16
Fri 6/3/16
Peter Tse (Koon Hing Tse)
Review BRD with SOE Management
0 days
Mon 5/30/16
Mon 5/30/16
Review BRD with QA and Obtain Approval
0 days
Wed 6/1/16

25. Wed 6/1/16
BRD Sign-off in ePLC
0 days
Thu 6/2/16
Thu 6/2/16
EIS Planning Phase Requirements & Activities
26.71 days
Mon 5/30/16
Tue 7/5/16
Complete Initial Security Risk Assessment Spreadsheet
5 days
Mon 5/30/16
Fri 6/3/16
Roger Brinkley, Kun Jiang
Review Initial Security Risk Assessment(SRA)
0 days
Thu 6/9/16
Thu 6/9/16
Scope Pentest and Technical Security Standard
Requirements
10 days
Mon 6/13/16
Fri 6/24/16
Nikolay Belov
Scope BR and BCP Requirements
10 days
Mon 6/13/16
Fri 6/24/16
Peter Tse(Koon Hing Tse)
Provide Final Security Assessment Cost Estimations and
quotes
5 days

26. Sat 6/25/16
Thu 6/30/16
Nikolay Belov
SME Reviews
10.29 days?
Mon 6/13/16
Mon 6/27/16
Create High Level Design Document
7 days
Mon 6/13/16
Tue 6/21/16
Kun Jiang, Peter Tse(Koon Hing Tse)
Conduct SME High Level Design Review Meeting
3 days
Fri 6/17/16
Tue 6/21/16
Kun Jiang
Submit SME Summary Sheet in ePLC
0 days
Mon 6/20/16
Mon 6/20/16
Ringi
30.86 days
Mon 5/30/16
Mon 7/11/16
Document Approach, Testing and Migration Strategy for
Project planning
10 days
Mon 5/30/16
Fri 6/10/16
Kun Jiang, Peter Tse(Koon Hing Tse)
Obtain Cost Estimations & Quotes/SOWs
0 days

27. Fri 6/17/16
Fri 6/17/16
Create Project Plan Document and ePLC Deliverables
11 days
Wed 6/8/16
Wed 6/22/16
Create WBS and Resource Plan for Phase 2 to Phase 5
10 days
Wed 6/8/16
Tue 6/21/16
Submit Project Ringi
0 days
Mon 6/20/16
Mon 6/20/16
Ringi Local Approval in ePLC
0 days
Sat 7/2/16
Sat 7/2/16
Planning Activities for Remaining Project Phases
17 days
Sat 6/25/16
Mon 7/18/16
Kun Jiang, Peter Tse(Koon Hing Tse)
EIS Planning Activities for Remaining Project Phases
17 days
Sat 6/25/16
Mon 7/18/16
Nikolay Belov, Philip Norman
End of Planning Phase
0 days
Sun 7/17/16

28. Sun 7/17/16
Design Phase
1 day
Tue 8/2/16
Tue 8/2/16
Development Phase
1 day
Tue 8/2/16
Tue 8/2/16
Testing Phase
1 day
Tue 8/2/16
Tue 8/2/16
Pre-Implementation
0
Tue 8/2/16
Tue 8/2/16
Time-Phase Budget
Planning phase
Design Phase
Implementation
May-16
Jun-16

29. Jul-16
Aug-16
TOTAL
DIRECT COST
Supplies
$ 5,000.00
$ 3,000.00
$ 1,000.00
$ 1,000.00
$ 10,000.00
Developers salaries
$ 40,000.00
$ 40,000.00
$ 20,000.00
$ 20,000.00
$ 120,000.00
Materials
$ 100,000.00
$ 80,000.00
$ 180,000.00
Equipment
$ 10,000.00
$ 10,000.00
$ 90,000.00
$ 110,000.00
Consultancy cost
$ 2,000.00

30. $ 3,000.00
$ 4,000.00
$ 9,000.00
Travel expenses
$ 1,000.00
$ 2,000.00
$ 1,000.00
$ 4,000.00
Communication cost
$ 1,000.00
$ 500.00
$ 750.00
$ 1,000.00
$ 3,250.00
INDIRECT COST
Administration expenses
$ 5,000.00
$ 5,000.00
$ 5,000.00
$ 5,000.00
$ 20,000.00
Stakeholders Salaries
$ 2,500.00
$ 2,000.00

31. $ 2,000.00
$ 2,000.00
$ 8,500.00
Legal cost
$ 1,000.00
$ 500.00
$ 500.00
$ 500.00
$ 2,500.00
CUMULATIVE COST
$ 55,500.00
$ 165,000.00
$ 122,250.00
$124,500.00
$ 467,250.00
Work Breakdown Structure (Howard, 2013)
REFERENCES
Howard, B. (2013). Microsoft Project 2013. Sebastopol,
California : O'Reilly Media.
Kerzner, H. (2001). Project management : a systems approach to
planning, scheduling, and controlling. New York: John Wiley.

32. Mehta, R. C. (2007). Project management. Jaipur: Aavishkar
Publishers.
Grading Guide
Content
Met
Partially Met
Not Met
Comments:
Project scope is refined from Week 1’s charter.
X
A work breakdown structure is created.
X
WBS looks great.
A project schedule and budget is created.
X
A schedule is created for the project lifecycle in Microsoft®
Project®.
X
The schedule is a good start. There are multiple levels. The
task durations appear to be reasonable. Predecessor information
needs to be setup for all tasks. Resources are defined and

33. assigned.
Specific tasks and milestones are included with time and
resource estimates.
X
A time-phased budget is created using Microsoft® Excel®
Using Microsoft® Excel®, create a time-phased budget
containing cost estimates. Include direct and indirect costs for
labor, machinery, equipment, supplies, and other elements
applicable to the project.
X
The budget is contained within Project.
Total Available
Total Earned
7
6.5
Writing Guidelines
Met
Partially Met
Not Met
Comments:
The paper—including tables and graphs, headings, title page,

34. and reference page—is consistent with APA formatting
guidelines and meets course-level requirements.
X
Intellectual property is recognized with in-text citations and a
reference page.
X
.
Paragraph and sentence transitions are present, logical, and
maintain the flow throughout the paper.
X
Sentences are complete, clear, and concise.
X
Rules of grammar and usage are followed including spelling and
punctuation.
X
Total Available
Total Earned

35. 3
3
Assignment Total
#
10
9.5
Additional comments:
Great work!
PROJECT CHARTER
Project Charter: End of Support RSA Authentication Servers
05.10.2016
Project Charter
PM 598 – PM Mgmt. Capstone - Week 1
May 16, 2016
Project Name: End of Support (EOD) RSA Authentication
Servers
Project Manager: Twanna Perkins
Project Start: 07/06/2016
Project End: 05/15/2017
Business Case:
The RSA EOS Hardware Upgrade project is an ISA initiated
effort. The RSA environment supports internal user and
external user authentication for remote access. The RSA
Authentication Servers reached End of Support on December 31,

36. 2014, and were replaced as part of the Alternative Web Hosting
project. However, EOS upgrade activities were not fully
completed due to that project’s budget and resource constraints.
Business Driver
Relevant?
Describe
Audit
No
Business Promotion
Yes
Will keep vendor applications current and available for business
purposes.
Cost Reduction
Yes
Moving to an Enterprise Plus License structure will reduce the
overall annual maintenance cost.
Head Office Initiative
No
IT Infrastructure
Yes

37. This is an ISA/SOE initiative
Regulatory
No
Risk Management
No
Upgrade
Yes
Complete remaining EOS Upgrade activities that were not fully
completed during the Alternate Web Hosting project
Narrative Project Description/Background
End-Of-Support (EOS): To provide authentication service for
customers to access Bank's Internet-facing applications, and
staff to remotely access the bank's network.
Problem & Result Statement
The current version of RSA comes to End-of-Support on
12/31/2016. In the event of an RSA failure that requires
technical support, customers will not be able to access Bank's
Internet-facing systems, and staff will not be able to remotely
access (VPN) Bank's resources.
Mission Justification
The Bank needs to complete the EOS upgrade of the RSA
environment in order to leverage the Enterprise Plus License
structure which will reduce the overall annual maintenance cost.

38. Project Scope Statement
The following items are considered to be in scope for this
project:
•
Complete the replacement and configurations of the RSA
Authentication Servers so that RSA Enterprise Plus Licenses
can be installed, which will reduce the overall RSA license
annual maintenance cost
•
Provide a Self-Service Portal for internal users of the RSA
environment.
•
Ensure that the portal can be accessed on all bank owned
devices, and on all bank approved personal devices
•
Ensure that the self-service portal can be accessed on all bank
supported browsers and on all supported browser versions.
•
Provide an Admin Portal for the Helpdesk to more efficiently
perform remote Internal User support activities
•
Create a test environment so that future updates and fixes can
be tested without interrupting Production.
•
Ensure no service interruption in the event of either a
Component or Data Center failure
The following items are not within scope of this project:

39. •
Implementing RSA Enterprise Plus licenses and a self-service
portal for MUB and ISA-West Coast users.
•
Providing a self-service portal for external customers.
The following items are not within scope of this project:
· Implementing RSA Enterprise Plus licenses and a self-service
portal for MUB and ISA-West Coast users.
· Providing a self-service portal for external customers.
Major Deliverables/Goals
· Install the remaining RSA Authentication Servers in both the
Harborside and Sterling Forest Data Centers
· Purchase new hardware and software for hosting a Self-
Service and Helpdesk Portal for Internal Users
· Leverage the Enterprise Plus License structure to reduce
license maintenance costs
· Install new RSA Self-Service Portals to reduce ongoing
administrative and overhead costs, and improve the end-user
experience of Internal Users
· Deploy a Self-Service Portal so that Internal Users working
remotely can reset their RSA Token PIN without having to call
the Helpdesk.
Key Stakeholders
Client
The Bank
Sponsor
John Doe
Project Manager

40. Twanna Perkins
Project Team Members
Martina Scott, Valeria Gomez, Daniel Schmidt
High-Level Project Milestones& Significant Events
Current high level milestone completion dates are as follows:
Planning
July 6, 2016
Design
August 7, 2016
Build & Configure Portals
September 18, 2016
Testing-Portals
November 13, 2016
Implementation: Portals
December 14, 2016
Build & Configure Soft Tokens
January 15, 2017
Testing: Soft Tokens
February 5, 2017
Implementation: Soft Tokens
February 22, 2017
ID
Milestone
Planned Completion
3
Project Initiation Request (PIR) Approved
4/17/2016
4
Kick-Off Security Risk Assessment
04/29/16
6

41. Obtain Initial Security Assessment Cost Estimations
05/08/16
8
Create BRD
05/04/16
11
BRD Sign-Off
05/15/16
13
Complete Initial Security Risk Assessment Spreadsheet
05/08/16
14
Review initial Security Risk Assessment (RSA)
05/15/16
15
Scope Pentest & Technical Security Standard Requirements
05/29/16
17
Provide Final Security Risk Assessment Cost Estimations and
Quotes
06/05/16
25
Create Project Plan Document
06/12/16
26
Create WBS & Resource Plan
06/11/16
28
RINGI (Budget) Approval
07/22/16
30
EIS Planning Activities for Remaining Project Phases
07/06/16
36
Design Phase
07/06/16

42. 85
Development Phase
07/06/16
146
Testing Phase
05/13/16
180
Pre-Implementation Phase
07/06/16
Project Budget
Items
Amount
Expected Semester Payment Term
2016/1
2016/2
2017/1
Investment
Hardware Purchase
$91,883.23
$91,883.23
S/W Development (Ext'l Consultant)
$140,215.00
$107,615.00
$32,600.00
S/W Purchase
$220,524.44
$220,524.44
Other

43. $16,597.10
$16,597.10
S/W Development (ISA Resources)
$75,446.82
$50,342.09
$25,104.73
S/W Development (ISA Resources Mark-Up)
$6,395.98
$4,262.08
$2,133.90
Sub Total
$551,062.57
$491,223.94
$59,838.63
Expense
Sales Tax
$21,372.49
$21,372.49
Sub Total
$21,372.49
$21,372.49
Grand Total
$572,435.06
$512,596.43
$59,838.63
$0.00
Technical Requirements, Constraints, Assumptions, Risks and

44. Dependencies
Technical Requirements
· N/A
Constraints
· N/A
Assumptions
· Core Banking has provided approval for upgrade migration
· Funding has been approved and allocated
· Necessary resources are available to complete tasks
Risks
· If RSA fails and technical support is required, customers will
not be able to access Bank's Internet-facing systems, and staff
will not be able to remotely access (VPN) Bank's resources
Dependencies
· Core Banking must provide approval prior to the scheduled
December 14, 2016 implementation of the Self-Service Portal.
· The Ringi (budget) must be approved by June 29, 2016 so that
the Enterprise Plus Licenses can be purchased with the
favorable discount which expires on June 30, 2016
Approval Signatures
[Name], Project Client
[Name], Project Sponsor
[Name], Project Manager
Content
Met

45. Partially Met
Not Met
Comments:
A project charter is developed.
X
The paper contains some of the required elements.
Narrative project description is included.
X
This section is underdeveloped.
Problem and result statement included.
X
This section is underdeveloped.
Mission justification is included.
X
This section is underdeveloped.
Project scope statement is provided.
X
Major deliverables are added.
X
Be sure to clearly identify deliverables. Deliverables and goals
are two separate things.

46. High-level milestones are included for significant events.
X
Applicable technical requirements, assumptions, or constraints
are provided.
X
The paper is 700- to 1,050 words in length.
X
Total Available
Total Earned
5.5
4.5
Writing Guidelines
Met
Partially Met
Not Met
Comments:
The paper—including tables and graphs, headings, title page,

47. and reference page—is consistent with APA formatting
guidelines and meets course-level requirements.
X
Text should be double spaced.
Intellectual property is recognized with in-text citations and a
reference page.
X
All writing assignments required sources.
Paragraph and sentence transitions are present, logical, and
maintain the flow throughout the paper.
X
Sentences are complete, clear, and concise.
X
Rules of grammar and usage are followed including spelling and
punctuation.
X
There are few, if any errors in spelling and grammar.
Total Available
Total Earned

48. 2.5
1.75
Assignment Total
#
8
6.25
Additional comments:
This is a great project to use throughout this course. Be sure
to clearly identify each requirement within your work and
address every requirement.
�Text should be double spaced.
�What is proposed to remedy the problem?
�This section should explain why this project is the best option
to remedy the problem.
The Project Charter Form is created for you by the simple
project management tool www.casual.pm
_1524662581.unknown
_1524662580.unknown