Milestone 3 Hightower Global Solutions
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
QSO 640
Subject
Information Systems
Date
Jan 9, 2024
Type
docx
Pages
16
Uploaded by MateAtomOctopus26
Running head: MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS CASE STUDY
1
Milestone 3: Hightower Global Solutions Case Study
Dennis Puyarena
Southern New Hampshire University
QSO 640 – Project Management
April 2, 2023
Dr. Tony Allen
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
2
Project Initiation
Hightower Global Solutions, a fortune 500 company specializing in financial services technology and outsourcing solutions (MindEdge, 2014). They possess an aggressive acquisition strategy that has contributed to the expansion of their product portfolio by buying small companies (MindEdge, 2014). Hightower has over 100 complex products and services offered to
a diverse client base, all of which the sales associates are tasked with tracking in order to successfully pitch products at the right opportunity. Both, new and experienced employees struggled with staying current on all of the company’s offerings, and sales leadership was concerned that they were missing opportunities to pitch new products (MindEdge, 2014). This project consisted in developing a "sales training intranet" (code named HighLEARN) for Hightower's 350 geographically dispersed sales associates to remedy this issue.
Connecting the employees via this method of training is crucial to safeguarding Hightower’s sustainability and success. Consequently, the project is feasible in all operational aspects including but not limited to economic, technical, and organizational. Proper training of employees impacts economic viability as it prepares employees to handle and be successful in meeting aggressive sales targets. With respect of technological viability, Hightower’s specialization in financial services technology is also impacted. In general this project aligns with Hightower as an organization given that they are a firm that specializes in financial services technology and outsourcing solutions globally. A global intranet platform goes hand in hand with
their business model.
Strategic Goal
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
3
To ensure Hightower’s success and sustainability in the global market, their strategic goals are to globally connect sales associates by means of an intranet platform to train all employees on Hightower’s diverse product offerings. With everyone in the sales becoming experts on as many products and services as possible, meeting the aggressive sales targets becomes attainable (MindEdge, 2014).
Project Charter
As previously mentioned, the organization’s strategic goal is to globally connect sales associates by means of the intranet, equipping them with expertise in the company’s diverse product offerings. This will ensure Hightower’s success and sustainability in the global market. Having everyone in the sales organization become experts on as many products and services as possible to meet aggressive sales targets (MindEdge, 2014)
Project Title
HighLearn
Date
June 1, 2019
Business Case
Organizational need, technological capability and economical need
Project Purpose
To create efficient and effective training program by means of an intranet platform where Hightower sales associates across the globe can log on and receive comprehensive product information and training
Project Objectives
To connect and train global sales associates from a singular intranet platform on the company’s diverse product portfolio with the purpose of meeting aggressive sales targets as well as ensure Hightower’s success and sustainability in the global market
Project Deliverables
1. 2.
Globally accessible intranet 3.
Comprehensive product information and presentations
4.
Access to webinars and videos with product specialist
5.
Share tips and feedback through blogs, forums and social features
Project Personnel
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
4
Tony DiBello
Project Manager
Ricardo Cortin
Director of Learning & Development
Steve Quan
HighTower IT Operations Specialist
Shannon Valley
Hightower IT Systems & Security
Monica Ianucci
Content Specialist
Jonathan Brant
Content Specialist
Risks
1. 2.
Website does not meet user requirements or functionality.
3.
Shannon Valley and Steve Quan are not available to contribute to the project until July 15, 2019.
4.
Marketing department has not endorsed the approach; believes they should go with Microsoft® SharePoint® system.
5.
Security of intranet/portal: no external access beyond firewall.
Schedule Summary
Project has a start date of June 1, 2019, with a roll-out date of January 1, 2020
Budget Summary
$1.5 Million
Measurable Success Criteria
1.
Develop highly interactive portal 2.
Custom intranet for global sales associates to log on and get comprehensive product information, presentations, access webinars and videos 3.
Access webinars and videos with product specialists and share tips and feedback through blogs, forums, and social features
Other Project Limitations
1. 2.
Aggressive timeline. 8-month build and roll-out date. 3.
Small project team to complete complex task list. 4.
3. Shannon and Steve are not available until July 15, 2019
Approval Signature
Approval Date
Carol Bailey
, CEO
4/1/2019
High-Level Timeline & Cost Estimations
Our task groups consist of four teams with multiple, high-level associated milestones. We
project completion of project in eight months from start date. These milestones are expected to be reached simultaneously.
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
5
TASK
RESPONSIBLE
MEMBER
Month 1
Month 2
Month 3
Month 4
Month 5
Month 6
Month 7
Month 8
Portal Development
User interface requirements
Ricardo Cortin
Visual design portal
Ricardo Cortin
Portal administration complete and accepted
Tony DiBello
Infrastructure & Security
Architecture approved for implementation
Shannon Valley
Servers for development, staging and production
Steve Quan
Integrate infrastructure & security systems
Steve Quan
Log-in systems complete and tested
Shannon Valley
Create user profiles and log-in credentials
Steve Quan
Content Creation & Editing
Product content modules complete and accepted
Monica Ianucci
Product sales summaries
Monica Ianucci
Sales case studies for content modules
Jonathan Brant
SMEs videos for content
Monica Ianucci
Upload presentations, demos and webinars for content modules
Jonathan Brant
Documentation
Development and documentation of coding standards & procedures
Shannon Valley
Develop test acceptance plans & procedures
Steve Quan
HighLEARN database test & acceptance
Shannon Valley
HighLEARN roll-out
Toni DiBello
The estimated cost of the HighLEARN project is $1.5 and it is estimated to be completed in seven months (MindEdge 2014). See allocation below:
Portal Development
$375,000
Infrastructure & Security
$375,000
Content Creation & Editing
$375,000
Documentation
$375,000
Total Budget
$1.5 Million
Key project stakeholders
Stakeholders are essential to the success of a project as they may positively impact and support initiatives and deliverables. In contrast, they may also have a negative impact on the
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
6
same. It is important to monitor the interests of these parties in order to better have control of and
ensure the success of the project.
Stakeholders Support Analysis
NAME
ROLE
INTEREST
POWER
CLASSIFICATION
Carol Bailey
CEO
High
High
Positive
Peter McKenzie
Head of Sales
Project Sponsor
High
High
Positive
Ricardo Contin
Head of Learning & Development
High
High
Positive
Steve Quan
IT Operations Specialist
Medium
Low
Neutral
Shannon Valley
IT Systems & Security
Medium
Low
Neutral
Monica Ianucci
Content Specialist
Medium
Low
Neutral
Jonathan Brant
Content Specialist
Medium
Low
Neutral
Stephanie Nameloc
Head of Acquisitions & Product Portfolios
Low
High
Neutral
Sasha Fiercer
Marketing/Advertising
Medium
Medium
Negative
Jason Holdmeer
Marketing/Advertising
Medium
Medium
Negative
Stakeholders Concerns
CONCERN
REPORTED BY
DESCRIPTION
PROJECT
IMPACT
DATE
IDENTIFIED
COMPLETION
DUE DATE
INTERNAL
OR
EXTERNAL
TEAM ASSIGNEE
1
Ricardo Contin
Website does not meet user requirements or functionality
High
6/1
6/3
Internal
Steve Quan
2
Sasha Fiercer
Jason Holdmeer
Marketing has not endorsed the approach and feel Microsoft ®
SharePoint
®
should be utilized
Medium
6/1
6/3
Internal
Peter
McKenzie
3
Content Development Team
Leadership is aggressively acquiring other businesses with new
products and services
Medium
6/1
12/11
Internal
Ricardo
Contin
4
Cyber Security Team
Security of internet/portal: no access beyond firewall
High
6/1
10/9
Internal
Shannon
Valley
Project Planning
Business Requirements
An important factor of the success of a project is the alignment to benefit the operations of the same. The requirements for this project are as follow:
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
7
1.
HighLEARN must be a fully operational intranet platform with the capabilitu to be modifiable and be able to provide data of all the services and products of Hightower
2.
HighLEARN must reduce the company’s costs in relation to training
3.
It must be user-friendly and clear to associates to ensure compliance and feasibility.
4.
Training conducted by HighLEARN must result in higher sales.
5.
It must facilitate the acquisition of businesses and the expansion of products and services.
6.
The project must be completed within a period of six months and remain under the budgeted $1.5 million.
Experts from the different dynamics involved or areas affected in the project must be consulted to ensure business requirements are met. Due to the size of the project and its impact on Hightower as a whole, it is also advisable that a prototype be built to demonstrate these requirements and gather realistic feedback from the users (Schedlbauer, 2011).
Subject Matter Experts
Subject matter experts are interviewed and asked for intel and recommendations. Among those are Peter McKenzie and Carol Bailey, who were interviewed regarding schedule, budget and business requirements. Subsequently, a focus group of Ricardo Contin, Steve Quan, and Shannon Valley other experts in marketing, cyber security. and business operations were consulted and contributed to the areas of development of the schedule, portal, infrastructure and security, content creation, and documentation.
Project Requirements Template
Requiremen
t
Number
Description
Priority
1
Improve sales performance
High
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
8
2
Create product experts from the sales team
High
3
Make product information & presentations available
High
4
Make webinars and videos with product specialists accessible
High
5
Portal to include social features including blogs and forums to
share tips and feedback
Medium
6
Portal must be enabled to be updated with new trends and material
Low
7
Project completion with in seven months
Low
8
Project to be completed within budget
Low
The project planning format is important as it is used to capture requirements because they need to be communicated to stakeholder for validation (Schedlbauer, 2011). This helps in confirming that these requirements are clearly understood and resources are not wasted while implementing unneeded functionality (Schedlbauer, 2011). Requirements traceability creates a matrix that defines why these exist and to guarantee they are being implemented (Schedlbauer, 2011). The use of this matrix allows us to trace a requirement to deliverables or in contrast, from a deliverable to requirement (Perforce, 2018) allowing the project manager to verify the project’s
trajectory and progress. It allows to ensure that goals are being met and aide in decision making given that changes take place and may impact requirements (Perforce, 2018).
Running head: MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS CASE STUDY
9
Project Schedule
Activity
Activity Name
Expected
Completio
n Date
Predecess
or
Activity
Resource
Assigned
Duration
in Days
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Delivery & Design
1
Survey stakeholders on vision
6/7/2019
-
Tony DiBello
5
2
Style sheets for portal
6/9/2019
1
Monica Ianucci
5
3
Theme design for website
6/30/2019
2
Jonathan Brant
15
4
Portal administration complete & accepted
6/9/2019
1
Ricardo Contin
2
5
Administrative access control design
7/28/2019
4
Ricardo Contin
35
6
Administrative page groups
10/6/2019
5
Monica Ianucci
50
7
Content display from repository
8/9/2019
3
Jonathan Brant
28
8
Architecture approved for implementation
6/19/2019
2
Shannon Valley
1
9
Servers for development, staging & production
9/18/2019
8
Tony Dibello
65
Content Creation & Editing
10
Interviews with subject matter experts
8/11/2019
1
Ricardo Contin
10
11
Product sales summaries
9/8/2019
1
Ricardo Contin
20
12
Sales case studies for content modules
10/27/2019
1
Ricardo Contin
35
13
Edit/film SME videos
11/3/2019
10
Monica Ianucci
5
14
Product content modules
11/10/2019
12
Monica Ianucci
5
15
Upload presentations, demos and webinars for content modules
11/24/2019
20
Jonathan Brant
1
Development & Programming
16
Integrate infrastructure & security systems
12/13/2019
9
Steve Quan
40
17
Create log-in & user profiles
12/14/2019
8
Steve Quan
20
18
Development and document coding standards & procedures
10/2/2019
8
Shannon Valley
75
19
Develop test acceptance pans & procedures
10/2/2019
8
Steve Quan
75
20
Configure/code indexing & functionality
12/18/2019
9
Steve Quan
65
21
Content upload & functionality
11/13/2019
9
Shannon Valley
40
Testing & Review
22
User interface design complete & tested
11/27/2019
19
Shannon Valley
40
23
Log-in & registration system complete and tested
12/19/2019
17
Shannon Valley
3
24
Content management & coding complete and tested
12/22/2019
23
Steve Quan
2
25
HighLEARN database test & acceptance
12/29/2019
24
Shannon Valley
5
Launch
26
HighLEARN Rollout 1/1/2020
25
Tony DiBello
1
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
10
Running head: MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS CASE STUDY
11
Refined Estimate
S. Valley and S. Quan were assigned to the project, however, were unable to come aboard until a month after initiation there were several tasks that had already been started by a SME, but possibly completed or signed off on by Valley or Quan. Despite of challenges during portal development, multiple tasks were fast-tracked to remain on schedule.
Activity
Activity Name
Expected
Completio
n Date
Predecess
or
Activity
Resource
Assigned
Duration
in Days
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Delivery & Design
1
Survey stakeholders on vision
6/7/2019
-
Tony DiBello
5
2
Style sheets for portal
6/9/2019
1
Monica Ianucci
5
3
Theme design for website
6/30/2019
2
Jonathan Brant
15
4
Portal administration complete & accepted
6/9/2019
1
Ricardo Contin
2
5
Administrative access control design
7/28/2019
4
Ricardo Contin
35
6
Administrative page groups
10/6/2019
5
Monica Ianucci
50
7
Content display from repository
8/9/2019
3
Jonathan Brant
28
8
Architecture approved for implementation
6/19/2019
2
Shannon Valley
1
9
Servers for development, staging & production
9/18/2019
8
Tony Dibello
65
Content Creation & Editing
10
Interviews with subject matter experts
8/11/2019
1
Ricardo Contin
10
11
Product sales summaries
9/8/2019
1
Ricardo Contin
20
12
Sales case studies for content modules
10/27/2019
1
Ricardo Contin
35
13
Edit/film SME videos
11/3/2019
10
Monica Ianucci
5
14
Product content modules
11/10/2019
12
Monica Ianucci
5
15
Upload presentations, demos and webinars for content modules
11/24/2019
20
Jonathan Brant
1
Development & Programming
16
Integrate infrastructure & security systems
12/13/2019
9
Steve Quan
40
17
Create log-in & user profiles
12/14/2019
8
Steve Quan
20
18
Development and document coding standards & procedures
10/2/2019
8
Shannon Valley
75
19
Develop test acceptance pans & procedures
10/2/2019
8
Steve Quan
75
20
Configure/code indexing & functionality
12/18/2019
9
Steve Quan
65
21
Content upload & functionality
11/13/2019
9
Shannon Valley
40
Testing & Review
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
12
22
User interface design complete & tested
11/27/2019
19
Shannon Valley
40
23
Log-in & registration system complete and tested
12/19/2019
17
Shannon Valley
3
24
Content management & coding complete and tested
12/22/2019
23
Steve Quan
2
25
HighLEARN database test & acceptance
12/29/2019
24
Shannon Valley
5
Launch
26
HighLEARN Rollout 1/1/2020
25
Tony DiBello
1
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Running head: MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS CASE STUDY
13
Project Execution
There were considerable drawbacks to the use of the waterfall method when exploring the right approach for the HighLEARN project. While it may be better for smaller projects, waterfall testing would not begin until development is completed. This leads to bugs being found
later in development where they are more costly to fix (Guru99, n.d.). Because waterfall is less focused on the client, it may very well result in a portal for that may not align with the business requirements, resulting in not being suitable for the use of the sales team. In contrast, Agile employs a client focused process that may ensure the sales team are continuously involved during every stage (Guru99, n.d.). It is recommended that Tony uses an agile approach to implement this project. To ease communication, especially since team members will simultaneously work on different tasks, a Jira board would be a great tool to keep the team up to date on project progress and the like.
Project Control
Change Management
A change control process is necessary to evaluate and implement changes that bring value to the project and reject those that could disrupt work (MindEdge, 2014). It will be important to implement an Agile methodology as it provides flexibility as changes arise. The team should evaluate change requests when received and then decide their suitability and effects on the project. When a benefit is a possibility, the team must also determine if the change is possible according to the project plan (MindEdge, 2014). Stakeholders are to be notified if a change has been accepted or rejected, and the rationale behind the decision.
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
14
Risk Management
Risk management involves risk identification, analysis, response and monitoring and control. The team will brainstorm to allow the free flow of ideas and assess the probability and consequences of risks (MindEdge, 2014). A risk registered should be created where all known and assumed risks are documented. Overall risk exposure and highlight specific risks are analyzed by means of a quantitative analysis. Subsequently, a response plan for each risk is identified, documented, and updated. The risk register will be used as a living document throughout the life of the project, and will be updated continuously, removing old risks, and adding new risks and responses respectfully.
Project Issues
Running into issues is inevitable. As they arise, they will need to be documented and supervised in attempts to successfully complete the project. An issues register may be created so that these issues can be documented as they occur, any possible solutions that are implemented to
serve as future reference. The information found in this register is used in the controlling portion of the project to take preventive and/or corrective action as needed.
Project closeout
At the conclusion of a project is considered best practice for a project manager to run a project close checklist. (MindEdge, 2014). The same includes the following:
Reassigning personal,
Auditing final records,
Closing contracts,
Creating support documents
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
15
Product materials
Informing the stakeholders of late-stage tasks and project completion
Completing a final report on the project
Hold a closing meeting with team members and stakeholders.
A responsibility assignment matrix is used to review and confirm the completion of each of the requirements in order to minimize the risks of overlooking a project process. While auditing the final records, the responsibility assignment matrix allows for a swift verification that all requirements have been met, the responsible party and all pertinent information. Warranty Period
This period provides us with an opportunity to support HighLEARN after launch and be able to make adjustments or enhancements at the request of the stakeholders. During this period the project time shares knowledge and information during implementation. It may also be expected of the project team to provide some on-going support where applicable.
Lessons Learned
Category
Issue
Problem/Success
Impact
Recommendation
Resources
Availability or Resources
Valley and Quan were unable to join the team until after the team was already
in motion.
Their tasks had to be resourced leveled via SME
in efforts to keep the project on schedule
Provide some flexibility in the project schedule in anticipation of similar setbacks.
Resources
Server capacity
Initial server storage:
Server size estimates meet requirements. Future content will demand added space.
Actual server storage:
While it meets the needs, it will
require additional space.
Anticipate greater storage needs. Consider cloud storage option.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
MILESTONE 3 – HIGHTOWER GLOBAL SOLUTIONS
16
Risks
Intranet portal security
Challenges presented regarding external access to
portal through the
firewall
No external access to portal due to firewall blocking. It required extra time spent troubleshooting and reconfiguring firewall to concede access.
Time flexibility to
be considered in anticipation of technical and network issues of this nature.
Risks
Site requirements
Website performed efficiently and even exceeded users’ minimum requirements.
Functionality was positively received by users. Considerations to maximize portal use was evident.
Allocate additional time for
interactions with, and user input.
References
Schedlbauer, M. (2011, January 25). Business analyst | The quest for good requirements. BA Times. https://www.batimes.com/articles/the-quest-for-good-requirements.html
Perforce. (2018, May 29). What is a requirements traceability matrix? Your A–Z guide. Perforce Software | Development Tools For Innovation at Scale. https://www.perforce.com/resources/alm/requirements-traceability-matrix#why
MindEdge, Inc, (2014). QSO-640: Project Management. Southern New Hampshire University:
Retrieved March 30, 2023 from: https://snhu.mindedgeonline.com/content.php?
cid=87492
Guru99. (n.d.). Waterfall vs. Agile: Must know differences. Meet Guru99 - Free Training Tutorials & Video for IT Courses. https://www.guru99.com/waterfall-vs-agile.html