An experienced DevOps consultant with over 20 years in the IT industry. A background in software engineering,dealing with everything from embedded systems through to fully distributed systems.
Hi Brett, what have you been up to recently?
Hi Andy, I’ve recently finished a three year engagement as DevOps Practice Lead with a large Government organisation, having been responsible for significant portions of their CI/CD pipeline processes adopted by all the various teams.
Can you take me through that journey?
As part of a business change programme, my team and I, were responsible for radically transforming their existing CI processes for multiple bespoke applications into a true CI/CD pipeline giving the organisation far greater agility than they had previously. They went from quarterly releases to two weekly incremental releases with greatly improved idea-to-production cycle times.
In addition to being responsible for the CI/CD processes we were also part of the live support team for the applications delivered upon our platform. Here the use of an everything-as-code, immutable infrastructure and cloud native approach drove improvements as well. We ensured that applications could deploy their own monitoring, alerting and custom dashboards with the application deployment. We also ensured that the tools we used were equally accessible to development teams from the outset, the result was development teams delivering dashboards that had operational as well as business value up-front as part of the application deliverable.
In order to achieve all this we had to engage early and constantly collaborate with our colleagues in Architecture, Security, Operations and Management. Without that collaboration and support none of the above
would have been possible.
How much of the organisation does this type of project affect?
Quite a lot! We delivered software developed for internal, public and business to business use and during my tenure shifted from hosted infrastructure to public cloud as well. All while addressing GDPR regulation
and the usual associated security concerns when moving to public cloud.
What was a key take-away in this project?
I know it’s a cliche but early, frequent collaboration is key. The early collaboration led to a guiding/mentoring behaviour between the teams instead of a traditional policing approach. Experienced individuals felt free to raise concerns or challenge a design or strategy, but were accepting if their challenge was not ultimately accepted.
Over such a long period, scope change is inevitable and strategic decisions once thought immutable may need revisiting as understanding improves and the unknown unknowns become more known. Collaborative behaviours allowed this to happen naturally at appropriate times without people trying to maintain their illusory fiefdoms of control.
How do you deal with challenges?
In short, have a plan and a roadmap, engage early and deliver incremental business value.Brett
I’m an engineer and I love challenges. I love learning, so researching, decomposing a problem into a workable plan or developing solutions is something I thoroughly enjoy. I’m also not afraid to seek help when needed so I’m always learning.
On the people side of things I strive to listen to all parties, be polite, honest, upfront and operate in the best interests of the client. In my 20+ years in the IT industry, 10 of which have been consulting, I’ve always found this to be the best operating policy.
In my first job as a software engineer straight out of University I had the fortune to be mentored by a senior engineer of extraordinary talent, patience and skill. For that reason alone I try to act as a mentor to Developers or DevOps people that need help. Watching them grow into competent engineers with my help is my way of thanking my friend for his assistance when I was young and green.
What is your biggest achievement?
A few years back I was brought on as DevOps Team Lead for a bank that had a huge engineering team. On my first day observing, I had one team member rage-quit a meeting in what I learned later to be frustration with
the team’s lack of progress and poor behaviour. That team member turned out to be one of my greatest allies in instigating change.
AWARD > the DevOps Industry Awards 2018 "Manager of the Year"
I went about breaking the silos and getting people to communicate. As we helped individual teams with their specific issues, they helped us fix bits we couldn’t do on our own. The results were an astronomical improvement in team interactions and rapid improvement in cycle time for development tasks. That was in addition to some very serious technical improvements to their infrastructure and pipeline processes on their internal and hybrid cloud operations.
On the day of my leaving, many months after, the CEO pulled me aside and said:
“I cannot thank you enough for the work you have done here.
You have made a significant impact that we are allClient
the better for, thank you”