The movement to Enterprise Cloud is happening ten times faster and will be ten times bigger than client-server computing, thanks to this computing epoch is software defined and executive management driven. As workloads and infrastructure are now software, how do you integrate lifecycle management and operations at scale? In this roundtable discussion, ONUG board members offer their best thinking and practices, but don’t just sit there and listen; this is an interactive session, so come ready to participate and offer up your experience, observations and questions.
Mick Currey is an Enterprise Cloud Architect championing resilient “anti-fragile” applications, cloud topologies, observability, automated governance, and automated security controls. When he learned the cloud was becoming an option for use at Fidelity, he worked with his CTO to create a new role to start working on the cloud. He has been working as an Enterprise Cloud Architect since then.
Mick’s career started as an Industrial Engineer doing computer simulations and programming robots. Programming robots was fun. However, he felt he was too technical, so he wanted to blend technical knowledge with more business and management concepts. He went back to school for an MBA in Information System. After grad school, his initial roles were in software development, AI development, and R&D architecture. Leading projects from a technical perspective led to project management and then development management. A few management roles mixed several different categories: ALM, Infrastructure (Servers, Storage and Network), Architecture, Governance, and Regulatory Compliance. Later roles included a product line manager with team members on several continents enabling development progress round the clock.
His experiences leading two drastically different hyper performing teams shaped his thinking regarding opportunities for teams to excel. (One team was a performance testing team with detailed root cause results for each two-week cycle. The second was an agile development team doing weekly iterations, 4-6 week releases to production while enjoying a less than 0.001% production bug rate per release.)
He works with several consortiums to understand, share cloud technical information and document the best practices available in the cloud.