Episode #11

• Graham is 67 and lives in Melbourne. 
• After 3 attempts, has finally successfully retired and now focuses on perfecting his golf game. 
• Studied Electrical Engineering at Royal Naval College in Plymouth and received his Masters in Systems Engineering from RMIT. 
• Started at 15 as a technician in the NAVY.  When he realised he was very bad at it, decided it was time to get a degree in engineering. 
• Worked in the NAVY for 20 years, and once he left spent the next 30 years building Ships, Radars, Air Traffic systems, armoured vehicles…. to list just a few! 
• His first role outside the NAVY, was the ‘real engineering’ he was seeking…. his first real engineering role was building the ANZAC ships, the design, procurement, integration and delivery of the Combat System. 
• Graham discovered he was very good at managing engineers – on 1 project he was involved in the management of 400 software engineers. 

• It’s so important to get the requirement management and specifications right at the start of a project, or you’ve got a serious problem. 
• Need to understand what the customer wants.  The customer has a big part to play in clearly communicating what exactly that is. 
• When writing a contract with a requirement in it, the test specification should immediately cater to make it clear how you are going to accept that requirement. Be very clear on acceptance criteria, just as clear as the requirement. 
• Far too often, requirements have a level of ambiguity.  Customer must be specific on what they want. 
• More work and involvement need to take place at the very beginning, the inception, of a project to ensure clarity of purpose from the very beginning.

• A Systems Engineer is not specific to any particular discipline in engineering.  It’s engineering that brings all various systems together.  It can be very interesting, challenging and at times, complex.  It’s the parent that brings all other elements together. 
• the management of stakeholder expectations can be the most challenging part of engineering. 
• Delivery of the project was the most satisfying. 
• Engineering in the NAVY isn’t about design engineering – it’s mostly people-management. 
• To have a team that enjoys what they’re doing is very satisfying. 
• If you surround yourself with good people, you will typically exceed expectations. 
• Staff selection is very import.  When you employ a group of people, give them a challenge that takes them to the limit. 

An engineering item for discussion. The speed that communication technology is developing. 

An engineer to admire. His son, James Pollock (software engineer) knew when he was young where he wanted his heart to lead him.  Has achieved balance between engineering and life.

Facebook: @FugaVeloce 

Insta: @Fuga.Veloce

Website: www.engineeringheroes.com.au 

Facebook: @BeerWithAnEngineer

Instagram: @BeerWithAnEngineer.podcast

LinkedIn: Beer With An Engineer

Melanie on LinkedIn

Dominic on LinkedIn 

Our drinking game.  You can’t have a beer with an engineer without having a drinking game!!  Anytime Dom says “ummm” or Mel says “so”… drink up! 

Our winner.  Thank you to our sponsor – Fuga Veloce.  The winner of our competition, and the 60-minute Joy Ride around Sydney in a Ferrari 360 goes to “Jogowhere”.  Thank you to everyone who provided us with a review.  We hope you continue to enjoy listening to our Podcast.