Journey to Zero-Touch Experience for Developers
•Download as PPTX, PDF•
0 likes•251 views
SpringOne Platform 2019 Title: Day 2 Keynote: Niall Sheehan Youtube: https://www.youtube.com/watch?v=Y5kyTQx1oaI&feature=youtu.be
Recommended
Recommended
More Related Content
Similar to Journey to Zero-Touch Experience for Developers
Similar to Journey to Zero-Touch Experience for Developers (20)
More from VMware Tanzu
More from VMware Tanzu (20)
Recently uploaded
Recently uploaded (20)
Journey to Zero-Touch Experience for Developers
- 1. JOURNEY TO ZERO-TOUCH EXPERIENCE FOR DEV “I believe the auto industry will change more in the next 5 to 10 years than it has in the last 50.” Mary Barra CEO & Chairman of General Motors
- 2. IT’S ABOUT SPEED TO MARKET INNOVATION IS OUR NORTH STAR
- 3. OUR LANDSCAPE IN 2012 OUTSOURCED & COMPLEX
- 4. WINNING TODAY & TOMORROW TO DRIVE PRODUCTIVITY, AGILITY & TIME-TO-VALUE • On-Demand Infrastructure & Tools • Shift-Left in the SDLC • Product Mindset • Balanced Teams • CI/CD Pipeline
- 5. WINNING TODAY & TOMORROW TO DRIVE PRODUCTIVITY, AGILITY & TIME-TO-VALUE • On-Demand Infrastructure & Tools • Shift-Left in the SDLC • Product Mindset • Balanced Teams • CI/CD Pipeline
- 6. WINNING TODAY & TOMORROW TO DRIVE PRODUCTIVITY, AGILITY & TIME-TO-VALUE • On-Demand Infrastructure & Tools • Shift-Left in the SDLC • Product Mindset • Balanced Teams • CI/CD Pipeline
- 7. WINNING TODAY & TOMORROW TO DRIVE PRODUCTIVITY, AGILITY & TIME-TO-VALUE • On-Demand Infrastructure & Tools • Shift-Left in the SDLC • Product Mindset • Balanced Teams • CI/CD Pipeline
- 8. WINNING TODAY & TOMORROW TO DRIVE PRODUCTIVITY, AGILITY & TIME-TO-VALUE • On-Demand Infrastructure & Tools • Shift-Left in the SDLC • Product Mindset • Balanced Teams • CI/CD Pipeline
- 9. GM FIRST MILE TRACTION FOCUSED ON STRATEGIC BUSINESS & TECHNOLOGY OPPORTUNITIES Kick Off Visio n MV P Optimizatio n PROBLEM / MARKET FIT SCALE TRACTION & MARKET VALIDATION Short Iteration s Top Problems Top SolutionsInceptio n CUSTOMER & USER FOCUSED Short Iteration s PROBLEM/SOLUTION FIT Short Iteration s
- 10. GM FIRST MILE TRACTION FOCUSED ON STRATEGIC BUSINESS & TECHNOLOGY OPPORTUNITIES Kick Off Visio n MV P Optimizatio n PROBLEM / MARKET FIT SCALE TRACTION & MARKET VALIDATION Short Iteration s Top Problems Top SolutionsInceptio n CUSTOMER & USER FOCUSED Short Iteration s PROBLEM/SOLUTION FIT Short Iteration s
- 11. REFLECTING ON OUR JOURNEY TO AN OUTSTANDING ZERO-TOUCH EXPERIENCE FOR DEVELOPERS • Technology is Important, but Only as a Means to an End
- 12. REFLECTING ON OUR JOURNEY TO AN OUTSTANDING ZERO-TOUCH EXPERIENCE FOR DEVELOPERS • Technology is Important, but Only as a Means to an End • A Cultural & Mindset Shift
- 13. REFLECTING ON OUR JOURNEY TO AN OUTSTANDING ZERO-TOUCH EXPERIENCE FOR DEVELOPERS • Technology is Important, but Only as a Means to an End • A Cultural & Mindset Shift • Frictionless End-to-End Automation
- 14. REFLECTING ON OUR JOURNEY TO AN OUTSTANDING ZERO-TOUCH EXPERIENCE FOR DEVELOPERS • Technology is Important, but Only as a Means to an End • A Cultural & Mindset Shift • Frictionless End-to-End Automation • It’s a Journey, Not a Destination
- 15. OUR VISION We see a world with CRASHES EMISSIONS CONGESTI ON ZERO ZERO ZERO and our people are the driving force behind making this a reality.
Editor's Notes
- Presenter Notes: Self Introduction & Current Role We at GM, are in the midst of a complete transformation in the way value is created, delivered, and consumed. This quote is quite fitting: GM has been pushing the limits of TRANSPORTATION & TECHNOLOGY for over 100 years & today, we are in the midst of a transportation revolution… solving the complex transportation challenges of today and tomorrow We at GM, Know that software has a key role to play, software is the differentiator With that, lets get started…(next slide)
- Presenter Notes: Today, You’ll learn how to maximize value with your software development teams by shortening the timeline from Ideation to Deployment and innovate faster. In today’s business environment speed matters. As software developers, Our ability to rapidly and effectively envision, develop, and deliver technology is crucial to enhancing the E2E customer experience How, as software developers do we go faster? How do we innovate? Our response to that is Create the conditions for success that allows dev teams to be self sufficient and eliminate/reduce the toil they experience Team first approach Eliminate/reduce waste across the SDLC Quality first mindset Leveraging microservices architecture and cloud capabilities (next slide)
- Presenter Notes: In 2012, When most of the fortune 500 companies outsourced, GM bucked the trend and brought all of IT in-house From: Complex, Convoluted, cost prohibited, highly-manual, multi-vendors…. To: Centralized fit-for-purpose Cloud Solutions We striped away the “friction & noise” and laid the pavement enabling software teams to deliver value by; Shortening the timeline Innovating faster With that…. (next slide)
- Presenter Notes: I’ll walk you through the elements of change that we at GM have went through and are still maturing… (Small stories for each slide bullet, covering: Purpose, Benefits, Lessons Learned, Where is GM Now (Where are we going? Whats our Goal?)) On-Demand Infrastructure & Tools: Self-Service consumption, environment as a service in minutes – in comparison to weeks/months Purpose: To empower teams and provide a frictionless experience Benefits: Zero-Handoffs, minimizing wait time & build compliance “up-front” You can provide standard services anytime, anywhere with ease of use For Example: Banking = Simplicity Lessons Learned: You need to have a “ShowBack” and a robust “Decommissioning” process in the back-end Where is GM now: We’re broadening the service offerings & moving up the value chain in terms of modernizing our applications and migrating to PaaS Shift-left in the SDLC: Purpose: Transition the focus to the forefront of the SDLC, in terms of design and engineering of solutions, rather than inspecting-in afterwards OPTIONAL: Look at the “Value Stream” – Challenging the status quo; i.e. change control & patch management Benefits: Foster greater collaboration between both the software development and infrastructure teams Lessons Learned: It’s a paradigm shift We’re creating a “one-team” mindset by eliminating and reducing the “rework” further downstream Where is GM now: These practices are gaining a foot-hold in GM – allowed us to shorten the delivery timeframe & innovate faster As we scale and mature, we are observing additional opportunities, for example: building-in “Security & Compliance” up-front Product Mindset: Purpose: Shifting from a “Project” to a “Product” mindset to focus on: “Lean Product Management User-Centered App Design” Benefits: Placing the Consumer at the Epi-Center of these activities, improving the consumer experience with a minimal viable product Becoming “Consumer Centric” means: We have greater involvement and engagement with the consumers upfront We’re capturing the personas & use cases from a product perspective vs. a deliverable Resulting in: Improving the overall consumption, user experience, and quality of the product Lessons Learned: Its not a natural exercise It’s a challenging mind-shift requiring Product Owners with unique set of skills, communication, & robust framework to scale and implement Where is GM now: We have pockets of excellence where certain software development teams have embraced this shift We’ve aligned on a common framework, developed playbooks, and are now educating our staff Balanced Teams: An autonomous group of people with a variety of skills and perspectives that support each other towards a shared goal Purpose: To ensure that we have different perspectives: Primarily from the Product Owner, UX & Development Teams Benefits: To reach the User-Centered App Design in mind – from ideation to deployment OPTIONAL: “Supply Chain Management” helps reduce the end-to-end lead time from ideation to deployment and optimizes the development cycle time Lessons Learned: Identified opportunities to align organizations around Balanced Teams Need to adopt “Design Thinking” concepts across the organizations to allow us to see the “bigger picture” OPTIONAL: And enable “Test Driven Development” to help build quality at source Where is GM Now: Many software development teams have proactively embraced this approach CI/CD Pipeline: Automate, Automate & Automate Purpose: Deliver software to a production environment with speed, frequency, safely, and reliability Benefits: Continuously delivering value to the business Lessons Learned: Review your end-to-end design, and simplify your tool-chain Treat your platform as a product Modernize Architecture Design Patterns, Re-engineer your applications & integrate CI/CD within your pipeline OPTIONAL: With “Open Source Software”, you’re unlocking the creative potential from your developers – Modernizing applications & platforms Where is GM Now: We’ve reduced the “Toil” on the Developer: inclusive of day-0 and day-2 activities We’re establishing “Consistent Environments” from Development all the way through Production (next slide)
- Presenter Notes: I’ll walk you through the elements of change that we at GM have went through and are still maturing… (Small stories for each slide bullet, covering: Purpose, Benefits, Lessons Learned, Where is GM Now (Where are we going? Whats our Goal?)) On-Demand Infrastructure & Tools: Self-Service consumption, environment as a service in minutes – in comparison to weeks/months Purpose: To empower teams and provide a frictionless experience Benefits: Zero-Handoffs, minimizing wait time & build compliance “up-front” You can provide standard services anytime, anywhere with ease of use For Example: Banking = Simplicity Lessons Learned: You need to have a “ShowBack” and a robust “Decommissioning” process in the back-end Where is GM now: We’re broadening the service offerings & moving up the value chain in terms of modernizing our applications and migrating to PaaS Shift-left in the SDLC: Purpose: Transition the focus to the forefront of the SDLC, in terms of design and engineering of solutions, rather than inspecting-in afterwards OPTIONAL: Look at the “Value Stream” – Challenging the status quo; i.e. change control & patch management Benefits: Foster greater collaboration between both the software development and infrastructure teams Lessons Learned: It’s a paradigm shift We’re creating a “one-team” mindset by eliminating and reducing the “rework” further downstream Where is GM now: These practices are gaining a foot-hold in GM – allowed us to shorten the delivery timeframe & innovate faster As we scale and mature, we are observing additional opportunities, for example: building-in “Security & Compliance” up-front Product Mindset: Purpose: Shifting from a “Project” to a “Product” mindset to focus on: “Lean Product Management User-Centered App Design” Benefits: Placing the Consumer at the Epi-Center of these activities, improving the consumer experience with a minimal viable product Becoming “Consumer Centric” means: We have greater involvement and engagement with the consumers upfront We’re capturing the personas & use cases from a product perspective vs. a deliverable Resulting in: Improving the overall consumption, user experience, and quality of the product Lessons Learned: Its not a natural exercise It’s a challenging mind-shift requiring Product Owners with unique set of skills, communication, & robust framework to scale and implement Where is GM now: We have pockets of excellence where certain software development teams have embraced this shift We’ve aligned on a common framework, developed playbooks, and are now educating our staff Balanced Teams: An autonomous group of people with a variety of skills and perspectives that support each other towards a shared goal Purpose: To ensure that we have different perspectives: Primarily from the Product Owner, UX & Development Teams Benefits: To reach the User-Centered App Design in mind – from ideation to deployment OPTIONAL: “Supply Chain Management” helps reduce the end-to-end lead time from ideation to deployment and optimizes the development cycle time Lessons Learned: Identified opportunities to align organizations around Balanced Teams Need to adopt “Design Thinking” concepts across the organizations to allow us to see the “bigger picture” OPTIONAL: And enable “Test Driven Development” to help build quality at source Where is GM Now: Many software development teams have proactively embraced this approach CI/CD Pipeline: Automate, Automate & Automate Purpose: Deliver software to a production environment with speed, frequency, safely, and reliability Benefits: Continuously delivering value to the business Lessons Learned: Review your end-to-end design, and simplify your tool-chain Treat your platform as a product Modernize Architecture Design Patterns, Re-engineer your applications & integrate CI/CD within your pipeline OPTIONAL: With “Open Source Software”, you’re unlocking the creative potential from your developers – Modernizing applications & platforms Where is GM Now: We’ve reduced the “Toil” on the Developer: inclusive of day-0 and day-2 activities We’re establishing “Consistent Environments” from Development all the way through Production (next slide)
- Presenter Notes: I’ll walk you through the elements of change that we at GM have went through and are still maturing… (Small stories for each slide bullet, covering: Purpose, Benefits, Lessons Learned, Where is GM Now (Where are we going? Whats our Goal?)) On-Demand Infrastructure & Tools: Self-Service consumption, environment as a service in minutes – in comparison to weeks/months Purpose: To empower teams and provide a frictionless experience Benefits: Zero-Handoffs, minimizing wait time & build compliance “up-front” You can provide standard services anytime, anywhere with ease of use For Example: Banking = Simplicity Lessons Learned: You need to have a “ShowBack” and a robust “Decommissioning” process in the back-end Where is GM now: We’re broadening the service offerings & moving up the value chain in terms of modernizing our applications and migrating to PaaS Shift-left in the SDLC: Purpose: Transition the focus to the forefront of the SDLC, in terms of design and engineering of solutions, rather than inspecting-in afterwards OPTIONAL: Look at the “Value Stream” – Challenging the status quo; i.e. change control & patch management Benefits: Foster greater collaboration between both the software development and infrastructure teams Lessons Learned: It’s a paradigm shift We’re creating a “one-team” mindset by eliminating and reducing the “rework” further downstream Where is GM now: These practices are gaining a foot-hold in GM – allowed us to shorten the delivery timeframe & innovate faster As we scale and mature, we are observing additional opportunities, for example: building-in “Security & Compliance” up-front Product Mindset: Purpose: Shifting from a “Project” to a “Product” mindset to focus on: “Lean Product Management User-Centered App Design” Benefits: Placing the Consumer at the Epi-Center of these activities, improving the consumer experience with a minimal viable product Becoming “Consumer Centric” means: We have greater involvement and engagement with the consumers upfront We’re capturing the personas & use cases from a product perspective vs. a deliverable Resulting in: Improving the overall consumption, user experience, and quality of the product Lessons Learned: Its not a natural exercise It’s a challenging mind-shift requiring Product Owners with unique set of skills, communication, & robust framework to scale and implement Where is GM now: We have pockets of excellence where certain software development teams have embraced this shift We’ve aligned on a common framework, developed playbooks, and are now educating our staff Balanced Teams: An autonomous group of people with a variety of skills and perspectives that support each other towards a shared goal Purpose: To ensure that we have different perspectives: Primarily from the Product Owner, UX & Development Teams Benefits: To reach the User-Centered App Design in mind – from ideation to deployment OPTIONAL: “Supply Chain Management” helps reduce the end-to-end lead time from ideation to deployment and optimizes the development cycle time Lessons Learned: Identified opportunities to align organizations around Balanced Teams Need to adopt “Design Thinking” concepts across the organizations to allow us to see the “bigger picture” OPTIONAL: And enable “Test Driven Development” to help build quality at source Where is GM Now: Many software development teams have proactively embraced this approach CI/CD Pipeline: Automate, Automate & Automate Purpose: Deliver software to a production environment with speed, frequency, safely, and reliability Benefits: Continuously delivering value to the business Lessons Learned: Review your end-to-end design, and simplify your tool-chain Treat your platform as a product Modernize Architecture Design Patterns, Re-engineer your applications & integrate CI/CD within your pipeline OPTIONAL: With “Open Source Software”, you’re unlocking the creative potential from your developers – Modernizing applications & platforms Where is GM Now: We’ve reduced the “Toil” on the Developer: inclusive of day-0 and day-2 activities We’re establishing “Consistent Environments” from Development all the way through Production (next slide)
- Presenter Notes: I’ll walk you through the elements of change that we at GM have went through and are still maturing… (Small stories for each slide bullet, covering: Purpose, Benefits, Lessons Learned, Where is GM Now (Where are we going? Whats our Goal?)) On-Demand Infrastructure & Tools: Self-Service consumption, environment as a service in minutes – in comparison to weeks/months Purpose: To empower teams and provide a frictionless experience Benefits: Zero-Handoffs, minimizing wait time & build compliance “up-front” You can provide standard services anytime, anywhere with ease of use For Example: Banking = Simplicity Lessons Learned: You need to have a “ShowBack” and a robust “Decommissioning” process in the back-end Where is GM now: We’re broadening the service offerings & moving up the value chain in terms of modernizing our applications and migrating to PaaS Shift-left in the SDLC: Purpose: Transition the focus to the forefront of the SDLC, in terms of design and engineering of solutions, rather than inspecting-in afterwards OPTIONAL: Look at the “Value Stream” – Challenging the status quo; i.e. change control & patch management Benefits: Foster greater collaboration between both the software development and infrastructure teams Lessons Learned: It’s a paradigm shift We’re creating a “one-team” mindset by eliminating and reducing the “rework” further downstream Where is GM now: These practices are gaining a foot-hold in GM – allowed us to shorten the delivery timeframe & innovate faster As we scale and mature, we are observing additional opportunities, for example: building-in “Security & Compliance” up-front Product Mindset: Purpose: Shifting from a “Project” to a “Product” mindset to focus on: “Lean Product Management User-Centered App Design” Benefits: Placing the Consumer at the Epi-Center of these activities, improving the consumer experience with a minimal viable product Becoming “Consumer Centric” means: We have greater involvement and engagement with the consumers upfront We’re capturing the personas & use cases from a product perspective vs. a deliverable Resulting in: Improving the overall consumption, user experience, and quality of the product Lessons Learned: Its not a natural exercise It’s a challenging mind-shift requiring Product Owners with unique set of skills, communication, & robust framework to scale and implement Where is GM now: We have pockets of excellence where certain software development teams have embraced this shift We’ve aligned on a common framework, developed playbooks, and are now educating our staff Balanced Teams: An autonomous group of people with a variety of skills and perspectives that support each other towards a shared goal Purpose: To ensure that we have different perspectives: Primarily from the Product Owner, UX & Development Teams Benefits: To reach the User-Centered App Design in mind – from ideation to deployment OPTIONAL: “Supply Chain Management” helps reduce the end-to-end lead time from ideation to deployment and optimizes the development cycle time Lessons Learned: Identified opportunities to align organizations around Balanced Teams Need to adopt “Design Thinking” concepts across the organizations to allow us to see the “bigger picture” OPTIONAL: And enable “Test Driven Development” to help build quality at source Where is GM Now: Many software development teams have proactively embraced this approach CI/CD Pipeline: Automate, Automate & Automate Purpose: Deliver software to a production environment with speed, frequency, safely, and reliability Benefits: Continuously delivering value to the business Lessons Learned: Review your end-to-end design, and simplify your tool-chain Treat your platform as a product Modernize Architecture Design Patterns, Re-engineer your applications & integrate CI/CD within your pipeline OPTIONAL: With “Open Source Software”, you’re unlocking the creative potential from your developers – Modernizing applications & platforms Where is GM Now: We’ve reduced the “Toil” on the Developer: inclusive of day-0 and day-2 activities We’re establishing “Consistent Environments” from Development all the way through Production (next slide)
- Presenter Notes: I’ll walk you through the elements of change that we at GM have went through and are still maturing… (Small stories for each slide bullet, covering: Purpose, Benefits, Lessons Learned, Where is GM Now (Where are we going? Whats our Goal?)) On-Demand Infrastructure & Tools: Self-Service consumption, environment as a service in minutes – in comparison to weeks/months Purpose: To empower teams and provide a frictionless experience Benefits: Zero-Handoffs, minimizing wait time & build compliance “up-front” You can provide standard services anytime, anywhere with ease of use For Example: Banking = Simplicity Lessons Learned: You need to have a “ShowBack” and a robust “Decommissioning” process in the back-end Where is GM now: We’re broadening the service offerings & moving up the value chain in terms of modernizing our applications and migrating to PaaS Shift-left in the SDLC: Purpose: Transition the focus to the forefront of the SDLC, in terms of design and engineering of solutions, rather than inspecting-in afterwards OPTIONAL: Look at the “Value Stream” – Challenging the status quo; i.e. change control & patch management Benefits: Foster greater collaboration between both the software development and infrastructure teams Lessons Learned: It’s a paradigm shift We’re creating a “one-team” mindset by eliminating and reducing the “rework” further downstream Where is GM now: These practices are gaining a foot-hold in GM – allowed us to shorten the delivery timeframe & innovate faster As we scale and mature, we are observing additional opportunities, for example: building-in “Security & Compliance” up-front Product Mindset: Purpose: Shifting from a “Project” to a “Product” mindset to focus on: “Lean Product Management User-Centered App Design” Benefits: Placing the Consumer at the Epi-Center of these activities, improving the consumer experience with a minimal viable product Becoming “Consumer Centric” means: We have greater involvement and engagement with the consumers upfront We’re capturing the personas & use cases from a product perspective vs. a deliverable Resulting in: Improving the overall consumption, user experience, and quality of the product Lessons Learned: Its not a natural exercise It’s a challenging mind-shift requiring Product Owners with unique set of skills, communication, & robust framework to scale and implement Where is GM now: We have pockets of excellence where certain software development teams have embraced this shift We’ve aligned on a common framework, developed playbooks, and are now educating our staff Balanced Teams: An autonomous group of people with a variety of skills and perspectives that support each other towards a shared goal Purpose: To ensure that we have different perspectives: Primarily from the Product Owner, UX & Development Teams Benefits: To reach the User-Centered App Design in mind – from ideation to deployment OPTIONAL: “Supply Chain Management” helps reduce the end-to-end lead time from ideation to deployment and optimizes the development cycle time Lessons Learned: Identified opportunities to align organizations around Balanced Teams Need to adopt “Design Thinking” concepts across the organizations to allow us to see the “bigger picture” OPTIONAL: And enable “Test Driven Development” to help build quality at source Where is GM Now: Many software development teams have proactively embraced this approach CI/CD Pipeline: Automate, Automate & Automate Purpose: Deliver software to a production environment with speed, frequency, safely, and reliability Benefits: Continuously delivering value to the business Lessons Learned: Review your end-to-end design, and simplify your tool-chain Treat your platform as a product Modernize Architecture Design Patterns, Re-engineer your applications & integrate CI/CD within your pipeline OPTIONAL: With “Open Source Software”, you’re unlocking the creative potential from your developers – Modernizing applications & platforms Where is GM Now: We’ve reduced the “Toil” on the Developer: inclusive of day-0 and day-2 activities We’re establishing “Consistent Environments” from Development all the way through Production (next slide)
- Presenter Notes: And our 2nd case study: First Mile The FirstMile organization was formed to help our new business ventures take a leap. They are a lean startup with the capabilities to scale out & were the organization to spearhead the introduction of PaaS within GM. With PCF, they’ve been able to support the GM business and technology opportunities to develop products and markets like: Maven, Maven GIG, Book By Cadillac, & now recently the ERIV eBIKE. FirstMile operates as a high efficient team and leverages all of the tools and processes as highlighted in the slide before with: On-Demand Infrastructure & Tools Shift-Left in the SDLC Product Mindset Balanced Teams CI/CD Pipeline First Mile aides in refining business models, achieving product/market fit, and scaling startups into high growth, revenue generating businesses. (next slide) ADDITIONAL NOTES: This organization was recently formed to help our new business ventures take a leap - focus strategic GM business and technology opportunities to develop products, teams, and markets: Aide in refining business models, achieving product/market fit, and scaling startups into high growth, revenue generating businesses. Products like: Maven, Maven GIG, Book By Cadillac, & ERIV eBIKE First mile operates as a high efficient team by leveraging all of the tools and process as highlighted earlier: Primarily: Self-service consumption with Infrastructure and PaaS Early engagement Product focused, not projects Balanced Teams Automation, with CI/CD Pipeline
- Presenter Notes: And our 2nd case study: First Mile The FirstMile organization was formed to help our new business ventures take a leap. They are a lean startup with the capabilities to scale out & were the organization to spearhead the introduction of PaaS within GM. With PCF, they’ve been able to support the GM business and technology opportunities to develop products and markets like: Maven, Maven GIG, Book By Cadillac, & now recently the ERIV eBIKE. FirstMile operates as a high efficient team and leverages all of the tools and processes as highlighted in the slide before with: On-Demand Infrastructure & Tools Shift-Left in the SDLC Product Mindset Balanced Teams CI/CD Pipeline First Mile aides in refining business models, achieving product/market fit, and scaling startups into high growth, revenue generating businesses. (next slide) ADDITIONAL NOTES: This organization was recently formed to help our new business ventures take a leap - focus strategic GM business and technology opportunities to develop products, teams, and markets: Aide in refining business models, achieving product/market fit, and scaling startups into high growth, revenue generating businesses. Products like: Maven, Maven GIG, Book By Cadillac, & ERIV eBIKE First mile operates as a high efficient team by leveraging all of the tools and process as highlighted earlier: Primarily: Self-service consumption with Infrastructure and PaaS Early engagement Product focused, not projects Balanced Teams Automation, with CI/CD Pipeline
- Presenter Notes: OK, well we don’t know, but its not a 10. Technology is important, but its only a means to an end We need to focus on: People & Processes (next slide)
- Presenter Notes: It’s about a Cultural & Mindset shift Management is attempting to change the game (next slide)
- Presenter Notes: In Addition to this, End-to-End Automation has been a critical focus point in our Journey Self-service Infrastructure, PaaS, CI/CD, and Open Source Software empowers you (and your development team) to be fast and agile. (next slide)
- Presenter Notes: And lastly, Recognize that this is a journey, not a destination. We didn’t always get it right, however we’ve embraced this change & we’re still learning how to make it right But we need to continue our focus on Developer Centricity The outstanding zero-touch experience for developers is to enable and allow developers to be DEVELOPERS (next slide) ===================== ADDITIONAL NOTES (Optional): NOTES from 9/30: SHIFT-LEFT (QUALITY AT SOURCE), ECONOMIES OF FLOW, DESIGN INTO THE PRODUCT RATHER THAN INSPECT IT EXPERIMENTATION (MVP), CONTINUOUS FEEDBACK, & VALUE MANAGEMENT Key's to success: Need these components/conditions in the ecosystems to deliver these outcomes * Product Management: Establish a product mindset * Balanced Teams: UX, Development, BA/QA * On-Demand Infrastructure & Tools: Providing End to End Automation OUTPUT 1. QUALITY: TBD 2. COLLABORATION: Established high performance teams 3. VELOCITY: Frictionless Automated Software Development Life Cycle
- Presenter Notes: GM is on a journey, and our vision is a world with Zero Crashes, Zero Emissions, & Zero Congestion Our ability to rapidly and effectively envision, develop, and deliver technology is crucial to our business and the customer experience Closing: Again, I’m Niall Sheehan, Hope you enjoyed my presentation, Look forward to speaking to you throughout the conference. (end presentation)