Roles & Responsibilities

During my just more than two years at TolPlan (Pty) Ltd. I had several (concurrent) roles, which included:

• Consultant to business and technical project managers: My responsibility was to ensure that sound project management principles and practices were followed throughout the enterprise – in both the business and technical areas of all projects;

• Methodology Lead & Mentor: I initiated and headed up the design, definition and implementation of a well-structured software development methodology – based on the OMG Objectory standard at the time (I also led the establishment and definition / design of the artifacts which had to be produced as deliverables of the implemented software development methodology);

• OO Analyst / Designer: I was the lead analyst / designer of a totally new toll collection and management information system which had been successfully deployed locally and internationally (the design was done in the Unified Modelling Language making use of the IBM® Rational® Rose Visual Modelling tool, which I’ve also successfully integrated with the Merant PVCS version control software at the time – something which hadn’t been done anywhere else at that stage);

• Programming Quality Assurer: My role was to ensure that all code produced for the system conformed to the required coding standards which I formulated (Delphi 2.0 / Delphi 3.0 / Delphi VCL);

• PVCS Version Control Software Administrator: I had the role of configuration manager on the projects, ensuring that sound SCCM principles were embedded and adhered to throughout;

Other: I served on several internal committees of the organization, including the QA committee, the configuration control committee (CAB – Change Authorization Board) and the EPMO management structure of the company, and by doing this, I provided general guidance and mentoring not only to a team of project managers, but also to other domain specialists, analysts/designers, coders and testers.