Johan Wheeler

Background

About Johan Wheeler

During my years as IT professional, I have had the opportunity to be involved in various facets of the IT environment. I have good understanding of the architecture and challenges involved in areas such as enterprise solution design, development and support. I obtained experience in multiple capacities, from Product specialist responsible for installing, configuration and support of document management and workflow systems to Business Analyst where I was responsible for leading JAD sessions and creating the business, functional and technical requirements, ensuring successful implementations. During this time, I was concentrating on Document Management and Workflow (BPM) solutions within the mining and insurance industry and moving to item processing within the financial environment. This allowed me to obtain extensive experience in supporting and maintaining the operational and technological environments. Following System Architect, I performed the role of Support Manager, responsible for the support of systems within the financial environment, as per outsourced support agreements. This entailed ensuring the support was delivered in line with the best practices as defined within the IT Infrastructure Library (ITIL). Part of my duties still included advising as a Systems Architect, which led to me accepting a role as Enterprise Architect where I have the responsible for the end-to-end development and integration of the solution, as well as fulfilling the role of Operational Manger. In 2014 in moved to Barclays Africa Group Limited (ABSA) where I started as a Service Architect – responsible for service enhancements and improvements within the Barclays Africa, Technology Operations. Progressing to, Manager, Service Transition (Release Management). Within this role I am responsible for overseeing the service transition area which focuses on the controlled deployment of software into the production environment. The includes the verifying of the compliance of the projects and investigating and combining of all deployment plans for an integrated, non-integrated and stand-alone deployments. During the last few years we have not experienced a major incident related to large software releases. This was partly due to taking a fresh approach to the services being delivered. By loosely coupling the services the dependency between testing and batch release was largely negated. This allowed for understanding the impact of a defect and the possible impact to batch release and bringing the bank on-line.