Career History

Executive IT Architect in the DevOps Global Tiger Team, IBM Hybrid Cloud @ IBM

January 2016 to date

A continuation of my previous role sees me focusing on DevOps when applied to the plethora of cloud deployment topologies (traditional IT in an organisation's data centre, on-premises cloud, off-premises dedicated cloud and off-premises shared cloud). It also places a focus on helping clients address some obvious challenges in the DevOps space, such as how to ensure compliance of regulations (such as segregation of duties) in a DevOps landscape, how to govern a DevOps project, how to involve suppliers when moving to DevOps, how to transform at an organisational level, which DevOps-related metrics to apply, how to get started, and so on. In other words, all of the hard problems that books don't give you answers to! The recommendations provided are, of course, based on the experiences gleaned from working with a multitude of clients across the globe and spotting practical patterns of success.

Executive IT Architect in the IBM Cloud Worldwide Tiger Team @ IBM

January 2015 to December 2015

IBM undertook at major reorganisation at the start of 2015 and my move to the new Cloud business unit was an obvious and welcome outcome, given that many of the challenges that clients faced (such as environment provisioning) would be addressed through a cloud capability (off-premises, on-premises or hybrid). The move also put my primary interest - the alignment of Architecture, Agile and DevOps - front and centre of my day-to-day job. During this period I picked up the mantle of running 1-day DevOps Innovation and Optimisation Workshops around the world, which were extremely effective in helping clients understand a) their challenges, b) DevOps (and cloud) concepts, c) potential solutions and d) what other organisations in their business domain were doing.

Financial Services Sector Industry Lead in the IBM Rational Worldwide Tiger Team @ IBM

April 2013 to December 2014

This was my first business development role within IBM, where I moved from a delivery role to the pre-sales "front line" of client engagement, where my objective was to help clients understand the relevance of technology as an enabler that would help them meet their business goals. Most of my time (as the job title implies) was spent working within the Financial Services Sector and I worked with many large enterprises around the globe. This "shift" was deliberate; I was keen to get a perspective of the IT industry at large and be in a position to spot patterns and form opinions whereas, in previous roles, I would tend to spend a good proportion of my time working within a single client (which was also rewarding, but for different reasons!).

Chief Architect, IBM Software Services for Rational @ IBM

January 2010 to March 2013

This was a client-facing role, leading engagements around the world while, at the same time, producing assets that would accelerate the implementation of Rational-centric solutions. With the increasing focus on the complementary nature of agile and architecture (despite what some may say!), I wrote a chapter on the very topic in the book "Agile Software Architecture" during this period, based on practical experiences working with clients.

Worldwide Technical Lead for Solution Architecture @ IBM

April 2007 to December 2009

In this role I was responsible for setting the standards by which solutions were consistently defined and assured, leading to the implementation of a method including a Development Environment Maturity Model. During this period I engaged with many clients around the world and, during this period, co-authored the book "The Process of Software Architecting" with Peter Cripps, based on the lessons we'd learned through our client engagements.

Rational Brand Architect for UK, Ireland and South Africa @ IBM

January 2005 to March 2007

In this role I set the technical direction of Rational UK, Ireland and South Africa, building relationships with the broader IBM. At the same time, I also continued to be involved in strategic architecture-centric client engagements since this is where I believe the "rubber hits the road" and where the most useful lessons are to be learned; practice rather than theory!

Worldwide Community of Practice Lead for Model-Driven Development @ IBM

February 2003 to December 2004

I joined IBM as a result of the acquisition of Rational Software in February 2003. The Model-Driven Development Community of Practice, an element of the Rational field infrastructure, had over 300 members from many areas of the IBM organization (primarily from Rational, WebSphere and IGS). This role has two main aspects to it. The first was a coordination role where I was responsible for instigating and leading a number of community-related initia-tives, mainly around Business Process Modeling, Model-Driven Architecture, Asset-Based Development, Enterprise Architecture and Service-Oriented Architecture. The second was a client-facing role. During this period significant engagements in an architecture-centric capacity were undertaken across Europe.

Chief Architect @

June 1999 to November 1999 produce a suite of web-based services - the "showpiece" being ZyWeb - a web site authoring tool that is itself deployed over the web. My role at Zy was to implement an appropriate web architecture that would allow Zy to extend the range of services on offer. This included the addition of single-user services such as email, calendars and scheduling, and also the addition of enterprise-level services, such as those offered by a typical ERP system (such as customer management and order processing). It was Zy's intention to facilitate the integration of 3rd party products, and provide the "shop window" by which these services can be offered.

Senior Technical Consultant @ Rational Software Corporation

December 1999 to February 2003

As a member of Rational's Worldwide Strategic Services Organization, I was involved in helping organizations both customise and implement the Rational Unified Process and Rational toolset in architecture-centric initiatives. I dealt with a variety of clients in various business domains, including banking, consultancies, utilities, public sector and travel / transportation. During this period I co-authored the book "Building J2EE Applications with the Rational Unified Process" with Kelli Houston and Wojtek Kozaczynski.

Chief Software Architect @ Metapath Software International (MSI)

June 1998 to May 1999

MSI produce software tools for telecoms operators (such as Vodafone, Cellnet, One-to-One, Orange and Sprint). Together, these tools provide an enterprise-wide solution - there are tools for planning, analysing and optimising radio networks, together with tools that handle customer-related activities (such as billing). When I joined, MSI were in the process of reengineering their flagship products, and also implementing new products that fill "gaps" in the enterprise solution. These initiatives were based on a common software architecture that I was responsible for defining. I was also responsible for coordinating the work undertaken by 30 technical staff (in both Newbury and London) that were responsible for focusing on various aspects of the implementation of this architecture.

Chief Technical Architect @ SSA Object Technology Ltd.

November 1995 to June 1998

Systems Software Associates (SSA) provides software solutions in the Enterprise Resourcing and Planning (ERP) sector. SSA acquired Integrated Objects (see below) with a view to using the NeWI technology from Integrated Objects to re-engineer their flagship ERP product. This NeWI technology evolved into a middleware product known as a Business Object Facility (BOF). I was Chief Technical Architect of SSA's BOF, and co-authored SSA's submission in response to the OMG's "Common Business Objects and Business Object Facility" RFP. Unfortunately, this standard was never adopted by the OMG, mainly due to the diversity of submissions made. This role called for regular attendance at, and contribution to, the OMG's Business Object Domain Task Force (BODTF). During this period I was also Technical Director of the Open Business Object Environment (OBOE) Esprit project. The objective of this project was to demonstrate the BOF vision. During this period I co-authored the book "Building Business Objects" with Oliver Sims.

Technical Architect @ Integrated Objects Ltd.

August 1993 to November 1995

I was a founder member of Integrated Objects - a joint venture between IBM and Softwright. Integrated Objects was formed in order to "productize" and market the NeWI OO infrastructure developed at Softwright (see below). I had a number of roles at Integrated Objects. First, I was responsible for leading the team responsible for the design and implementation of NeWI. Second, I was responsible for implementing automated software testing and production mechanisms. Third, I was responsible for writing all of the user documentation. I also spent a year (part-time) in a consultancy capacity with National Power, running a project to produce a system that simulates the electricity market. I was responsible for leading a team of 5 people, and for the analysis and design of the system (using the Object Modeling Technique design methodology).

Senior Technical Consultant @ Softwright Systems Ltd.

March 1993 to August 1993

Softwright is a software house that deals mainly with bespoke developments on behalf of its clients. At Softwright I was technical lead of the team responsible for producing an OO infrastructure known as "NeWI" (New World Infrastructure). NeWI predates both CORBA and DCOM, and implemented its own Object Request Broker (ORB). NeWI proved to be so successful in-house, that Integrated Objects was formed to develop and market NeWI externally.

Principal Software Engineer @ Racal Redac Systems Ltd.

March 1988 to March 1993

Racal Redac (now Zuken Redac) produced electronic CAD products that assist with the design and construction of printed circuit boards. Here, I was team leader of the Framework Products Group. This team produced the technical framework for the construction of the company's products. I also produced and ran an OO Analysis and Design training course for employees both in the UK and in the US. This included the development of an in-house method, which itself included various standards and guidelines.

Senior Software Engineer @ Dowty Fuel Systems Ltd.

September 1985 to March 1988

Dowty Fuel Systems is an engineering company that produces (primarily) aircraft fuel control systems, but also runs MOD-related projects. During this time I wrote software to automate the mathematical modeling of a torpedo propulsion system. I also produced real-time software for testing aircraft fuel control systems in a controlled (test rig) environment.