The Australian Electoral Commission (AEC) provides Australians with an independent electoral service. Within the AEC, the IT Portfolio Management Office (ITPMO) provides governance, assurance, and strategic oversight across the IT portfolio, managing portfolio risks, dependencies, and integrated releases in shared environments and platforms.

• Operating a light-touch Release Approval Board (RAB) scoped to production releases only — a pragmatic fit for an environment where governance frameworks are still being established and organisational buy-in is actively being built.
• Pre-production governance managed by programmes themselves, with escalation to the RAB reserved for releases where risk genuinely warrants it. Closure gate kept to bare minimum by design.
• Three gate checklists — Pre-Production, Production, and Closure — developed collaboratively with BAU teams, covering the critical release readiness requirements at each stage.
• A checklist validation exercise is currently underway: programmes are independently assessing their current practice against each checklist item, with an 80–90% match expected — confirming the checklists codify what good looks like rather than impose foreign requirements.

• Built an automated intake triage system at small scale and pending organisational approval — the same core pattern established at Defence: a web questionnaire linked from intake channels, scoring-based risk tiering, auto-routing to the release team inbox, and an auto-response with links to next steps and onboarding guidance.
• Delivering this in an environment of active resistance — programmes pushing back, management reluctant to mandate it — with CIO approval as the formal backstop.

• Developing and maintaining release management documentation including procedures, templates, and deployment plans consistent with ITIL and transition frameworks.
• Championing automation and auditability in release practices.

• Applying a three-gate release assurance framework — Pre-Production, Production, and Closure — with checklists developed collaboratively with BAU teams covering commercial, technical, security, testing, governance, operational readiness, and support requirements at each stage.
• Managing programme resistance throughout: building the case for governance incrementally, using the checklist validation exercise to demonstrate that the framework codifies existing good practice rather than imposing new burdens.
• Operating with CIO mandate as the formal backstop while working to build genuine organisational buy-in — recognising that mandate without engagement does not produce durable governance.

Developed and applied the Structured Comment Consolidation and Traceability (SCCT) methodology to govern an AI-assisted stakeholder feedback analysis programme covering the Enterprise Release Framework, the Release Approval Board (RAB) Terms of Reference, and a parallel operational document created to capture feedback that fell outside governance scope.

• Grouped related stakeholder comments, applied collective simplification to make consolidated responses easier to read, and traced every comment or group to a verifiable disposition — ensuring full traceability across all documents.
• Used Microsoft Copilot throughout, identifying and actively managing recurring AI-tooling risks: output drift across iterations, ambiguous inputs resolved silently, and errors cascading through the multi-stage appendix structure.
• Designed and iteratively refined a structured prompt instruction set, built from scratch using external AI research tools, to constrain Copilot’s behaviour and direct it to flag ambiguities rather than resolve them silently.
• Verified every AI-generated output before use, ensuring no silent alteration, drift, or corruption of underlying comment data.
• Delivered: a governance-quality, fully traceable stakeholder comment report; updated Enterprise Release Framework; cross-referenced RAB Terms of Reference; a parallel operational document; and a reusable SCCT prompt instruction set for future AI-assisted governance analysis.

Achievement: Delivering enterprise release governance in the most resistant organisational environment encountered in career — against programme pushback, immature BAU, and management reluctance — with CIO approval as the formal backstop. Gate checklists collaboratively developed, validation exercise underway, automated demand triage built and pending approval. The same core governance and triage pattern established at Defence, now being embedded at the AEC.

Provided enterprise-level governance and assurance for the planning, transition, and decommissioning of ICT services across Defence Cyber Operations, protecting Production environments while ensuring Defence’s service capability remained sustainable, secure, and fit for purpose. Applied ITIL-based expertise across Release, Change, and Demand Management to ensure readiness for Design, Transition, and Closure CABs.

• Governed the full ITIL release lifecycle — Development, Pre-Production, Production, and Closure — across a dispersed portfolio of Defence Cyber Operations programmes and projects, many operating across Agile and Waterfall delivery models simultaneously.
• Built and implemented an automated demand triage system on the Defence Digital Delivery Group’s Golden Thread: programmes submitted intake via a web questionnaire linked from the Golden Thread; responses were scored for complexity and risk; submissions auto-routed to the release team inbox; an automated response issued with links to next steps and onboarding guidance; face-to-face validation conducted where risk tier warranted it; and qualifying programmes onboarded to the Release Approval Board (RAB).
• Programmes and projects followed a structured RAB presentation template, covering such important operational readiness requirements as a release risk register, production support documentation with formal handover, and confirmed first, second, and third line support arrangements — amongst others.
• The release risk register was maintained as a formal artefact throughout the release lifecycle by the programme or project, and was a mandatory slide at the RAB — providing a live, up-to-date view of each programme’s release risk posture at the point of approval.
• Identified a critical process gap in the Defence Digital Delivery Group’s (DDG) Golden Thread project delivery methodology, which omitted any reference to SELP governance processes — causing engagement misalignment, visibility issues, and delayed approvals across Defence digital delivery programmes.
• Conducted a gap analysis, identified the accountable page owner, prepared explanatory artefacts, and independently briefed the process owner to build the case for change. Resulting outcome: SELP formally integrated into the Golden Thread as a mandatory project step, reducing rework at CABs and strengthening compliance across Defence digital delivery programmes.
• On mission-critical Defence programmes, exercised sound judgement to uphold standards and safeguard production systems — at times making difficult calls resulting in escalations or project delays that protected Defence’s long-term operational integrity.
• Contributed to reporting mechanisms tracking process compliance and driving Continuous Service Improvement (CSI) initiatives across the Service Lifecycle.

Achievement: Built and implemented automated demand triage on the Golden Thread — converting ad-hoc manual intake into a risk-tiered, engineered process with auto-routing, auto-response, and structured RAB onboarding. Risk-tiering applied at the point of entry. Technologies: Multiple technologies & vendors, Azure cloud. Type: Waterfall and SAFe Agile projects.

Established the approach for Release and Deployment Management, leading the design, improvement, and integration of the Release and Deployment process, collaborating with the federal customer and service provider stakeholders while overseeing resources allocated for the execution of Release and Deployment processes.

• Drove continuous improvement initiatives, managing change and risk associated with process execution and coordination across the multi-vendor environment.
• Expanded and maintained Release Model Libraries.

Technologies: Multiple technologies & vendors (ServiceNow).

FIX8: Business and retail supply of cabling, suspension and display objects. Reviewed and improved the Digital process, inclusive of the digital inventory, using a plan-do-check-act approach.

Technologies: MYOB, Shopify, MS.

Cubic Transportation Systems: industry-leading integrator of payment and information solutions for intelligent travel applications, delivering rail, bus, light rail and ferry contactless smart card technology solutions. Technologies: ServiceNow, JIRA, Confluence, Network, Wintel, Oracle, Java, transport devices and associated software. Type: Waterfall and SAFe Agile projects.

• Ran daily release stand-up meetings with Project Managers to maintain a firm view of release changes and manage risks or issues affecting release readiness.
• Managed 3 major ETS releases running in parallel on an 8-weekly schedule — with unplanned production fix releases running as a separate parallel track on top. At any point in the calendar, two to three major releases were simultaneously in flight across different lifecycle stages.
• Collaborated closely with Project Managers responsible for vendor delivery, aligning vendor deliverables with the overall Release Plan and ensuring business delivery targets were met.
• Reviewed, improved, implemented and managed Program Release Management policies, standards, processes and procedures in line with best practice and business/contractual requirements; integrated with the CMMI Institute Capability Maturity Model.
• Assisted with development and planning of the Program Delivery Plan, ensuring the release plan was developed jointly with Program Delivery and Operational teams.
• Owned all end-to-end aspects of managing and coordinating release processes, using process improvement to ensure continuous quality release improvements.
• Planned and coordinated releases from Engineering into test and rollout for live Operations.
• Chaired release planning meetings with stakeholders to identify software/hardware features expected in current and future releases, following up downstream actions for Deployment, Operations and Change teams.
• Provided detailed release plans, schedules and status to business and IT stakeholders for review and approval.
• Developed agile and flexible approaches to managing a highly dynamic Programme Release pipeline within aggressive delivery timeframes.
• PIR run as a structured stakeholder feedback process: feedback requested via email, categorised by the release team, then confirmed with all stakeholders at a follow-up meeting to verify the categorisation and priority were accurate. An effective change vehicle — findings from the 2014 programme PIRs directly informed the 2017 ETS framework maturation.
• Ran dress rehearsals in pre-production capturing actual implementation and reversion times — validating that the deployment plan would fit within the production window before go-live.
• Protected the integrity and stability of the production environment, working with Change and Configuration Management teams to raise appropriate placeholder Change Requests.
• Established a high degree of trust with the customer through collaboration, joint planning, accurate presentation, and regular release communications.
• Applied a multi-domain release assurance framework across four formal gates — Development, Pre-Production, Production, and Closure — with domain lead accountability and formal sign-off at each stage across Commercial, Technical, Security, Testing, Governance, Operational Readiness, and Cyber domains.

Achievement: Matured the ETS Program Release Management Framework built on PIR findings from the 2014 engagement — implementing improvements to SIT independence, Build & Test Readiness assessment, and Production Deviation Authorisation governance. Scope protected through gate disciplines; production integrity and customer trust maintained across a complex multi-modal, multi-vendor programme.

A bespoke financial management system enabling end-to-end management of the NSW budget. Technologies: Oracle, SQL, Linux, ADF, BPM, SOA, LDAP, Hyperion, Jira, Subversion. Type: Waterfall morphing into Agile projects.

• Continuously developed, maintained and improved the release management process to ensure release deployments met customer business and IT quality expectations.
• Planned and managed the deployment of middleware and application releases into multiple environments (test, training, support and production).
• Coordinated the deployment of releases, ensuring traceability, repeatability and reliability of software component deployment.
• Coordinated technical teams across the IT spectrum to manage middleware and application upgrades and deployments.
• Managed defects, incidents and issues in relation to software releases, and ensured application cutover activities (configuration, user access, rehearsals, data migration) followed the implementation plan.
• Worked with software vendors and cross-functional technical teams to resolve release issues and environment/software defects.

EquiGroup: giving complete visibility and management across all hardware technology assets, 24/7. Group Technology supporting 3 operating businesses each with their own needs and priorities. External supplier: Cognizant. Technologies: Jira, SQL, Visual Studio, .NET. Type: Agile projects.

• Defined structured JIRA issue submission standards — mandatory fields including issue type (Bug, System Query, Data Modification, Improvement, New Feature, Story), concise summary, detailed description with steps and environment details, acceptance criteria, priority, business impact, and supporting screenshots.
• Designed and operated a formal triage process validating every submission against issue type, summary adequacy, description detail, priority correctness, business impact, and attachments — invalid, duplicate, or incorrectly prioritised items rejected or re-routed before entering the sprint pipeline.
• Built a Priority/Business Impact matrix cross-referencing Priority (Critical/Major/Routine/Low) against Business Impact (Catastrophic/Significant/High/Low) to determine the correct SLA tier. Defined SLAs: Critical — 2hr reaction / 24hr resolution / every-8hr comms; Major — 8hr reaction / 48hr resolution / daily COB update; Routine and Low — scheduled through the prioritisation process.

• Introduced 3-sprint forward planning: colleagues confirmed issue priorities three sprints in advance. Individual business groups reviewed their own priorities; Steering Groups reviewed project priorities; the Change Review Board negotiated combined priorities; GM Strategy & Technology gave final sign-off and froze the agreed sprint — no changes permitted except emergencies.
• Sprint scope locked 8 weeks out from production; leadership approval required to alter scope after lockdown.

• Established acceptance criteria as a mandatory pre-development gate: what the system must do, how you know it's fixed, and testing scenarios — nothing entered development without criteria defined to sufficient detail.
• UAT conducted in pre-production: maximum 1 week, UAT tester sign-off followed by separate Customer Advocate sign-off before production approval was granted.

• Managed production deployment to 2 regions on a defined schedule: Wednesday night Asia Pacific, Thursday Europe. Post-release showcase run after each production release.
• Post-Implementation Review embedded as a standard step at the end of every sprint — used for continuous improvement of both testing and release processes.
• Identified that production incident severity classification fundamentals were not being rigorously applied — incorrectly elevated priorities were burying genuinely critical items. Defined the correct classification framework, drove a full re-examination and reclassification, and embedded correct triage into the ongoing process.
• Analysed the end-to-end JIRA workflow — from business requirements through to post-release — redesigned the process in collaboration with all stakeholders, and directed a JIRA engineer to implement the new design. Warmly received across the organisation as it materially improved ways of working.

Achievement: Designed and personally presented a complete IT process re-engineering initiative — the 6-step JIRA Demand Stream — to the full organisation via team meetings. Shifted IT from reactive, incorrectly prioritised demand to structured, SLA-governed, forward-planned delivery across three operating businesses. Three-sprint advance planning with scope lockdown at −8 weeks; Priority/Business Impact matrix with defined SLAs; Customer Advocate approval gate; dual-region production deployment.

Industry-leading integrator of payment and information solutions for intelligent travel applications, delivering rail, bus, light rail and ferry contactless smart card technology solutions. Technologies: Network, Wintel, Oracle, Java, transport devices and associated software, ServiceNow. Type: Waterfall and SAFe Agile projects.

• Greenfield build of the ETS Program Release Management Framework — designed to solve the programme’s core problem of fluid release dates and reactionary planning, establishing structured forward planning, internal gating, and executive accountability from the ground up.
• Built the framework around the Target Operating Model (TOM) Integration Working Group requirements, contractual obligations to TfNSW, emergency fix procedures, and formal executive accountability to the ETS Programme Control Group (PCG) and the Executive Joint Steering Committee (EJSC).
• Managed 3 major ETS releases running in parallel on an 8-weekly schedule — with unplanned production fix releases running as a separate parallel track on top. At any point in the calendar, two to three major releases were simultaneously in flight across different lifecycle stages.
• Conducted the first Cubic internal Build & Test Readiness assessment — establishing the production readiness gate across all stages through to pre-production. Nothing could bypass it before progressing to production.
• Ran dress rehearsals in pre-production capturing actual implementation and reversion times — validating that the deployment plan would fit within the production window before go-live.
• Established Production Deviation Authorisation (DA) governance: any deviation from the agreed release process required formal authorisation. A production incident (incident 201176) was confirmed via Post-Implementation Review to have been caused by a DA bypass — validating the governance and demonstrating the cost of circumventing it.
• Implemented PIR as Release Gate 5, structured under ITIL Continual Service Improvement: What did we do well / What could we do better / Future Focus — with findings formally feeding back into the next release cycle.
• PIR run as a structured stakeholder feedback process: feedback requested via email, categorised by the release team, then confirmed with all stakeholders at a follow-up meeting to verify the categorisation and priority were accurate. An effective change vehicle — findings from the 2014 programme PIRs directly informed the 2017 ETS framework maturation.
• Protected the integrity and stability of the production environment through engagement with internal and client Change Advisory Boards.
• Engaged and managed internal and external stakeholders to inform and report on release management and environment aspects across the multi-vendor programme.

Achievement: Greenfield build replacing reactionary planning practices — the ETS Program Release Management Framework established structured forward planning, internal gating, executive accountability, and Production Deviation Authorisation governance where none had existed. PIR (Release Gate 5) confirmed that a DA bypass caused production incident 201176, validating the governance and the cost of circumventing it. Foundation built on in the 2017–18 engagement.

GT-X Professional Services supports technology and business executives with meeting the demands of scaling up IT and business projects with delivery assurance.

• Consulted as Release Management SME in a workshop with Westpac and GT-X (12 participants), analysing Release Management roles in collaboration with both organisations.
• Delivered to the Westpac Workforce Optimisation team: horizontal analysis across job activities, skills and capabilities; vertical (role-specific) analysis; role comparison (current versus future); identification of new roles, changes and anomalies; future-state job category acceptance; segmentation analysis and alignment to current strategy.

Replaced human resources and payroll systems for TAFE colleges with SAP. Team size: 2 core. Technologies: Network, SAP, Mainframe, Citrix, AD, Wintel, SQL, IIS, Oracle, Unix, TIBCO, Remedy. Type: Waterfall projects.

• Worked for the NSW Department of Education on the technical cutover of SAP HR and Payroll into production for NSW TAFE colleges — part of the NSW Government's $755M LMBR programme. Responsible for managing multiple parallel streams: infrastructure establishment, application installation and connectivity, data load, acceptance against agreed functional, technical and business criteria, deployment planning, and change control governance through both the LMBR and ITD Change Advisory Boards.
• Executed against a detailed cutover plan tracking milestone and checkpoint completion to ensure the transition proceeded without disruption to employee pay runs.

Achievements: Quality-assured the successful Technical Cutover into the live production environment.

AMP AXA Integration project. Team size: 4 core, plus 12 Portfolio and Program Release Managers reporting up to Enterprise Release Managers. Technologies: Network, Mainframe, Wintel, SQL, IIS, Oracle, Unix, TIBCO, WebSphere, MQ, Remedy. Environment: 3,000+ physical-server applications, 400+ systems. Type: Waterfall projects.

• RG1 — Release Gate Initiation (up to −20 weeks): Release registered; business case, project schedule, change management approach, Systems Impact Surveys, solution architecture and requirements submitted; test environment and data requirements confirmed; release pipeline, risks and issues register, and release console opened.
• RG2 — Release Gate Assessment (−20 to −8 weeks): Initial complexity assessment via Systems Impact Survey; release scope locked and approved at −16 weeks; Enterprise Release Delivery Plan drafted; release go-live acceptance criteria and business/operational readiness criteria in draft; Application Impact Matrix and Cross-Project Impact Matrix initiated — the primary dependency tracking and cross-stream impact management tools across concurrent release streams; Release Working Group established; Release Participants Single View Timeline published.
• RG3 — Release Gate Design and Planning (−8 to −4 weeks): Test environment and data requirements finalised; E2E implementation and rollback plans drafted; PVT plan, system test report, technical and business release notes in progress; business/operational readiness criteria formally agreed and signed off.
• RG4 — Release Gate Release Acceptance and Implementation Readiness (−4 to −1 week): Final complexity assessment; implementation plan completed; final Application and Cross-Project Impact Matrices; Business Sponsor and IT Final GO/NO-GO; Business Impact Assessment checkpoint; release console and participants timeline finalised; Business/Operational Readiness Report delivered.
• RG5 — Release Gate Implementation and Measure (−1 to +2 weeks): Code freeze; production go-live; Enterprise Release IT and Business sign-off; pre- and post-release communications; actual run times recorded against plan; warranty period tracked to completion with End of Warranty notification.
• RG6 — Release Gate Handover and Closure (+2 to +4 weeks): Post-Release Review and Report; IT change records closed; risks and issues register closed; release closure communications; formal handover to BAU operational teams.

Achievement: Greenfield build — no release governance existed before ERLF. The framework established a centralised enterprise release calendar with dates planned two years in advance, a six-gate lifecycle from initiation through post-release closure, mandatory deliverables scaled by project size, and formal accountability across all release-critical roles. Complexity assessed via Systems Impact Survey at RG2 Release Gate Assessment, further assessed at RG3 Release Gate Design and Planning, and finalised at RG4 Release Gate Release Acceptance and Implementation Readiness — providing a progressive risk view through the lifecycle. Scope locked at RG2 Release Gate Assessment (−16 weeks) and protected through go/no-go disciplines; urgent changes handled through formal priority escalation, not late-stage scope changes. Delivered across a 3,000+ server, 400+ system environment with Warranty.

Integrated Point of Sale Programme: implementation of the Beanstore point-of-sale application from IBM Business Partner PCMS. Team size: 6 core, matrix-managing development, infrastructure, vendor and support teams (10 teams / 50 people); impact on thousands of people across all M&S stores. Technologies: Network, Wintel, SQL, IIS, WebSphere, MQ, PCMS Beanstore, HP Quality Centre, Remedy. External suppliers: PCMS, Fujitsu, Cognizant, Cable & Wireless, Logicalis, Tata Consultancy Services, EMC.

Environment: VM Hosts 300–400 · Physical servers 4,000–5,000 · Applications 1,000–2,000 · Systems 2,000–3,000.

• Release-managed a critical up-scale change to the POS application and architecture to resolve performance issues that, if mishandled, would have prevented M&S stores from trading online or offline.
• Validated the WebSphere scale-up of web servers, channels and trade nodes — along with Network Load Balancer and IIS changes — through rigorous ‘what if’ failure testing on critical infrastructure: deliberately inducing failure scenarios to observe system behaviour and recovery, building the confidence and surety needed to proceed with the scale-up.
• Managed teams of direct and non-direct control to meet project delivery dates through strong communication and continuous coordination.
• Maintained continuous interaction with the wider programme, business, architects and change management given the critical, high-business-impact nature of the project.

Achievement: Implemented Point of Sale system scale-up improvements on time, with immediate performance improvements to the live environment.

Integrated Point of Sale Programme: implementation of the Beanstore point-of-sale application from IBM Business Partner PCMS. Team size: 15 core, matrix-managing development, infrastructure, vendor and support teams (12 teams / 60 people). Technologies: Network, Infrastructure, Mainframe, Unix AIX, AD, SQL, IIS, WebSphere, MQ, PCMS Beanstore, HP Quality Centre, Remedy. External suppliers: PCMS, Fujitsu, Cognizant, Cable & Wireless, Logicalis, Tata Consultancy Services, CapGemini, EMC. Type: Hybrid Waterfall/Agile POS project.

Environment: VM Hosts 300–400 · Physical servers 4,000–5,000 · Applications 1,000–2,000 · Systems 2,000–3,000.

• Delivered a complex solution combining the PCMS Beanstore POS application with Network, WebSphere and SQL architecture in a virtualised environment interfacing to multiple M&S application systems.
• Held overall Program Release Management responsibility, coordinating release program activities and managing non-production and production environments, including infrastructure provisioning and cross-domain release integration testing.
• Created, managed and executed the Release plan to move deployments into production, and managed teams building and releasing application, infrastructure and software implementations across Wintel, Unix and Mainframe.
• Defined, managed and supported the environment release plan in MS Project, feeding into the programme plan using the Summit PM methodology.
• Ensured compliance to policies and operational processes/procedures, release integration and production validation, with all releases configuration-managed via a central repository.
• Released the pilot IPOS project to 60 M&S stores and was instrumental in the mass roll-out to the remaining 600 M&S stores.

Achievement: Brought in to deliver the solution after the original supplier had failed to deliver on time; delivered the system on time despite aggressive timelines.

• Assigned to oversee mainframe application releases ensuring timely implementation.
• Responsible for ensuring that the test infrastructure was built correctly to production specification.
• Trained the new development team to adhere to release management principles and disciplined procedures.
• Worked closely with Project Managers within the Summit methodology to ensure proper release planning.
• Managed and trained the new offshore supplier mainframe release managers.

• Assigned to oversee the delivery and release management of servers and application software.
• Responsible for ensuring applications were built to production specification in time for integration testing.
• Introduced scrums, quality control checks, defect tracking and change and configuration controls.
• Troubleshot application problems including software defects, issues, risks and change requests.

• Supported Project Leaders across various initiatives providing an excellent transition service for a large number of applications through testing environments into production.
• Provided technical project leadership for the upgrade and changeover of the BizTalk testing environments.
• Coordinated the e-business application and infrastructure teams to ensure that change management to pre-production environments would be compatible across all systems.
• Oversaw and supported the creation of pre-production and system test environments.
• Undertook the transition and ensured quality of release of the retail e-business website re-launch.
• Implemented a production-like change process in the pre-production environment to risk-mitigate the large volume of changes, with associated risk and impact controls throughout the Amazon migration.
• Ensured that the security patching process was correctly deployed in the pre-production environments.

• Assigned to build and support the backend dedicated pre-production environments at M&S Central Testing Services.
• Responsible for implementing, scheduling and supporting the data conversion and all testing within the environments.
• Identified the systemic root cause of recurring production failures: test environments did not mirror production, invalidating pre-release testing. Made the case for a permanent fix.
• Proposed, project-managed and built a dedicated pre-production environment that mirrored the live M&S production environment — significantly reducing go-live failures and becoming a permanent strategic asset.
• Maintained the environment as a trusted test oracle — a golden master and ground truth so reliable that its outputs were taken as definitively correct — input interfaces from upstream systems fed it continuously, output interfaces were severed to prevent data escape, and production parity was restored via a rigorous scripted process: production backup, restore to pre-production, all configurations including interface configurations applied via batch, parallel batch execution, and automated shakedown and regression. What started as a core system mirror expanded to encompass the full production ecosystem as every team sought access to a trusted production-equivalent. When a critical system failed under severe time pressure, the oracle made it quicker and easier to trace data through the multi-system mesh, identify precisely where it diverged, and then reason about why — rather than hunting blind across hundreds of interconnected systems.
• Created and supported the automated HP WinRunner regression testing scripts, eliminating manual regression effort and establishing repeatable, reliable test execution as standard practice.
• Specified all environments ensuring end-to-end security and integrity.
• Part of a team that established and then continuously evolved release documentation standards — requiring implementation plans precise enough for anyone to execute without prior system knowledge. Documents were QA'd before the release ran; the author given the opportunity to correct deficiencies first. During pre-production execution, any document non-conformances were raised as defects alongside release defects — with every release tested through all environments on the way to production.

Environment: VM Hosts 300–400 · Physical servers 4,000–5,000 · Applications 1,000–2,000 · Systems 2,000–3,000.

Achievement: Designed and delivered the M&S pre-production environment from concept to production — a fully operational second production ecosystem serving regression, performance, operability, integration, UAT and DevOps testing simultaneously, and functioning as a trusted test oracle — a golden master and ground truth so reliable that its outputs were taken as definitively correct — that dramatically reduced diagnostic time when critical systems failed under pressure. Automated regression testing with HP WinRunner eliminated manual effort and established repeatable test execution as standard. The environment and capability grew to the point where management established a dedicated team to sustain and evolve it.

Details available on request.

Led the application team making Year 2000 changes for the Integrated Customer Ordering System (ICOS) at M&S London. Responsible for test and production environments, releases, and release cutover. Observations made during this role directly led to identifying the systemic pre-production environment problem and proposing the solution built in the following role.

Details available on request.

Details available on request.

Legacy replacement of COBOL with Objectstar 4GL across Old Mutual's COBOL applications. A twelve-year career beginning as Network Installer and Network Controller at Old Mutual's head office, then progressing through Programmer, Methodologies Analyst, Developer (Individual Marketing and Agency Systems), Design Consultant, and Developer (contract) — building deep foundations in application design, release, and structured delivery methodology. Included the Huron Implementation programme as Individual Business Unit Developer and Objectstar Consultant.