Reference no: EM132221923

The Case study: e-Borders Project in the UK

Case Study Overview

Case study background

In 2003, UK border controls relied primarily on systems and procedures that operated at the border itself. In the early 2000s there was a growing realisation in the UK and elsewhere of the need to do more checks before people arrived in the country, and ideally before they left their point of origin. It was against this background that the Department set up its e-borders program. The e-Borders program was commenced in 2003 by the Home Office, which aimed to deliver an immigration control model in the UK that was modern and efficient. The vision for this, was to enhance the use of traveller information by:

– collecting passenger information from plane, train and ferry terminals about individuals entering and leaving the UK:
– analysing data before individuals arrive at the border, including, in some cases, preventing travel;
– presenting the results of analysis to border officials so they can make better-informed decisions about whether to allow entry; and
– creating traveller records so the authorities know whether persons of interest are in the country, and their travel patterns.

Raytheon Systems - a technology and innovation company specializing in defence, civil government and cybersecurity solutions, leading a development consortium (called the Trusted Brothers), was awarded the contract in 2007 to develop the eBorder software system, an implementation component of the £750 million program. However, the contract was terminated in 2010 after the Home Office expressed dissatisfaction towards the execution of the software development project. The Department frequently found Raytheon's solutions unconvincing; conversely, Raytheon Systems felt that requirements were growing and shifting, leading to major disputes, including varying interpretations of different parts of the contract. Nor could Raytheon Systems compel cooperation by agencies or carriers.

The two measurable deliverables that were expected to be completed by Raytheon Systems were never achieved, and entailed:

1. Advance collection of passport data to 95 percent of inbound and outbound passengers by the end of 2010 and 100 percent by March 2014.

2. The second deliverable was to replace the current two legacy systems by April 2011 with a single integrated system responsible for receiving and analysing data in advance and at the border (Khan, 2015).

Following the termination, Raytheon Systems sued the Home Office for wrongful termination. The proceedings led to the award of £150 million to Raytheon plus legal costs by the UK government.

The program costed the UK government more than £830 million which had yet to deliver according to the original requirement on time and on budget. The e-Borders program failed because it exhibited poor project management practice.Propose a project plan to help the UK government "plug the holes" in its current eBorder system capabilities and include a new function that authenticates travellers coming into and exiting from UK. Your project report should:

1. Identify the stakeholders, their influences and impacts, and their information needs and contributions, including proposing a communication plan that informs stakeholders of project progress and to collect user-requirement information from some of them. You need to explain how these sub-plans' information is used in enabling project progress monitoring and variance controlling.

2. Plan the product and project (WBS) scope baselines, clearly modelling the identified system services in terms of their functional and non-functional requirements, to an appropriate modelling depth that would help you confidently identify the appropriate breakdown structure of work activities and output-milestones to deliver the system services. You need to explain how the WBS scope baseline is used in enabling project progress monitoring and variance controlling.

3. Summarise a scope change management procedural guide that explains how scope changes are to be detected and managed by the project team during all SDLC stages of software development.

4. Model a schedule baseline in the form of a Gantt chart, clearly highlighting scheduled project activity and deliverable milestones and how this baseline is used in enabling project progress monitoring and variance controlling.

Recommended Report Structure:

1. Introduction

2. Stakeholder Analysis & Communication Plan
Concepts Introduction
Analysis Assumptions,
Planning approach taken to analyses the stakeholders & develop the communication plan
Stakeholder Analysis Matrix
Recommended Communication Plan
Section Highlights Summary

3. Scope Management Plan
Concepts Introduction
Scope planning assumptions
Planning approach taken to develop this scope management plan
Product Scope Specification
- Functional specifications
- Non-functional specifications
Project Scope Specification
- WBS Specification
Scope Change Management Process Model
Section Highlights Summary

4. Schedule Management Plan
Concepts Introduction
Schedule planning assumptions
Planning approach taken to develop this schedule management plan
Schedule in the form of a summary and meaningful Gantt Chart, with access to full details
Section Highlights Summary

Attachment:- Case study.rar