MGT 4111 Project Management: Sending a Work Team Overseas for a Year

This project plan outlines the strategic approach for BlackBerry QNX to send a team of 15 employees to Ford Motors in Australia for one year to assist with developing innovative automobile technology. It details the project's importance to BlackBerry QNX's organizational strategy, emphasizing the company's expertise in software solutions for the automotive industry, particularly in connected car technology. The plan defines project goals focused on delivering AI-based software solutions, specifies the roles and responsibilities of team members including a Team Leader, Project Manager, Software Architect, and Software Engineers, and includes a stakeholder analysis to manage potential impacts. A detailed project plan incorporates a Work Breakdown Structure, Process Breakdown Structure, and Responsibility Matrix, along with time and cost estimates. Furthermore, the plan includes a risk management assessment to mitigate potential challenges, ensuring the successful execution of the project and the achievement of its objectives.

Running head: PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Planning To Send a Work Team of 15 People Overseas For a Year
Name of the Student
Name of the University
Author’s note

1PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Table of Contents
1. Project Overview and Goals........................................................................................................3
1.1 Importance of Project for the Organization...........................................................................3
1.2 Tie of the Project Overview with the Overall Organizational Strategy.................................4
1.3 Justification of Goals for the Project.....................................................................................6
2. Project Team Structure and Stakeholder Analysis......................................................................7
2.1 Project Team Members..........................................................................................................7
2.2 Stakeholders involved within the Project..............................................................................9
2.3 Identification of negative impacts towards project from certain stakeholders....................10
2.4 Responsibilities of particular Stakeholders within the Project............................................11
3. Detailed Project Plan.................................................................................................................12
3.1 Project Scope.......................................................................................................................12
3.2 Deliverables.........................................................................................................................13
3.3 Milestones............................................................................................................................13
3.4 Work Breakdown Structure.................................................................................................15
3.5 Process Breakdown Structure..............................................................................................17
3.6 Responsibility Matrix..........................................................................................................18
3.7 Estimates of time and costs for each concerned activity and overall project......................19
4. Risk Management Assessment..................................................................................................21
5. Rationale for Above Project Aspects.........................................................................................24

2PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Bibliography..................................................................................................................................26

3PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
1. Project Overview and Goals
1.1 Importance of Project for the Organization
QNX is one of the commercially launched Unix-like real-time operating system, which is
primarily aimed at the underlying embedded systems market. This product was primarily
developed in the early 1980s by a Canadian firm named as QNX Software Systems. The
software company was acquired by BlackBerry in 2010. The company is in the process of
expanding their business operations and bringing in new processes within their business systems.
The BlackBerry QNX has majorly empowered QEMs to help in developing scalable, secure and
trusted form of software solutions that would be able to enable better future impacts towards
autonomous and connected cars.
In the present case study, the primary focus is on discussing about the ways in which the
company would expand their business context in the overseas market. One of the major projects
that have been achieved within their business prospects is the innovative aspect of connected car.
With the innovation that have been brought with the impact of autonomous cars, the company
has been able to expand their reach of their business. This project is based on sending a working
team comprising of 15 people to the overseas market in order to propagate their business
structure and their innovation aspect. The BlackBerry QNX has been approached by Ford
Motors, Australia for helping their automobile designing team in bringing an innovative design
of cars. The team that would be provided by BlackBerry QNX would be sent to Australia and
would stay there for a contractual period of one year.
The concerned team of 15 people would comprise of both experienced and new comers
who would also be able to provide a variety of suggestions to their automobile team in designing

4PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
the technology-enabled car. In the recent market, it has been further been analysed and discussed
that automobile designers are being challenged with various kind of regulatory and increasing
demands of customers. For Motors are also in the process of bringing an innovative segment
with the evolution of connected car technology. However, the automobile and technological
experts in the automobile engineering department are lacking in the particular expertise and thus
cannot progress with designing the technology for their cars. Hence, the Automobile Design
management team has approached BlackBerry QNX to help them in designing the technology
for uplifting the business benefits for the company.
BlackBerry QNX is responsible for planning the entire strategy for planning the entire
project, which initiates from selecting the proper people who would be able to make certain plans
for making design of the technology. The second stage includes sending those people to
Australia where they would join the automobile team of Ford Motors and thus discuss about the
ways in which they could plan the entire design of the new project. The entire project would be
helpful for BlackBerry QNX as this would help the organization in incurring a good name
towards the organization and also increase the business revenue.
1.2 Tie of the Project Overview with the Overall Organizational Strategy
The BlackBerry QNX is a reputable company in Canada and thus made a great impact in
the lives of many people. Different people make use of the controllable systems of QNX in order
to serve their various purposes of driving, shopping, watching TV shows and using Internet
connected technologies. The ultra-reliable nature of QNX software is considered as the most
preferable choice for various kind of critical systems that includes surgical equipment, air traffic
control systems and in different nuclear power plants. The organization is dedicated towards

5PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
designing a particular software solution that would highly be efficient for the business partners in
developing their systems.
The overall strategy of BlackBerry QNX is to offer a varied range of comprehensive
portfolio based on industrial systems for the purpose of addressing the imminent challenges that
are faced with the rising competition. The unique nature of software solutions that are developed
by BlackBerry QNX provides highly efficient kind of business solutions. These software systems
are highly reliable and thus enables their customers for creating custom solutions with low
billing of maintenance costs and development of materials. The robust nature of their partnered
ecosystems and innovative practices helps other organizations to speed up their business projects
and building out different solutions.
In this project case study, the main objective of the project is to send a mixed team of 15
people who would go to Australia in order to design an AI based software solution within their
automobile technology. In the group of 15 people, it would consist of experienced and new
people who would be able to work together and thus serve Ford Motors in designing the
innovative software technological systems. In the recent market of newly developing connected
car technology, the automobile designers at Ford Motors are facing some kind of challenges in
implementing the technology within their cars. They are thus lacking in the sector of software
technological expertise that would help the company in understanding the needs of customer and
the raising expectations.
The BlackBerry QNX offers a broader portfolio of innovative software solutions based
on thinking about the future of the automotive industry. The software solutions that are
developed by BlackBerry QNX includes type-1 hypervisor that supports ECU integration,
acoustics and ADAS. One of the software product based for the automotive sector is the Over-

6PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
the-Air (OTA) software update platform. This particular software ensures a secure form of
software lifecycle management based on providing an innovative nature to the technical
platform. The BlackBerry QNX helps in providing scalable and flexible form of software
solutions that would enable the recent vehicular systems to provide the best kind of service to the
customers. Thus the futuristic cars would be fully automated and thus serve a wide range of
purposes. By providing such kind of highly scalable solutions for Ford Motors, the BlackBerry
QNX would be able to prove their high level skills in the highly competitive market and would
also open new areas for growth of the business.
1.3 Justification of Goals for the Project
The primary goals for the project is to ensure that the concerned team that would be sent
to Australia for helping the automobile team at Ford Motors would be able to deliver the best
kind of business solutions towards the project. The goals set for BlackBerry QNX is to help the
Australian automobile manufacturing company in developing the best form of software solution
that would be based on AI, cloud computing and IoT technology. The team involved at
BlackBerry QNX is extremely efficient in developing a wide range of software solutions such as
Advanced Driver Assistance Systems (ADAS), Instrument clusters, telematics and many others.
Some kind of improved functionalities with the implementation of the software solutions are
enhancement for engine sounds, hands free system, infotainment, rear seat entertainment and
many others. These wide cluster of facilities would be highly used by Ford Motors in order to
design the new concept of futuristic cars.
The defined activities that would be performed by the team of 15 people aligns with the
goals of the project. They would be efficient in understanding the business scenario and thus
define proper measures, which would be helpful for improving the context of the business. The

7PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
project would also open new roadways for the software developers to improvise their
technological aspects and skills based on innovating the present software systems. Hence, it can
be discussed that the goals set for the project are specific and thus are clearly defined.
2. Project Team Structure and Stakeholder Analysis
2.1 Project Team Members
The team that would be sent to Australia would consist of a group of experienced and
new people who have recently joined the company. With the mix of the group of people, it
would be helpful for the team to work together on the project. The experienced people would be
able to guide the new people who would be involved within the team.
As per the provided project on sending a team of 15 people to the overseas for a time
period of one year, it would be discussed that the following team members would be responsible
for doing the work on the project.
1. Team Leader – The team leader would require the soft skills for managing the entire
technical aspects of the team. They would focus on individual team members and the tasks that
are performed by them. The hard skills such as the designing the plan for the project would be
defined within the scope of the team. The primary responsibilities and role of the team lead is to
maintain a proper level of team cohesion, facilitation of each members of team and ensuring that
the entire team has access to various kind of resources that are required by them. The team leader
would also hold responsibility to safeguard the entire team by noticing their concerns and thus
take measures to mitigate their concerns. Ensuring a proper care over the team would ensure that
the project would achieve the expected success criteria for the concerned project.

8PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
2. Project Manager – The project manager would be responsible for handling the entire
aspects of the project team concerned with the project. The project manager would understand
the requirements of the client and would then convey the entire requirements to the team leader.
The team leader would then be responsible for following up with the requirements and then
transfer the gained knowledge to the team members involved within the project. The project
manager would also handle the entire aspect of managing the task of sending the working team
to Australia and then be responsible for ensuring that the project is undergoing successfully.
3. Software Architect – The software architect for the project would be responsible for
thinking of a proper plan that would need to be executed during the design phase of the software.
They would also look within the entire technical design of the software. The software architect
would hold responsibility to determine the appropriate technological stack that could be used.
They would also oversee the proper engineering discipline and the proper team members who
would be able to perform the technical tasks in a proper manner.
4. Software Engineers or Developers – The software developers are responsible for
understanding the requirements set by the team leader and software architect. The developers
would then plan accordingly to the structure of the software plan. The team of software
developers would thus work to ensure the stability and usability of the product. The software
developers would research for the best kind of coding platform that could be used for the
development of the software. They should be able to include each of the intrinsic details within
the software and should also ensure that proper encryption systems should be embedded within
the code.
5. UX Designer – The job role of the UX designer would be based on understanding the
current market scenario and the existing problems that are faced by users. The UX designers

9PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
would be responsible for interviewing the users of automobiles, research over the collected data
from the market and then gather those findings for performing additional research over them.
6. UI Designer – The role of the UI designer is to collaborate with the UX designer and
thus think of various innovative ways for designing the entire software interface. The interface
should be designed in such a way that it would appeal to a wide number of users.
7. Tester – The testing team that would consist of 5 people would hold the responsibility
of ensuring the quality assurance of the developed software. After the development team has
developed the code, it would be passed on to the testing team for quality assurance check of the
developed software. Once a problem such as a software bug has been detected, the code would
be returned to the development team for rechecking of the code and mitigate the errors within the
code.
2.2 Stakeholders involved within the Project
There should be a good kind of process for the discovery of proper stakeholders who
would be involved within the process of software development. The stakeholders who would be
involved within the concerned project might be working within the organization or might not
also be directly associated by the organization. The input from the stakeholders who would be
involved within the project would be able to discuss about the ways in which the software
solution would be developed and be embedded within the automatic connected cars.
The stakeholders who are involved within the project would understand the concerns of
the client and would thus provide recommendations for the betterment of the concerned product
that is currently been developed. These stakeholders would be responsible for constructing map
workflows for understanding the use-case diagrams. The definition of the proper methodology

10PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
for the software design would be able to guide the UI design of the software. The stakeholder
involved within the current project scenario are the CEO of BlackBerry QNX software solution
company, the team members involved within the development project, managers and owners for
the project.
The stakeholders who would be affected by the project are the CEO, managers and the
automobile management team at Ford Motors. These stakeholders are primarily responsible for
hiring the group of 15 people and thus providing them with the responsible equipment and
software solutions that would help them in developing the new kind of software product. These
stakeholders would be overseeing the entire development work of the project and would also
point out any kind of faults when detected within the system functions.
2.3 Identification of negative impacts towards project from certain stakeholders
The stakeholders are considered as the most important aspect within an organization.
Each of the project group has their own kind of list of involved stakeholders who are responsible
for providing directions to the entire team. The identification of the proper kind of stakeholders
would be helpful for determining the success of the project. A successful project would be able
to address the needs of stakeholders within the life cycle of the project. Within the phase of
planning for the project, the most important step is to identify the possible stakeholders who
would be involved within the team and would bring a positive impact towards the team. The
improper mode of planning for the stakeholders would result in risks such as project delays and
ultimately lead to cancellation of the concerned project.
Stakeholders also form a major influence over the project. In the concerned project, each
of the stakeholders are important for the project. However, there some situations in which
stakeholders might form a negative impact over the project. In the present project context, the

11PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
team members such as the developers might form a negative impact over the project. Improper
use of software solutions within the context of the business might lead to negative consequences
for the project. The technical software platforms would be provided by different other technical
companies. Offering the software solutions within the proper time to the Automobile engineering
department at Ford Motors is a matter of grave concern for the company. Delays within the
schedule of the project would lead to delay in further progressing of the works over the project.
In case the project is delayed due to some concerns, it would result in increase of costs that
would be incurred for the project. It would also add to the increase of legal proceedings for the
company. In order to mitigate such kind of issues associated with the stakeholders, it would be
extremely important to handle such kind of negative impacts from the project and thus deal with
them before the initiation of the project. The stakeholders should deliver the materials before
time in order to ensure that there would be no such kind of delay in the works of the project.
2.4 Responsibilities of particular Stakeholders within the Project
The stakeholders form a major aspect within every project. Hence, neglecting the need of
stakeholders involved within a project can be defined as a risky proposition towards the project.
With the unique nature of each software development project, there is a vast need to identify the
proper kind of stakeholders who might put an impact over the project. The identification of the
proper kind of stakeholders would be able to guide the entire team throughout the work of the
project.
The good kind of software development for the described systems is a necessary criteria.
Based on the identification of the proper stakeholders, it would be helpful for determining about
the success of the project. In the concerned project, the stakeholders would be identified by
conducting proper kind of interview sessions. The project manager or the CEO of the

12PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
organization would take the responsibility of hiring the proper team members would be involved
within the development work of the project. Hence, each of the people concerned within the
team would be properly chosen by conducting a series of test scenarios. These must be cleared in
order to get selected to be sent overseas for delivering a high kind of business solution.
After the proper stakeholders have been selected for the concerned project, they would
need to be properly instructed to work according to some predefined conditions. The team leader
would define the proper structure of the software that would be designed for Ford Motors. The
team members that includes the development team and testing team should properly abide by the
provided instructions and then should deliver the proper kind of software solution. Ensuring the
proper persons have been put on board, would ultimately result in positive feedbacks after the
delivery of software. After the proper stakeholders have been identified for the project, it would
ultimately result in positive workflow within the various processes in the automobile
manufacturing industry.
3. Detailed Project Plan
3.1 Project Scope
The scope of the project is based on defining a software technological solution for Ford
Motors. The company is in the process of the implementing a new kind of software systems that
would be able to mitigate the existing problems in car technology and also meet with the
changing preferences of the customers. The project is based on incurring a team of 15 members
for the project who would be responsible for designing a plan for the project. The team would
conduct a market research of the preferences of customers and thus map those scenarios in order
to gain appropriate results. The scope of the project is also based on identifying the risks within
the project and thus thinking of proper measures in order to mitigate the risk approaching

13PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
towards the project. The team would be involved with the various activities of planning,
scheduling, development, testing and deployment of software solutions.
3.2 Deliverables
The deliverables that would be included within the project are:
1. The project would include a proper form of project plan. This plan would be able to
deliver the proper deliverables that would be understood by each of the team members involved
within the project. This plan would detail the list of activities that would be included within the
project. The plan would include the resources that would be responsible for performing the
particular tasks, the costs allocated to each resources and the working order of each of the
activities within the project.
2. The project also includes a list of involved stakeholders within the project. The
concerned activities and roles are fully determined in the stakeholder list.
3. The project also includes the work breakdown structure of each of the aspects of the
project. This structure defines the activities that would be performed within the project.
4. The milestones are also included in the list of deliverables concerned within the
project. These milestones would be highly needed to be determined as they would be needed to
get completed in order to proceed on to the next activity.
3.3 Milestones
The milestones involved within the project are:
1. Completion of Project Initiation Phase
2. Completion of planning phase of software

14PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
3. Approval of technical plan by the project designing team
4. Finalising of requirements
5. Completion of planning phase of software
6. Completion of execution of software design phase
7. Completion of quality assurance and control phase
8. Completion of Project Closure Phase

15PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
3.4 Work Breakdown Structure
QNX Software Design
Start of the Project Initiation of the Project
Contacting Ford
Motors about the
contract
Evaluating the
contract
Making an initial
plan
Deciding the project
manager
Deciding of the team
leader
Making them
understand about
the details of the
contract
Hiring of a
development and
testing team head
Meeting with the
development team
about the project
Making decisions
over the contract
Deciding of the
technical solutions
to be implemented
for Ford Motors
Making decision
about the particular
software
Finalising of the
decisions
Finalising the
business contract
Developing a
project charter
Submission of the
project charter to
Ford Motors
Reviewal of the
Project Charter
Signing of the
Project Charter by
both companies
Completion of the
Phase
Planning phase of
software
Analysis of
requirements
Designing the
financial plan for
project
Approval of project
plan
Creating
stakeholder
management plan
Creation of Project
Scope Statement
Determining the team
of 15 members
Conducting
preliminary test for
determining the
eligible candidates
Deciding the results
and formation of the
project team
Creation of
Technical plan
Approval of the
technical plan by the
team leader
Finalising the
requirements
Contacting Ford
Motors for assisting
them in booking of
flight tickets
Sending of flight
tickets
Shift of the team to
Australia
Completion of the
Phase
Execution of the Software
Design Phase
Kickoff meeting of
the project
Understanding the
primary
requirements of
Ford Motors team
Performing initial
tests over the
existing cars
Gathering results
from the conducted
test activities
Conducting meeting
with automobile
designers
Collection of user
feedbaack
Verification and
validation of user
requirements
Making of Initial
payment to
Blackberry QNX
team
Designing the
software system
specifications
Procurement of
hardware and
software
Installation of the
software solutions
Embedding software
security patches
within the developed
software
Testing of the
procured hardware
and software
Recruiting new
technical team
members within
Ford Motors
Making the team to
understand about
the technical
requirements of
organisation
Training to the Ford
automobile team
Initiating the desired
project work
Testing of the
software
Re-assessing the
software code and
making changes
Installation of the
live system within
cars
Testing of the
software system by
automobile makers
Gathering feedbacks
from the internal
team
Making of partial
payment
Completion of the
phase
Quality Assurance and
Control Phase
Kicking off meeting
with the Project
Management team
Deciding of results
gained from testing
phase of software
Collecting a group
of users for
feedback
Conducting beta
testing of the
software application
Gathering of results
from the group of beta
users
Preparing data
analysis over the
gathered results
Detecting of flaws (If
any) within the system
Making of
recommendation
plans
Deciding strategies to
work on the system
Contacting the
development team
to mitigate the
errors
Making amendments
within the developed
code
Conducting a risk
management plan
Gaining feedbacks
about risks present
within the system
Deciding of
strategies for
mitigating risks
Mitigating the risks
detected within the
system
Designing the project
management plan
Updating the project
management plan
Completion of the
Phase
Project Closure Phase
Designing of an audit
plan for project
Procurement of the
audit plan for project
Preparing of the
documentation of
the project
Updating the current
files and records of
the present designed
system
Presenting results to
the Ford Motors
team
Collecting final
business related
payments
Handing the
documentation of
the project charter
Gaining a formal
acceptance from the
management team
Archiving of files
and documents
Making of payments
to development team
Making payments to
testing team
Producing the
documentation
results to project
manager and team
lead
Making final
payments to project
manager and team
lead
Signing off on
procurement
Returning of the
project team back to
Canada
Meeting with the
BlackBerry QNX
team about project
review
Evaluation of their
entire performances
Completion of the
phase
End Project

16PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
(Fig 1: The Work Breakdown Structure of the Project)
(Source: Created by Author)

17PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
3.5 Process Breakdown Structure
The process breakdown structure for the project includes:
1. Initiation of the Project – The contract for the project would begin in this phase. This
would include the deciding over the contract of the project. Under this phase, the entire
deliverables of the phase are decided. This phase would also decide on the project charter, which
would help in designing the entire plan for the project.
2. Planning phase of the software – During this phase, the plan for the design of the
software would begin. The entire list of technical requirements for the project is determined and
then the software systems installed at Ford Motors are determined in order to test whether they
would be able to meet with the system specifications.
During this phase, the proper technical software would be defined. The coding platforms
would also be determined. The technical team that includes the development team and testing
team would also be hired in this phase. The entire list of specifications would be designed in this
phase. The plan for progressing with the work over the software would be determined. Under
this plan, the entire set of discussed and would-be implemented technology would be
determined. This would help the technical teams to gain a full idea for developing the software.
3. Execution of Software Design Phase – In this phase, the task of execution of the
planned activities would begin. During this phase, the technical team would be responsible for
coding and developing the software design. After the code has been developed, the testing team
is responsible for testing the entire code in order to detect any bugs if present within the
software. If any kind of bugs are detected within the system, the testing team would again report

18PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
the matter to the development team who would perform their work of removing the bugs from
the system.
4. Quality Assurance and Control Phase – The quality assurance team would ensure
that the project is completed as per the given criteria by Ford Motors and that it suits the needs of
customers. Different forms of quality checks would be performed in this phase.
5. Project Closure Phase – In the final phase, the project would be completed and each
of the stakeholders would be paid as per their choice of salary. In this phase, feedback would
also be gained from the Ford Motors company, which would prove that BlackBerry QNX has
been able to prove their capability of delivering high quality technical solutions.
3.6 Responsibility Matrix
ROLES
Project Sponsor
Ford Motors
Project
Manager
Technical Lead
Developers
Technical
service provider
Testing team
Testters
Deliverable or Task Status
Initiation of the Project
Initial project planning A R C R I C
Detailing of project goals and objectives A C I A
Planning phase of the software
Outlining the details of implementation works C I R I
Planning for deployment of the software I A C R A
Execution of Software Design Phase
Developing the code A I R C
Rigorous testing after code development I C R A A
Quality Assurance and Control Phase
Deploying and putting the equipment under test I R A C
Quality check over the software C A R R A
Project Closure Phase
Gaining feedbacks from Ford Motors I R A C
Sponsor Project Team Other Resources
(Fig 2: RACI Matrix)

19PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
(Source: Created by author)
3.7 Estimates of time and costs for each concerned activity and overall project
The duration of the entire project would be 483 days, while the costs incurred for the
project is $4,57,774. The payback period for the project is 2.91 years.
Initiation of the Project 52120
Planning phase of software 35080
Execution of the Software Design Phase 319414
Quality Assurance and Control Phase 45520
Project Closure Phase 5640
Total Cost for the project 457774
Total Cost for the project
(Fig 3: The Budget for the Project)
(Source: Created by author)

20PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Year of Project
year 0 year1 year 2 year 3 year 4 year 5 TOTALS
Net economic benefit $0.00 $35,000.00 $35,000.00 $35,000.00 $35,000.00 $35,000.00
Discount Rate 8% 1 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Benefits $0.00 $32,407.41 $30,006.86 $27,784.13 $25,726.04 $23,820.41
NPV of all BENEFITS $0.00 $32,407.41 $62,414.27 $90,198.39 $1,15,924.44 $1,39,744.85 $4,40,689.36
One Time Costs $87,200.00
Recurring Costs $0.00 $200.00 $200.00 $200.00 $200.00 $200.00
Discount Rate 8% 1.0000 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Recurring Costs $0.00 $185.19 $171.47 $158.77 $147.01 $136.12
NPV Of All Costs $87,200.00 $87,385.19 $87,556.65 $87,715.42 $87,862.43 $87,998.54 $5,25,718.22
Overall NPV ($85,028.87)
Overall ROI = (Overall NPV / NPV Of All Costs -0.16
Break-Even Analysis
Yearly NPV Cash Flow $0.00 $32,222.22 $29,835.39 $27,625.36 $25,579.04 $23,684.30
Overall NPV Cash Flow $87,200.00 ($54,977.78) ($25,142.39) $2,482.98 $28,062.01 $51,746.31
Project break-even occurs between years 2 and 3
Use 1st year of positive cash flow to calculate break-even fraction 2.9101 years
(Fig 4: The Payback period for the Project)
(Source: Created by author)

21PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
4. Risk Management Assessment
Types of
Risks
Person
affected by
the risk
Risks within the project Risk
Rating
Defensive Measures Person
responsible
for
mitigating
of risk
Project
scheduling
The Ford
Motors
company
The schedule defined for the project
within the project management file
should be properly followed in order
to gain an idea over the entire aspect
of the project. Wrong estimation over
the time allocated for each activity
would result in delay of a particular
task.
The failure to identify the complex
functionalities in any given tasks
would result in delay of the particular
activity that would further lead to
delay in performing the latter part of
project activities.
4 In order to mitigate the risk based on the
scheduling of activities, it could be
discussed that the schedule of the project
should be followed properly. A buffer
time should be kept after each activity in
order to ensure that each of the activities
would be completed within the pre-
estimated time period.
Project
Manager
Budgetary
risks
Financial
Manager at
Ford Motors
The risks based on budget could lead
to costs overruns for the project.
Wrong estimation of the budget for
the project might lead to instability in
the activities within the project. It
might also happen that the project
might run out of resources, which
cannot be further procured due to
lack of funds.
3 In order to mitigate the risks based on
budgetary issues, it should be confirmed
that the budget of the entire project should
be clearly defined much before the start of
the project.
Each of the technical aspects of the
project that includes the software
specifications, salary of employees should
be calculated during defining the entire
Financial
Manager at
BlackBerry
QNX

22PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
plan for the budget.
Operational
risks
Team Leader
at BlackBerry
QNX
The risks due to loss based on
improper kind of implementation
processes or some form of risks
based on events could lead to failure
of the project.
Insufficient resources within the
project or no proper kind of subject
training could lead to damage to the
project. Improper communication
within the team members and the top
level managerial levels could lead to
risks based within the operations of
the business.
3 There should be a proper kind of
communication with each of the team
members within the project team.
The project should address the conflicts
that might arise due to priority based
activities.
A formal training should be arranged by
the management team at BlackBerry
QNX in order to make them highly
efficient for showcasing their skills during
their work at Ford Motors in Australia.
Team
Leader and
Project
Manager
Technical
risks
Team leader at
BlackBerry
QNX
Continuous form of changing
requirements with the use of
technical innovations could lead to
problems in changing aspects of
coding. New technologies are
arriving in the market with every
passing day and this would lead to
challenges for the concerned project
team to decide on the best form of
coding technology that would be
implemented for the software.
Integration of difficult project
modules that would be implemented
by the team leader could be a
difficult approach for the
development team.
5 The coding platform that would be used
for the ongoing project should be
predefined and should be approved by the
development team and concerned team
leader at the project.
Each of the modules that would be
implemented within the project should be
properly understood and thus discussed
with each of the team members involved
within the project.
Each of the phases that are implemented
within the project should be properly
tested and then a plan should be defined
for performing further works over the
project.
Team
Leader

23PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
It might also happen that the project
might be difficult to be implemented
after a certain phase has been
completed.
Programmati
c risks
Development
team
During the development of the
project, there might be some form of
uncertain risks within the
development activities of the project.
Some of the external activities that
could be impact the project are:
 Lack of proper funding for
project.
 Changing form of project
priorities and customer
product strategy
 Low analysis over present
market development
4 In order to mitigate the risks based on
programmatic activities, it could be
defined that:
The funds needed for the entire project
should be pre-defined and should be taken
into control.
The changing strategy of the market
should be properly understood and the
project manager or team leader should
provide recommendations to the entire
team about bringing in change within
their ideas.
Project
Manager
and team
Leader

24PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
5. Rationale for Above Project Aspects
The project is based on the designing of a new and advanced mode of software systems
by BlackBerry QNX for Ford Motors in Australia. The Canadian firm has already designed their
systems based on connected cars. These cars are specially designed and are fitted with an
embedded software within them. This functionality thus helps the cars to enable different forms
of advanced software features for performing the daily activities that might be required by the
customers. The changing needs and preferences of customers have mostly forced Ford Motors to
realise the present situation and then perform some kind of activities to implement such kind of
activities within the car. Research has been made to develop best kind of software systems for
Ford Motors.
The project is based on sending a group of 15 people to Australia where they would be
responsible for planning an innovative design software, which would further be implemented
within the organization. The new kind of operating system can be discussed as a software
product that would meet with the functional safety of the automotive. The new designed product
can be thus used as a reliable platform based on ensuring the safety of drivers. In the recent
times, it has been seen that there is a growing concern for ensuring the safety of customers. Ford
Motors is highly dedicated towards providing the best form of solutions to their problems.
Hence, they have made a contract with BlackBerry QNX to bring in the best kind of automotive
solutions with the implementation of connected cars. This project discusses about the major
aspects that affect during the design of any project. The report thus discusses about the project
team, the responsibilities of each of the project team members, stakeholder involved within the
project and the responsibilities of each of the stakeholders. With the help of this project,
BlackBerry QNX would be able to propagate their technological systems and thus gain a huge

25PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
share in the worldwide market. They would also be able to provide software solutions to other
companies, which would further help them in generating a huge amount of business revenue for
the organisation.

26PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Bibliography
Bécsi, T., Aradi, S., & Gáspár, P. (2015, June). Security issues and vulnerabilities in connected
car systems. In 2015 International Conference on Models and Technologies for
Intelligent Transportation Systems (MT-ITS) (pp. 477-482). IEEE.
Bocken, N. M., Short, S. W., Rana, P., & Evans, S. (2014). A literature and practice review to
develop sustainable business model archetypes. Journal of cleaner production, 65, 42-56.
Braekers, K., Ramaekers, K., & Van Nieuwenhuyse, I. (2016). The vehicle routing problem:
State of the art classification and review. Computers & Industrial Engineering, 99, 300-
313.
Brookhuis, K. A., De Waard, D., & Janssen, W. H. (2019). Behavioural impacts of advanced
driver assistance systems–an overview. European Journal of Transport and
Infrastructure Research, 1(3).
Choi, T. M., Chan, H. K., & Yue, X. (2017). Recent development in big data analytics for
business operations and risk management. IEEE transactions on cybernetics, 47(1), 81-
92.
Coppola, R., & Morisio, M. (2016). Connected car: technologies, issues, future trends. ACM
Computing Surveys (CSUR), 49(3), 46.
Daza, I., Bergasa, L., Bronte, S., Yebes, J., Almazán, J., & Arroyo, R. (2014). Fusion of
optimized indicators from Advanced Driver Assistance Systems (ADAS) for driver
drowsiness detection. Sensors, 14(1), 1106-1131.

27PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Dhall, R., & Solanki, V. (2017). An IoT Based Predictive Connected Car
Maintenance. International Journal of Interactive Multimedia & Artificial
Intelligence, 4(3).
Elverum, C. W., & Welo, T. (2015). On the use of directional and incremental prototyping in the
development of high novelty products: Two case studies in the automotive
industry. Journal of engineering and technology management, 38, 71-88.
Gawer, A., & Cusumano, M. A. (2014). Industry platforms and ecosystem innovation. Journal
of Product Innovation Management, 31(3), 417-433.
Gora, P., & Rüb, I. (2016). Traffic models for self-driving connected cars. Transportation
Research Procedia, 14, 2207-2216.
Guler, S. I., Menendez, M., & Meier, L. (2014). Using connected vehicle technology to improve
the efficiency of intersections. Transportation Research Part C: Emerging
Technologies, 46, 121-131.
Häberle, T., Charissis, L., Fehling, C., Nahm, J., & Leymann, F. (2015). The connected car in the
cloud: a platform for prototyping telematics services. IEEE Software, 32(6), 11-17.
Haimes, Y. Y. (2015). Risk modeling, assessment, and management. John Wiley & Sons.
Hamid, U. Z. A., Pushkin, K., Zamzuri, H., Gueraiche, D., & Rahman, M. A. A. (2016). Current
collision mitigation technologies for advanced driver assistance systems–a
survey. PERINTIS eJournal, 6(2).
Han, M. L., Lee, J., Kang, A. R., Kang, S., Park, J. K., & Kim, H. K. (2015, December). A
statistical-based anomaly detection method for connected cars in internet of things

28PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
environment. In International Conference on Internet of Vehicles (pp. 89-97). Springer,
Cham.
Harjunkoski, I., Maravelias, C. T., Bongers, P., Castro, P. M., Engell, S., Grossmann, I. E., ... &
Wassick, J. (2014). Scope for industrial applications of production scheduling models and
solution methods. Computers & Chemical Engineering, 62, 161-193.
Ji, Z., Ganchev, I., O'Droma, M., Zhao, L., & Zhang, X. (2014). A cloud-based car parking
middleware for IoT-based smart cities: Design and implementation. Sensors, 14(12),
22372-22393.
Joore, P., & Brezet, H. (2015). A Multilevel Design Model: the mutual relationship between
product-service system development and societal change processes. Journal of Cleaner
Production, 97, 92-105.
Koesdwiady, A., Soua, R., & Karray, F. (2016). Improving traffic flow prediction with weather
information in connected cars: a deep learning approach. IEEE Transactions on
Vehicular Technology, 65(12), 9508-9517.
Krahn, H., Rumpe, B., & Völkel, S. (2014). Roles in software development using domain
specific modeling languages. arXiv preprint arXiv:1409.6618.
Lago, P., Aklini Kocak, S., Crnkovic, I., & Penzensradler, B. (2015). Framing sustainability as a
property of software quality.
Lockamy III, A. (2014). Assessing disaster risks in supply chains. Industrial Management &
Data Systems, 114(5), 755-777.

29PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Lu, C., Rong, K., You, J., & Shi, Y. (2014). Business ecosystem and stakeholders’ role
transformation: Evidence from Chinese emerging electric vehicle industry. Expert
Systems with applications, 41(10), 4579-4595.
Lu, Y. (2017). Industry 4.0: A survey on technologies, applications and open research
issues. Journal of Industrial Information Integration, 6, 1-10.
Noe, R. A., Hollenbeck, J. R., Gerhart, B., & Wright, P. M. (2017). Human resource
management: Gaining a competitive advantage. New York, NY: McGraw-Hill
Education.
Okuda, R., Kajiwara, Y., & Terashima, K. (2014, April). A survey of technical trend of ADAS
and autonomous driving. In Technical Papers of 2014 International Symposium on VLSI
Design, Automation and Test (pp. 1-4). IEEE.
Parkinson, S., Ward, P., Wilson, K., & Miller, J. (2017). Cyber threats facing autonomous and
connected vehicles: Future challenges. IEEE transactions on intelligent transportation
systems, 18(11), 2898-2915.
Porter, M. E., & Heppelmann, J. E. (2014). How smart, connected products are transforming
competition. Harvard business review, 92(11), 64-88.
Ring, T. (2015). Connected cars–the next targe tfor hackers. Network Security, 2015(11), 11-16.
Simchi-Levi, D., Schmidt, W., Wei, Y., Zhang, P. Y., Combs, K., Ge, Y., ... & Zhang, D. (2015).
Identifying risks and mitigating disruptions in the automotive supply
chain. Interfaces, 45(5), 375-390.
Slovic, P. (2016). The perception of risk. Routledge.

30PLANNING TO SEND A WORK TEAM OF 15 PEOPLE OVERSEAS FOR A YEAR
Smirnov, A., & Lashkov, I. (2015, April). State-of-the-art analysis of available advanced driver
assistance systems. In Proc. 17th Conference of the Open Innovations
AssociationFRUCT (pp. 345-349).
Svahn, F., Mathiassen, L., & Lindgren, R. (2017). Embracing Digital Innovation in Incumbent
Firms: How Volvo Cars Managed Competing Concerns. Mis Quarterly, 41(1).
Swan, M. (2015). Connected car: quantified self becomes quantified car. Journal of Sensor and
Actuator Networks, 4(1), 2-29.
Teece, D., Peteraf, M., & Leih, S. (2016). Dynamic capabilities and organizational agility: Risk,
uncertainty, and strategy in the innovation economy. California Management
Review, 58(4), 13-35.
Teo, T. S., & Bhattacherjee, A. (2014). Knowledge transfer and utilization in IT outsourcing
partnerships: A preliminary model of antecedents and outcomes. Information &
Management, 51(2), 177-186.
Vogel-Heuser, B., Diedrich, C., Fay, A., Jeschke, S., Kowalewski, S., Wollschlaeger, M., &
Göhner, P. (2014). Challenges for software engineering in automation. Journal of
Software Engineering and Applications, 7(05), 440.
Yang, K., Guler, S. I., & Menendez, M. (2016). Isolated intersection control for various levels of
vehicle technology: Conventional, connected, and automated vehicles. Transportation
Research Part C: Emerging Technologies, 72, 109-129.
Zhang, T., Antunes, H., & Aggarwal, S. (2014). Defending connected vehicles against malware:
Challenges and a solution framework. IEEE Internet of Things journal, 1(1), 10-21.