top of page

Who I worked for...

Accenture is a global technology and consulting organisation in more than 120 countries, across more than 40 industries and are the number one largest independent technology services provider. The brief description Accenture provide as a company overview is as follows:

 

“Accenture is a leading global professional services company, providing a broad range of services and solutions in strategy, consulting, digital, technology and operations.”[1]

 

Accenture work on a client basis, they have a large number of clients ranging from large well-known companies in the FSTE 100 (along with themselves) to smaller lesser known companies. Accenture’s main assets are their employees; employees of Accenture search for project placements with clients (or are found by current Accenture projects with clients) using their internal project positions availability website. Accenture focus on providing highly skilled personnel and delivering the personnel to clients who require quick access to the knowledge of those who have been trained by Accenture.

 

[1] (Accenture UK PLC, 2016)

What I did...

Java development – Carrying out Java development and programming for various different tickets including security improvements (added security to receiving messages), refactoring of code, code performance improvements and new feature implementation.

 

Version control set up (using Git) – Designing the new Git model for the move from SVN managed code to Git managed code. Including deployment processes through the Git model to the live environment (production) and developer process for committing and pushing code changes. Also maintaining, fixing and updating the Git system when needs be.

 

Version control management – Managing the overall Git model i.e. ensuring the Git model/ process is retained and followed throughout development and deployment. Keeping the Master branch the most stable branch that should have only fully tested code and that this is the only branch to be deployed to staging (pre-production) and live (production)

​

Deployment management – Carrying out the end of sprint deployments (fortnightly) and ensuring only fully tested code is getting deployed. Managing the deployed tickets and checking that these tickets are all merged successfully into the Master branch. Ensuring the deployment(s) are successful for all components of the data warehouse. Handling the change requests and working with operations management to organize the deployment times and process.

 

Testing

  • Ticket testing – Testing individual tickets (pieces of work) throughout the sprint, and at the end of sprint if needed, to ensure functionality is correct and fulfils the requirements of the ticket. This includes writing test cases which will fully test the functionality/ fix of the ticket, documenting the results and deciding on a pass or fail to determine if the ticket should be deployed with the sprint release.

​

  • Smoke testing (after deployments) – Carrying out a full smoke test of the system on the individual components. This includes monitoring the system through the entire smoke test, checking the results and reporting any issue that may arise from this.

 

  • System regression testing – During a major component change, which changes the core functionality of the component, a full regression test is needed. This is similar to the smoke test but is more focused to the individual component(s) which requires extensive testing of the functionality and the impact, if any, to the system as a whole. Test results are documented and checked and problems reported if needs be.

 

  • Performance testing for software releases – Carrying out spike and soak tests on the main components of the data warehouse infrastructure to determine impact and actions required due to software releases. These results are documented and from this actions to prevent component failures are determined and carried out.

 

Data analytics- Analyzing messages reported by users and combining this with metadata to extract meaningful information presented in an effective manner using Looker (third party BI tool). Including creating Looks (pages to present the data), dashboards, PDTs (scheduled builds of tables) etc. and coding specific LookML views which are used to access data in certain way that wasn’t yet implemented.

 

SQL development – This closely ties in with the data analytics carried out on Looker as Looker is SQL at its core. SQL has also been used in different areas across the database system.

 

Data warehouse infrastructure – Monitoring the data warehouse graphs and status to help identify any irregular or problematic patterns or occurrences and helping to fix these issues.

 

Incident work – working on active incidents with appropriate urgency depending on the priority of each. If the incident was a priority of one this means that the incident is/ has the potential to be largely business impacting so the issue needs to be determined and fixed in a timely fashion. After an incident is resolved an impact assessment is to be carried out to ensure we understand the full impact that such an incident caused on the business.

 

General ticket work – Working on various feature and bug tickets related to a variety of areas.

bottom of page