Geoff was asked to Project Manage and lead the work of five client-side personnel in a new Business Architecture team. Workstreams included Methodology Creation, Consolidating disparate requirements from multiple sources, to De-duplicate and rationalise them, and to Manage the Requirements process from there.
Work involved liaising heavily with the PMO team to ensure that best practise was followed. Experience and reputation ensured I was called on as an expert contributor for changes to this organisation.
The role included working together as part of the deliverables of a larger team which was responsible for Project Managing the Design and Implementation of the overall systems that would be needed to create a whole new business within this Telecoms company

Geoff was responsible for creating and maintaining a Programme Management Office for this large Telecommunications company, with the primary aim of ensuring that the Programme (itself creating a Openreach, a new division of BT) was constrained to strict Financial, Resource and Scope control under an agreed Quality Plan.

Geoff worked within the marketing team in The Strand to design, develop, test, and deploy a single, global solution to filter off-net content within each of the Operating Companies within the Group. Geoff’s role was to deliver 5 key documents as part of the Business Analysis workstream:
Requirements gathering is the key to documenting a comprehensive understanding of the solution by liaising between the Marketing Executives and detailed Design Architects.
Use Case definition supports the contractual scope of the off-net filter to be delivered by the vendor. These use cases will detail the movements at an understandable level of detail the primary scenarios in which the filter will be used.
Service Level Requirements documents the minimum system functionality and support processes of the off-net filter. This together with the Technical specifications made up the Service Level Agreement (SLA).
Operations and Customer support requirements are gathered from 16 Operating Companies (OpCo) to ensure that the varying requirements of each OpCo are fed into the Product Business Process definition.
Product Business Process definition defines a template from which each OpCo can begin creating detailed procedures specific to their operating environment.