CV - Steve Ridley

Latest Role - Project/System Architect


American Express Europe - Nov 2002 - Present
Machine Environment
IBM 3090 under MVS/XA, Unix SUN 440 Solaris , Windows XP
COBOL/3, SQL, JCL, Unix shell scripting, Java J2SE, REXX, CICS, IMS, LYNX CE-script
DB2, UDB, TSO/ISPF, Microstrategy, Web Focus, Changeman, QMF, Datamanager, File aid, Infoman, Visio, Ms Word, Excel, Powerpoint.

My role has covered multiple standard IT roles, Project Architect, System Architect, SME, BSA and elements of project management. For many small to medium sized projects I have been effectively working as the lead technician combining several technical roles with a business facing role. My work is most rewarding when I am given the responsibility and control to drive a project from feasibility to implementation. My responsibilities have included the following - by phase:


Consultancy on technical practicality of feasibility options. Documentation of feasibility options.

Creative input to the requirement definition process. Consultancy on practicalities and costs of different requirement options. Documentation of requirements.
Design Team Leader monitoring progress: Creation of high level design, database design, process flow designs; QA of detailed designs.
SME consultant for the offshore build team
Test planning. Creative test scenario production liaising with BE and NPD. Tracking test progress. Problem analysis/resolution using SME knowledge. Allocation of issues to test personnel.
Support for implementation & rollout on & off site covering nights & weekends.

Areas of the Amex Corporate systems I have gained subject expertise on include: ASDB, ABC, EBTA (batch & online); CAPS; TMS; Business factors; @work; @work re-post; Co-brand revenue share, MST statementing & EBTA statementing.

As with my previous role for Amex global statementing I have been working in a matrix managed, multi-project, multi-role environment, with team members from various vendors and cultures spread around the globe. I strongly believe that these environments will be successful and efficient and that accurate, timely communication is critical to this success.

In September 2004 I spent 2 weeks in Phoenix picking up the US ABC reporting system. Although the business function and technical environment were well outside my comfort zone at the time I learned both virtually from scratch and took over responsibility for the system a month later. Since then the availability and reliability of ABC has been improved significantly despite problems with funding.