Software Defining an Infrastructure Company -
A Transformative Journey
Mike Walls
Head of Portfolio & Professional Services – Revera
Disruptive change can blindside anyone, anytime
Our Story
Successful NZ cloud infrastructure company
• 2005 a service provider out of a storage engineering company
• 2011 an up-start beat the big boys for the AoG panel
• 2016 transact with resellers, start-ups, SMBs, banks, utilities etc.
Exponential growth
• 45%+ yoy growth
• $18M > $100M+ in ~5 years
But; there were challenges in fast paced growth!
Reduced innovation and increased chance of blind spots.
So we needed to re-focus - with two goals:
1. Get focus back on R&D and CSI – to continually innovate and transform
2. Pivot from Infrastructure to Cloud services provider and digitise transactions (CX)
.
Refocus to Continuously Add Value
Created a small dedicated team focused on strategy, ideation, MVP
• Removed from everyday business
• Focus on quick GTM to validate
Focus on Customer – Problem – Value – Solution
• Utilised Lean principles
- define the value proposition – lean canvas
- focus on business result and then define technology
- define & build technology by quick experimentation (MVP)
- measure success
- learn (stop or iterate)
The Need to Transform
Pivot from Infrastructure to a Cloud services provider and digitise transactions (CX)
• software define our infrastructure & future – orchestrate & automate
• go digital - feature rich user interface to our services
= More efficient operations
- reduce resource burden associated with manual tasks
- release resource to do more value add
= Better user experience
- end user self consume, provision, change on demand
- value-add data from dashboards and reports
But; we were an infrastructure company with an engineering mind set
The Journey So Far
• We developed a vision and strategy for where we wanted to go
- CEO on-board – a requirement to software define
• Developed CloudCreator as interface to all services
- continuously iterate
- client feedback & requirements
- new products & services
- used specialists when required – UX review
• Working on the next disruptor
• Created a new team – focused on software development
- name and org structure as a focal point
- used Agile as framework to build team around
- team of multi-skilled co-located people
- assigned one of us as Product Owner
- organisational Agile training
- picked some quick wins to iterate quickly with
Challenges
• Success = enormous backlog
• Product Owner loss = loss of vision
• Siloed SMEs = reduced velocity
• CICD not considered from start = reduced velocity
• Bi-modal MVPs often require integration back into business
Good Learnings
Technology is a key enabler; but
People and Culture are at the heart of DX
Agile and Lean are great tools for DX
• empower people (collaborative, self-managing, multi-skilled teams)
• focus on customer experience (canvas, prototype, UX)
• help focus on what’s important (canvas, standups, sprints)
Agile
• is not just about two week sprints – mind-set is key
• needs to plug into your organisational DNA to truly work
• requires Leadership buy-in
• Product Owners are crucial
• requires good people
DX is continuous improvement
• CSI needs to be enabled
• start small and iterate
Disruption can blindside the best of us
• learn from disruption to change
• comes from outside traditional parameters
• focus on ones self and those that matter
People respond to change if its impactful
• create a culture and focus
• story tell
An agile iterative process delivers
• small multi-skilled teams
• response was broken into smaller achievable
and impactful chunks
Images are powerful
Thanks for listening
Any Questions?
Presenter Timeline
Presentation due
Save presentation in AgileNZ Conference 2015 Drop Box
folder we provided you with to for submissions, email
Vicky.price@agilenz.co.nz to confirm it is in folder (if you
have lost the link we can resupply it)
Friday 18 November 2016
Presentation feedback
We will come back to you with any concerns
Wednesday 23 November 2016
Speaker briefing
30min before start all speakers to attend briefing where they
will meet stage managers, be walked through audio visual
and intro/exit procedures
8:30am Tuesday 29 November
2016 (Rangitoto 1 & 2, Level 1,
ANZ Viaduct Events Centre)
Headline font/size: Sancoale Slab Norm Medium: 44pt-60pt
Main body copy in Helvetica Neue Light 28pt-40pt
Helvetica Neue light is a good clear presentation font.
If you choose a different font, please use a common sans serif like
Helvetica or Arial. Please consider legibility!
Master slide (16:9 format)
Please turn guides ON (go to VIEW, check Guides).

Mike Walls (Revera)

  • 1.
    Software Defining anInfrastructure Company - A Transformative Journey Mike Walls Head of Portfolio & Professional Services – Revera
  • 2.
    Disruptive change canblindside anyone, anytime
  • 3.
    Our Story Successful NZcloud infrastructure company • 2005 a service provider out of a storage engineering company • 2011 an up-start beat the big boys for the AoG panel • 2016 transact with resellers, start-ups, SMBs, banks, utilities etc. Exponential growth • 45%+ yoy growth • $18M > $100M+ in ~5 years But; there were challenges in fast paced growth! Reduced innovation and increased chance of blind spots. So we needed to re-focus - with two goals: 1. Get focus back on R&D and CSI – to continually innovate and transform 2. Pivot from Infrastructure to Cloud services provider and digitise transactions (CX) .
  • 4.
    Refocus to ContinuouslyAdd Value Created a small dedicated team focused on strategy, ideation, MVP • Removed from everyday business • Focus on quick GTM to validate Focus on Customer – Problem – Value – Solution • Utilised Lean principles - define the value proposition – lean canvas - focus on business result and then define technology - define & build technology by quick experimentation (MVP) - measure success - learn (stop or iterate)
  • 5.
    The Need toTransform Pivot from Infrastructure to a Cloud services provider and digitise transactions (CX) • software define our infrastructure & future – orchestrate & automate • go digital - feature rich user interface to our services = More efficient operations - reduce resource burden associated with manual tasks - release resource to do more value add = Better user experience - end user self consume, provision, change on demand - value-add data from dashboards and reports But; we were an infrastructure company with an engineering mind set
  • 6.
    The Journey SoFar • We developed a vision and strategy for where we wanted to go - CEO on-board – a requirement to software define • Developed CloudCreator as interface to all services - continuously iterate - client feedback & requirements - new products & services - used specialists when required – UX review • Working on the next disruptor • Created a new team – focused on software development - name and org structure as a focal point - used Agile as framework to build team around - team of multi-skilled co-located people - assigned one of us as Product Owner - organisational Agile training - picked some quick wins to iterate quickly with
  • 7.
    Challenges • Success =enormous backlog • Product Owner loss = loss of vision • Siloed SMEs = reduced velocity • CICD not considered from start = reduced velocity • Bi-modal MVPs often require integration back into business
  • 8.
    Good Learnings Technology isa key enabler; but People and Culture are at the heart of DX Agile and Lean are great tools for DX • empower people (collaborative, self-managing, multi-skilled teams) • focus on customer experience (canvas, prototype, UX) • help focus on what’s important (canvas, standups, sprints) Agile • is not just about two week sprints – mind-set is key • needs to plug into your organisational DNA to truly work • requires Leadership buy-in • Product Owners are crucial • requires good people DX is continuous improvement • CSI needs to be enabled • start small and iterate
  • 9.
    Disruption can blindsidethe best of us • learn from disruption to change • comes from outside traditional parameters • focus on ones self and those that matter People respond to change if its impactful • create a culture and focus • story tell An agile iterative process delivers • small multi-skilled teams • response was broken into smaller achievable and impactful chunks Images are powerful
  • 10.
  • 12.
    Presenter Timeline Presentation due Savepresentation in AgileNZ Conference 2015 Drop Box folder we provided you with to for submissions, email Vicky.price@agilenz.co.nz to confirm it is in folder (if you have lost the link we can resupply it) Friday 18 November 2016 Presentation feedback We will come back to you with any concerns Wednesday 23 November 2016 Speaker briefing 30min before start all speakers to attend briefing where they will meet stage managers, be walked through audio visual and intro/exit procedures 8:30am Tuesday 29 November 2016 (Rangitoto 1 & 2, Level 1, ANZ Viaduct Events Centre)
  • 13.
    Headline font/size: SancoaleSlab Norm Medium: 44pt-60pt Main body copy in Helvetica Neue Light 28pt-40pt Helvetica Neue light is a good clear presentation font. If you choose a different font, please use a common sans serif like Helvetica or Arial. Please consider legibility!
  • 14.
    Master slide (16:9format) Please turn guides ON (go to VIEW, check Guides).

Editor's Notes

  • #3 Talking Digital disruption and transformation - Kodak, Uber, Air Stark reminder recently of power of disruption great illustration of the instantaneous impact of disruptive change and how it can blindside anyone, anytime It also provides some lessons reinforcing the value of agile - we’ll discuss later
  • #4 Focus on transacting reduced innovation Bell curve - Commodity phase approaching – high growth but lowering margins Fast pace of consumerisation - CX interactions maturing - Digitisation of transactions required Hyper-scale competition landing near shore we needed to transform to avoid becoming irrelevant to our customers
  • #5 Challenge #1 Bi-modial Often not branded to validate in market without brand risk Powered by revera brand
  • #6 Embrace our future competition (Azure, AWS) into portfolio – created value over top Digitise our NZ cloud platforms for now – and disrupt into future Software is required to be a digital disruptor
  • #7 Vision: Trusted Custodian of NZ cloud Services – service provider – split focus Re-branded New team – motivate the 2x people and add new Cloud automation team Culture & mindset Vision and roadmap – priorities (org wide)
  • #8 Additional resource investment – break into manageable teams Using a PM as the focal point loose the ability to self-manage, innovate Take more teams and org on journey Consider DevOps – in particular CICD from start – integration and automated testing Resourcing, support and channel models, funding
  • #9 Products, Services, Experience small disruptions/innovations can be enough to keep customers sticky – but always remember customer experience rules – involve your customers/stakeholders(cloud/mobile/software/data) People (you and your customer)
  • #10 Immediate aftermath Get the elderly and sick out first, then move the to next water in first - then the toilets, then the beer and pizza access route, - one at a time then move to the next Earthquake is a powerful example of disruption and also provides learnings in change and how agile can help