Optimizely Full Stack helps product development teams experiment deep into their stack to create exceptional customer experiences on everything from search results and promos to recommendations and payment structures. In this session, Jamie Connolly, Senior Product Manager on Developer Experience will talk about the latest enhancements to Full Stack to drive compatibility, usability, and performance.
Supercharging Optimizely Performance by Moving Decisions to the EdgeOptimizely
To survive in today’s competitive market, it’s imperative that you drive high-velocity experimentation and maximize site performance. In this talk, Optimizely will be joined by performance experts, Cloudflare to share latest updates to the Optimizely platform to make client-side experimentation blazing fast.
In this session you’ll learn:
- How to take advantage of the latest performance enhancements to the Optimizely platform
- Best practices for implementing Optimizely for maximum performance including how to take advantage of your CDN
- How to have an informed conversation with your performance engineering team when it comes to Optimizely
All Change how the economics of Cloud will make you think differently about JavaSteve Poole
How far have you gotten with learning about the cloud? Got your head around platform as a service? Understand what IaaS means? Know how to spell Docker? It’s easy to focus on learning new technology, but it’s time to take a step back and look at what the technical implications are when an application is heading to the cloud. In the world of the cloud, the benefits are high but the economics (financial and technical) can be radically different. Learn about these new realities and how they can change application design, deployment, and support. Cloud technologies and their rapid adoption are creating new opportunities and challenges. Whether you’re a designer, developer, or tester, this session will help you start thinking differently about Java and the cloud.
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
Cloud-Native Builds & Deployments in Bitbucket PipelinesAtlassian
Pipelines is Bitbucket Cloud's new integrated build and release tool, and we're on a mission to give every development team a painless build and release process. Matt Ryall, Pipelines Product Manager, will talk about new features in Pipelines to enable Docker builds and database testing in your builds, and how teams are replacing their legacy build system with Pipelines to save valuable developer time. A must-see talk for teams deploying to the cloud.
HPQC ALM was the tool of choice for organizations to manage their software testing process for decades, however, it is quickly falling out of favor with today’s savvier testers. Learn more in this webinar slide deck.
From 0 to DevOps in 80 Days [Webinar Replay]Dynatrace
From 0 to DevOps in 80 Days
Link to the webinar replay: https://info.dynatrace.com/apm_dtm_ops_17q3_wc_from_enterprise_tocloud_native_na_registration.html
“Innovate or die” may sound extreme, but it’s the only way to thrive in today’s ever competitive market. Bernd Greifeneder, CTO of Dynatrace, wanted to ensure that the company was relevant 5 years from now so he formed an internal incubator with one goal: transform Dynatrace into a Cloud Native DevOps organization.
The incubator focused on what the company needed to do in order to integrate nascent cloud technologies so that they wouldn’t be left in the dust when the inevitable tipping point to cloud arrives. Transforming into a cloud native company would allow for rapid release cycles and provide an embedded feedback loop.
The Results: Dynatrace now has a 99.998% availability of SaaS Service and can deploy changes within an hour if necessary. In parallel, a new SaaS and managed offering is released every 2 weeks with 170 production updates per day.
Watch this recorded webinar as Bernd Greifeneder shares the lessons learned moving Dynatrace from an on-prem company to one that is cloud native.
Bernd discusses:
• The driving factors that led to the transformation
• The goals that were set back in 2011 towards the engineering team
• How to sell such a transformation project in a large enterprise organization
• How to support this multi-year project from top down without impacting regular operations
• What's next on the innovator's mind
Efficient Performance Test Automation - Opitmizing the Jenkins PipelineJules Pierre-Louis
Shift-left testing represents a huge opportunity within the context of DevOps and Continuous Delivery, and integrating performance tests into your Continuous Integration scope greatly reduces performance risks when adding a new feature, or fixing a bug.
Even better – adding performance tests into the widely used Jenkins Pipeline is easier than you might think. In this webinar, co-presented by CA BlazeMeter and CloudBees, we’ll offer practical tips and best practices for leveraging performance test automation in a continuous integration environment.
In this webinar we’ll cover:
- How to easily implement a project’s entire build/test/deploy pipeline in Jenkins and store that alongside existing code
- How to configure and execute realistic, large-scale performance-testing scenarios as part of the Continuous Integration process
- Enabling easy test configuration maintenance using the open source test automation tool Taurus along with Jenkins Pipeline
- Analyzing comprehensive performance test results in real-time, and integrating those results as a part of the build promotion criteria
Extend the impact of performance testing across the software delivery pipeline and the popular tools your teams are already using.
Supercharging Optimizely Performance by Moving Decisions to the EdgeOptimizely
To survive in today’s competitive market, it’s imperative that you drive high-velocity experimentation and maximize site performance. In this talk, Optimizely will be joined by performance experts, Cloudflare to share latest updates to the Optimizely platform to make client-side experimentation blazing fast.
In this session you’ll learn:
- How to take advantage of the latest performance enhancements to the Optimizely platform
- Best practices for implementing Optimizely for maximum performance including how to take advantage of your CDN
- How to have an informed conversation with your performance engineering team when it comes to Optimizely
All Change how the economics of Cloud will make you think differently about JavaSteve Poole
How far have you gotten with learning about the cloud? Got your head around platform as a service? Understand what IaaS means? Know how to spell Docker? It’s easy to focus on learning new technology, but it’s time to take a step back and look at what the technical implications are when an application is heading to the cloud. In the world of the cloud, the benefits are high but the economics (financial and technical) can be radically different. Learn about these new realities and how they can change application design, deployment, and support. Cloud technologies and their rapid adoption are creating new opportunities and challenges. Whether you’re a designer, developer, or tester, this session will help you start thinking differently about Java and the cloud.
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
Cloud-Native Builds & Deployments in Bitbucket PipelinesAtlassian
Pipelines is Bitbucket Cloud's new integrated build and release tool, and we're on a mission to give every development team a painless build and release process. Matt Ryall, Pipelines Product Manager, will talk about new features in Pipelines to enable Docker builds and database testing in your builds, and how teams are replacing their legacy build system with Pipelines to save valuable developer time. A must-see talk for teams deploying to the cloud.
HPQC ALM was the tool of choice for organizations to manage their software testing process for decades, however, it is quickly falling out of favor with today’s savvier testers. Learn more in this webinar slide deck.
From 0 to DevOps in 80 Days [Webinar Replay]Dynatrace
From 0 to DevOps in 80 Days
Link to the webinar replay: https://info.dynatrace.com/apm_dtm_ops_17q3_wc_from_enterprise_tocloud_native_na_registration.html
“Innovate or die” may sound extreme, but it’s the only way to thrive in today’s ever competitive market. Bernd Greifeneder, CTO of Dynatrace, wanted to ensure that the company was relevant 5 years from now so he formed an internal incubator with one goal: transform Dynatrace into a Cloud Native DevOps organization.
The incubator focused on what the company needed to do in order to integrate nascent cloud technologies so that they wouldn’t be left in the dust when the inevitable tipping point to cloud arrives. Transforming into a cloud native company would allow for rapid release cycles and provide an embedded feedback loop.
The Results: Dynatrace now has a 99.998% availability of SaaS Service and can deploy changes within an hour if necessary. In parallel, a new SaaS and managed offering is released every 2 weeks with 170 production updates per day.
Watch this recorded webinar as Bernd Greifeneder shares the lessons learned moving Dynatrace from an on-prem company to one that is cloud native.
Bernd discusses:
• The driving factors that led to the transformation
• The goals that were set back in 2011 towards the engineering team
• How to sell such a transformation project in a large enterprise organization
• How to support this multi-year project from top down without impacting regular operations
• What's next on the innovator's mind
Efficient Performance Test Automation - Opitmizing the Jenkins PipelineJules Pierre-Louis
Shift-left testing represents a huge opportunity within the context of DevOps and Continuous Delivery, and integrating performance tests into your Continuous Integration scope greatly reduces performance risks when adding a new feature, or fixing a bug.
Even better – adding performance tests into the widely used Jenkins Pipeline is easier than you might think. In this webinar, co-presented by CA BlazeMeter and CloudBees, we’ll offer practical tips and best practices for leveraging performance test automation in a continuous integration environment.
In this webinar we’ll cover:
- How to easily implement a project’s entire build/test/deploy pipeline in Jenkins and store that alongside existing code
- How to configure and execute realistic, large-scale performance-testing scenarios as part of the Continuous Integration process
- Enabling easy test configuration maintenance using the open source test automation tool Taurus along with Jenkins Pipeline
- Analyzing comprehensive performance test results in real-time, and integrating those results as a part of the build promotion criteria
Extend the impact of performance testing across the software delivery pipeline and the popular tools your teams are already using.
Five Ways Automation Has Increased Application Deployment and Changed CultureXebiaLabs
Paychex, a recognized leader in the payroll, human resource, and benefits outsourcing industry, found that the demand for application deployments had increased beyond what could be supported by manual configuration. Keeping up with this demand required a shift from manually providing a service to developing an automated platform for self-service resulting in a culture change with new partnering across their DEV, OPS and Architecture teams.
David Jozis, Automation Engineer at Paychex, discusses the challenges they encountered when making these significant changes and how they were able to overcome them to accomplish 5x as many deployments as before.
JavaOne 2015 Devops and the Darkside CON6447Steve Poole
So you get DevOps. You like the idea and think it’s important. The trouble is that others in your team don’t. This session will help you understand how to convince your team of the benefits of DevOps. Packed with facts and figures, the presentation works through the common challenges Java teams face when moving to a DevOps model and outlines how to address them. It also shows you how to balance evangelism against pragmatism when championing DevOps in your organization. You’ll learn how others have made the transition to DevOps and understand what mistakes to avoid when doing so. Whether you need to know how to be a DevOps evangelist or simply want to understand why DevOps is important, this session is for you.
Performance Metrics Driven CI/CD - Introduction to Continuous Innovation and ...Mike Villiger
Deck used for my talk at the 2016 Spring User Conference in Toronto. Deck was followed up by a walkthrough of a Jenkins workflow that deployed to Cloud Foundry based on jmeter test results
How HipChat Ships and Recovers Fast with DevOps PracticesAtlassian
HipChat operates a ‘You Build It, You Run It’ service model, where developers are responsible for building, testing, and operating their systems. While we have a high speed of development, things can break – but we also recover quickly. Learn about how we've integrated best practices within our planning, building, operating and learning processes to optimize for speed and efficiency but also mitigate, prepare for, and handle incidents.
The presenter will walk you through four steps for how to operate at a high speed of development and also prepare for any incident — planning, prevention, preparation and collecting feedback— and instruct you on how you can build these processes into your Atlasssian workflow (including JIRA Software, HipChat, Bitbucket, Confluence, Bamboo, and StatusPage).
Learn about:
- Planning: How we use JIRA Software and Confluence to plan roadmaps and sync up with teams
- Prevention: Best practices during code reviews and testing
- Preparation: How we prepare for incidents with war games
Review: Collecting feedback, assessing incident causes and improving our processes
Come out of this session with a newfound understanding of how to use Atlassian products within your DevOps workflow!
Mickie Betz, Software Developer, Atlassian
Making the Switch from HP Quality Center to qTestQASymphony
HP Quality Center has been the most widely adopted test management solution in the market to date, however, companies are replacing that solution with new replacement options. QASymphony’s modern qTest platform provides robust functionality that enterprise companies demand, and support for new methodologies like agile, DevOps, and open source automation that will make even the most discerning of testers happy.
To help you seamlessly adopt these top of the line features, we provide a wide array of migration options to satisfy all needs and budgets. Kevin Dunne, VP of Business Development at QASymphony, will provide an overview of his experience migrating dozens of customers from HP QC and he will share his best practices for making a smooth transition into the next generation of test management.
He will cover:
Market Trends — What new developments are shaping the way teams work?
Common Migration Challenges — What hurdles are typically faced in a migration?
Migration Methods — What options does QASymphony recommend for migration?
Migration Best Practices — How are leading companies making the switch?
Agile Incident Response and Resolution in the Wold of DevopsAtlassian
Devops has transformed how teams build and run software: you build it, you own it! In this new Devops world, the methods of responding to and resolving incidents have changed dramatically. You no longer have a 24/7 NOC handling incident response; instead, developers and ops engineers must work closely together and go on-call to triage alerts and resolve incidents.
At the same time, with more applications and services moving to the cloud, the impact of major outages has increased. Most enterprises have multiple major incidents each month and lose over $100K in revenue and lost productivity per incident.
This session describes how to effectively manage the entire incident lifecycle end-to-end, helping teams lower the duration and frequency of outages. We will cover the following topics:
- How to prepare and train your team up-front to respond to incidents quickly.
- How to handle triaging large volumes of alerts, identify the severity of issues, and loop in the right people ASAP.
- How to manage and run an incident effectively across multiple responders and stakeholders.
- How to create a learning feedback loop in your incident lifecycle by conducting a blameless post-mortem.
Overall, we will cover people, process, and tools as they relate to the incident lifecycle. In terms of tooling, we will feature a best-of-breed toolchain from Atlassian, PagerDuty, and other modern innovative companies.
Alex Solomon, CTO and Co-Founder, PagerDuty
Sprinting for Success: Digital Transformation through Agile and DevOpsDynatrace
Verizon is not a startup that can simply copy and apply what works well for Uber, Facebook and other “Unicorn-Companies.” They are challenged by complex IT and business infrastructure accumulated over decades. Yet they wanted to streamline operations, optimize business output and deliver more useful products faster to their consumers.
Verizon’s journey started back in 2011 by identifying Technical Debt, Business Debt and Organizational Rust. Now in 2016, after several years of streamlining their development and IT organization, they run every single project using a “Verizon agile,” DevOps approach.
Download this webinar to hear, Assoc. Director at Verizon Enterprise Solutions, Nita Awatramani, share Verizon’s amazing digital transformation journey. Learn how they re-invented the way they develop, deploy and run their software supporting their business to remain competitive, profitable and relevant, in an era of increasing customer expectations.
Discover how Verizon successfully:
Decreased the number of apps they support by 40%
Reduced IT complexity by consolidating from 13 to 5 data centers
Increased their virtual server footprint 66% while reducing hardware footprint 25%
Implemented a “level-up” mind set for team members through metrics-driven continuous delivery
Nita is joined by Andreas Grabner, Performance Advocate at Dynatrace who will support why monitoring, application and end user metrics have to be a key part of your own transformation!
Nita Awatramani
Associate Director at Verizon Enterprise Solutions
Nita Awatramani is responsible for infrastructure program management, security, compliance and business operations for Verizon Enterprise Solutions pre-sales and ordering systems. She has been with Verizon for 15 years, first with Consumer and Mass Business and then with Verizon Enterprise Solutions. She has a bachelor’s degree in Mathematics and a master’s in Computer Science. She holds a CISSP certification and is currently pursuing the Advanced Computer Security Program at Stanford.
Andreas Grabner
Performance Advocate at Dynatrace
Andreas Grabner has 15+ years’ experience as an architect and developer in the Java and .NET space. In his current role, Andi works as an advocate for high performing applications in both the development and operations areas. He is a regular expert and contributor to large performance communities, a frequent speaker at technology conferences and regularly publishes articles blogs on blog.dynatrace.com
Where Testers & QA Fit in the Story of DevOpsQASymphony
Where Testers and QA Fit in the Story of DevOps
Continuous delivery. CI. GitHub. Scrum. CD. Jenkins. Continuous testing. Continuous integration. These are just some terms that are supposed to describe the word soup that is DevOps. Chances are that you have heard some or all of these words being passed around at your daily stand ups or company meetings.
However, where does QA and testing fit into the story of DevOps? Some would say that developers and operations teams are all you need for a successful DevOps pipeline, while others show that Dev, Test and Ops need to be included to ensure quality at every step in your pipeline.
In this webinar, Ryan Yackel, QASymphony's Director of Product Marketing, and Sunil Sehgal, Managing Partner at TechArcis, will share their experiences as they navigate you through the DevTestOps waters. In this webinar you will learn:
Overview of the State of DevOps
Common misconceptions of DevOps and QA
How testers must adapt to the DevOps process
The tools testers need for continuous testing
Can't make the webinar? Sign up and we will send you the recording.
Quality Jam 2017: Kevin Dunne "Macro Trends and Useful Tools that 'Get It'"QASymphony
Testers can’t live without their beloved tools, and the landscape of testing and development tools is changing rapidly. While testers were previously limited to a few expensive and difficult to use tools, the market is now filling with many more affordable, powerful, and easy to use products. In this presentation, Kevin will discuss 5 of the most important macro trends in test tools: 1) Specialization 2) Cloud hosting 3) Architectural Shifts 4) Collaboration 5) Ease of Use/Deployment. Kevin will also provide examples of popular tools that are capitalizing on these trends and gaining popularity in the market.
Watch the Quality Jam presentation at www.qasymphony.com/blog/quality-jam-2017-presentations/
Machine Learning to Turbo-Charge the Ops Portion of DevOpsDeborah Schalm
Already on a continuous or short-cycle delivery? Constantly rewiring your apps with microservice and similar architectures? Maintaining visibility and maximizing service levels once this stuff gets into production could be a regular nightmare. Coding instrumentation into your apps is time-consuming and error-prone. Instead, let machine learning do the work of adapting your monitoring to your fast-moving application environments. In this webcast learn about various types of machine learning that are optimized for operational data, and see in a demo how this could be leveraged to ensure your ops move as fast as rest of your DevOps pipeline.
Quality Jam 2017: Elise Carmichael and Corey Pyle "Jumpstarting Your Test Aut...QASymphony
Elise Carmichael and Corey Pyle walk you through real-life test automation stories and use cases including: How to decide which tests to automate, how to write XCUITests for IOS, demo how Amazon Alexa can be automated and how to publish automated results to qTest using a node package.
The recording from Quality Jam 2017 can be found at: www.qasymphony.com/blog/quality-jam-2017-presentations/
5 Steps for Identifying Deficiencies and Fixing Problems FASTDynatrace
5 Steps for Identifying Application Development Deficiencies and Fixing Problems FAST
Are your software development practices and IT systems negatively impacting your overall business? How do you adopt processes that will drive customer and business value quickly, and then extend that throughout your organization?
In this webinar featuring Gary Carr, Software Architect at American Fidelity Assurance, you’ll learn how AFA changed from a process where troubleshooting performance issues involved several iterations between development, QA and production to an environment where top-notch performance of their applications comes easily.
Understand how changes to the business, such as regulatory controls, customer expectations, and development process drove their need to identify deficiencies and fix problems faster so that technology truly supports the goals of their organization and their customers.
• Learn metrics-based techniques to build applications faster and with more confidence, while practically eliminating their defect remediation cycle.
• Find out why separation of duty for the development team no longer serves customers well.
• Discover how seeing all the data for every transaction helps developers connect to users (and one another) with less effort, and helps IT solve problems faster.
DevOpsGuys FutureDecoded 2016 - is DevOps the AnswerDevOpsGroup
DevOps is the Answer, what was the question again?
Everyone is talking DevOps and in this presentation we try and put DevOps in context of Digital Transformation, how you can move to a DevOps model, how Microsoft solutions might form a part of that, and a bit of tech demo thrown in for fun!
Lightning talks on best practices for product and engineering teams to experiment everywhere in their applications.
Originally given at Optimizely's conference: Opticon on October 17th, 2017.
Practical Tips for Ops: End User MonitoringDynatrace
Practical Tips for Ops: End User Monitoring
Watch replay here: https://info.dynatrace.com/apm_wc_devops_journey_series_end_user_monitoring_na_registration.html
Companies that have adopted DevOps Best Practices have 2555x faster lead times* in delivering new features to their end users. However, speed of delivery is not the only success metric! Success must also be measured on how end-users react to the speed of innovation.
Getting insights into how your end-users react to the changes you deploy allows you to share valuable feedback to the Dev and Biz teams. The teams can then see clearly how their changes impacted end-users and where fine tuning can improve infrastructure performance.
In this webcast Andreas Grabner, Chief DevOps Activist, and Brian Chandler, Systems Engineer, share practical tips that IT groups can start to implement quickly. You'll learn:
• Best approach for monitoring end-user mobile versus desktop versus tablet versus service end-points
• How to evaluate network bandwidth requirements by app, service and feature; to better understand and optimize resource consumption
• How to optimize your delivery chain in depth by understanding who is using your app, where, and on what device
• Clear view on which features are being used the most, the least, and what kind of behavior can be observed that is useful in tuning performance
If you are stuck in analysis paralysis, get insights that you can apply today!
*In addition, companies using DevOps are two times more likely to exceed profitability, market share and productivity goals (from the State of DevOps report by Puppet Labs 2016)
Tech Mahindra and CollabNet have worked together on a number of mission-critical projects, and over the course of their partnership have developed unique expertise in lifecycle, development-to-production metrics. Gain an understanding not only of what metrics are important, but also practical approaches to building reports and dashboards that deliver a single-pane view of all your delivery pipelines across the enterprise.
Participants will learn:
KPI’s of end-to-end dashboard driven development and delivery
Best practices for metrics in Agile / DevOps environments
Role of technology frameworks for integrated planning and reporting
Failure is an Option: Scaling Resilient Feature DeliveryOptimizely
Designing a perfect, failproof software delivery system is impossible. Failures will happen. What's more important is the speed and reliability of your recovery.
Shipping with feature flags helps you limit your risk in the first place and recover faster when the unexpected happens.
Today, with Optimizely Agent, companies that build their apps using service-oriented architectures can achieve production-scale faster with their feature delivery and experimentation platform.
Five Ways Automation Has Increased Application Deployment and Changed CultureXebiaLabs
Paychex, a recognized leader in the payroll, human resource, and benefits outsourcing industry, found that the demand for application deployments had increased beyond what could be supported by manual configuration. Keeping up with this demand required a shift from manually providing a service to developing an automated platform for self-service resulting in a culture change with new partnering across their DEV, OPS and Architecture teams.
David Jozis, Automation Engineer at Paychex, discusses the challenges they encountered when making these significant changes and how they were able to overcome them to accomplish 5x as many deployments as before.
JavaOne 2015 Devops and the Darkside CON6447Steve Poole
So you get DevOps. You like the idea and think it’s important. The trouble is that others in your team don’t. This session will help you understand how to convince your team of the benefits of DevOps. Packed with facts and figures, the presentation works through the common challenges Java teams face when moving to a DevOps model and outlines how to address them. It also shows you how to balance evangelism against pragmatism when championing DevOps in your organization. You’ll learn how others have made the transition to DevOps and understand what mistakes to avoid when doing so. Whether you need to know how to be a DevOps evangelist or simply want to understand why DevOps is important, this session is for you.
Performance Metrics Driven CI/CD - Introduction to Continuous Innovation and ...Mike Villiger
Deck used for my talk at the 2016 Spring User Conference in Toronto. Deck was followed up by a walkthrough of a Jenkins workflow that deployed to Cloud Foundry based on jmeter test results
How HipChat Ships and Recovers Fast with DevOps PracticesAtlassian
HipChat operates a ‘You Build It, You Run It’ service model, where developers are responsible for building, testing, and operating their systems. While we have a high speed of development, things can break – but we also recover quickly. Learn about how we've integrated best practices within our planning, building, operating and learning processes to optimize for speed and efficiency but also mitigate, prepare for, and handle incidents.
The presenter will walk you through four steps for how to operate at a high speed of development and also prepare for any incident — planning, prevention, preparation and collecting feedback— and instruct you on how you can build these processes into your Atlasssian workflow (including JIRA Software, HipChat, Bitbucket, Confluence, Bamboo, and StatusPage).
Learn about:
- Planning: How we use JIRA Software and Confluence to plan roadmaps and sync up with teams
- Prevention: Best practices during code reviews and testing
- Preparation: How we prepare for incidents with war games
Review: Collecting feedback, assessing incident causes and improving our processes
Come out of this session with a newfound understanding of how to use Atlassian products within your DevOps workflow!
Mickie Betz, Software Developer, Atlassian
Making the Switch from HP Quality Center to qTestQASymphony
HP Quality Center has been the most widely adopted test management solution in the market to date, however, companies are replacing that solution with new replacement options. QASymphony’s modern qTest platform provides robust functionality that enterprise companies demand, and support for new methodologies like agile, DevOps, and open source automation that will make even the most discerning of testers happy.
To help you seamlessly adopt these top of the line features, we provide a wide array of migration options to satisfy all needs and budgets. Kevin Dunne, VP of Business Development at QASymphony, will provide an overview of his experience migrating dozens of customers from HP QC and he will share his best practices for making a smooth transition into the next generation of test management.
He will cover:
Market Trends — What new developments are shaping the way teams work?
Common Migration Challenges — What hurdles are typically faced in a migration?
Migration Methods — What options does QASymphony recommend for migration?
Migration Best Practices — How are leading companies making the switch?
Agile Incident Response and Resolution in the Wold of DevopsAtlassian
Devops has transformed how teams build and run software: you build it, you own it! In this new Devops world, the methods of responding to and resolving incidents have changed dramatically. You no longer have a 24/7 NOC handling incident response; instead, developers and ops engineers must work closely together and go on-call to triage alerts and resolve incidents.
At the same time, with more applications and services moving to the cloud, the impact of major outages has increased. Most enterprises have multiple major incidents each month and lose over $100K in revenue and lost productivity per incident.
This session describes how to effectively manage the entire incident lifecycle end-to-end, helping teams lower the duration and frequency of outages. We will cover the following topics:
- How to prepare and train your team up-front to respond to incidents quickly.
- How to handle triaging large volumes of alerts, identify the severity of issues, and loop in the right people ASAP.
- How to manage and run an incident effectively across multiple responders and stakeholders.
- How to create a learning feedback loop in your incident lifecycle by conducting a blameless post-mortem.
Overall, we will cover people, process, and tools as they relate to the incident lifecycle. In terms of tooling, we will feature a best-of-breed toolchain from Atlassian, PagerDuty, and other modern innovative companies.
Alex Solomon, CTO and Co-Founder, PagerDuty
Sprinting for Success: Digital Transformation through Agile and DevOpsDynatrace
Verizon is not a startup that can simply copy and apply what works well for Uber, Facebook and other “Unicorn-Companies.” They are challenged by complex IT and business infrastructure accumulated over decades. Yet they wanted to streamline operations, optimize business output and deliver more useful products faster to their consumers.
Verizon’s journey started back in 2011 by identifying Technical Debt, Business Debt and Organizational Rust. Now in 2016, after several years of streamlining their development and IT organization, they run every single project using a “Verizon agile,” DevOps approach.
Download this webinar to hear, Assoc. Director at Verizon Enterprise Solutions, Nita Awatramani, share Verizon’s amazing digital transformation journey. Learn how they re-invented the way they develop, deploy and run their software supporting their business to remain competitive, profitable and relevant, in an era of increasing customer expectations.
Discover how Verizon successfully:
Decreased the number of apps they support by 40%
Reduced IT complexity by consolidating from 13 to 5 data centers
Increased their virtual server footprint 66% while reducing hardware footprint 25%
Implemented a “level-up” mind set for team members through metrics-driven continuous delivery
Nita is joined by Andreas Grabner, Performance Advocate at Dynatrace who will support why monitoring, application and end user metrics have to be a key part of your own transformation!
Nita Awatramani
Associate Director at Verizon Enterprise Solutions
Nita Awatramani is responsible for infrastructure program management, security, compliance and business operations for Verizon Enterprise Solutions pre-sales and ordering systems. She has been with Verizon for 15 years, first with Consumer and Mass Business and then with Verizon Enterprise Solutions. She has a bachelor’s degree in Mathematics and a master’s in Computer Science. She holds a CISSP certification and is currently pursuing the Advanced Computer Security Program at Stanford.
Andreas Grabner
Performance Advocate at Dynatrace
Andreas Grabner has 15+ years’ experience as an architect and developer in the Java and .NET space. In his current role, Andi works as an advocate for high performing applications in both the development and operations areas. He is a regular expert and contributor to large performance communities, a frequent speaker at technology conferences and regularly publishes articles blogs on blog.dynatrace.com
Where Testers & QA Fit in the Story of DevOpsQASymphony
Where Testers and QA Fit in the Story of DevOps
Continuous delivery. CI. GitHub. Scrum. CD. Jenkins. Continuous testing. Continuous integration. These are just some terms that are supposed to describe the word soup that is DevOps. Chances are that you have heard some or all of these words being passed around at your daily stand ups or company meetings.
However, where does QA and testing fit into the story of DevOps? Some would say that developers and operations teams are all you need for a successful DevOps pipeline, while others show that Dev, Test and Ops need to be included to ensure quality at every step in your pipeline.
In this webinar, Ryan Yackel, QASymphony's Director of Product Marketing, and Sunil Sehgal, Managing Partner at TechArcis, will share their experiences as they navigate you through the DevTestOps waters. In this webinar you will learn:
Overview of the State of DevOps
Common misconceptions of DevOps and QA
How testers must adapt to the DevOps process
The tools testers need for continuous testing
Can't make the webinar? Sign up and we will send you the recording.
Quality Jam 2017: Kevin Dunne "Macro Trends and Useful Tools that 'Get It'"QASymphony
Testers can’t live without their beloved tools, and the landscape of testing and development tools is changing rapidly. While testers were previously limited to a few expensive and difficult to use tools, the market is now filling with many more affordable, powerful, and easy to use products. In this presentation, Kevin will discuss 5 of the most important macro trends in test tools: 1) Specialization 2) Cloud hosting 3) Architectural Shifts 4) Collaboration 5) Ease of Use/Deployment. Kevin will also provide examples of popular tools that are capitalizing on these trends and gaining popularity in the market.
Watch the Quality Jam presentation at www.qasymphony.com/blog/quality-jam-2017-presentations/
Machine Learning to Turbo-Charge the Ops Portion of DevOpsDeborah Schalm
Already on a continuous or short-cycle delivery? Constantly rewiring your apps with microservice and similar architectures? Maintaining visibility and maximizing service levels once this stuff gets into production could be a regular nightmare. Coding instrumentation into your apps is time-consuming and error-prone. Instead, let machine learning do the work of adapting your monitoring to your fast-moving application environments. In this webcast learn about various types of machine learning that are optimized for operational data, and see in a demo how this could be leveraged to ensure your ops move as fast as rest of your DevOps pipeline.
Quality Jam 2017: Elise Carmichael and Corey Pyle "Jumpstarting Your Test Aut...QASymphony
Elise Carmichael and Corey Pyle walk you through real-life test automation stories and use cases including: How to decide which tests to automate, how to write XCUITests for IOS, demo how Amazon Alexa can be automated and how to publish automated results to qTest using a node package.
The recording from Quality Jam 2017 can be found at: www.qasymphony.com/blog/quality-jam-2017-presentations/
5 Steps for Identifying Deficiencies and Fixing Problems FASTDynatrace
5 Steps for Identifying Application Development Deficiencies and Fixing Problems FAST
Are your software development practices and IT systems negatively impacting your overall business? How do you adopt processes that will drive customer and business value quickly, and then extend that throughout your organization?
In this webinar featuring Gary Carr, Software Architect at American Fidelity Assurance, you’ll learn how AFA changed from a process where troubleshooting performance issues involved several iterations between development, QA and production to an environment where top-notch performance of their applications comes easily.
Understand how changes to the business, such as regulatory controls, customer expectations, and development process drove their need to identify deficiencies and fix problems faster so that technology truly supports the goals of their organization and their customers.
• Learn metrics-based techniques to build applications faster and with more confidence, while practically eliminating their defect remediation cycle.
• Find out why separation of duty for the development team no longer serves customers well.
• Discover how seeing all the data for every transaction helps developers connect to users (and one another) with less effort, and helps IT solve problems faster.
DevOpsGuys FutureDecoded 2016 - is DevOps the AnswerDevOpsGroup
DevOps is the Answer, what was the question again?
Everyone is talking DevOps and in this presentation we try and put DevOps in context of Digital Transformation, how you can move to a DevOps model, how Microsoft solutions might form a part of that, and a bit of tech demo thrown in for fun!
Lightning talks on best practices for product and engineering teams to experiment everywhere in their applications.
Originally given at Optimizely's conference: Opticon on October 17th, 2017.
Practical Tips for Ops: End User MonitoringDynatrace
Practical Tips for Ops: End User Monitoring
Watch replay here: https://info.dynatrace.com/apm_wc_devops_journey_series_end_user_monitoring_na_registration.html
Companies that have adopted DevOps Best Practices have 2555x faster lead times* in delivering new features to their end users. However, speed of delivery is not the only success metric! Success must also be measured on how end-users react to the speed of innovation.
Getting insights into how your end-users react to the changes you deploy allows you to share valuable feedback to the Dev and Biz teams. The teams can then see clearly how their changes impacted end-users and where fine tuning can improve infrastructure performance.
In this webcast Andreas Grabner, Chief DevOps Activist, and Brian Chandler, Systems Engineer, share practical tips that IT groups can start to implement quickly. You'll learn:
• Best approach for monitoring end-user mobile versus desktop versus tablet versus service end-points
• How to evaluate network bandwidth requirements by app, service and feature; to better understand and optimize resource consumption
• How to optimize your delivery chain in depth by understanding who is using your app, where, and on what device
• Clear view on which features are being used the most, the least, and what kind of behavior can be observed that is useful in tuning performance
If you are stuck in analysis paralysis, get insights that you can apply today!
*In addition, companies using DevOps are two times more likely to exceed profitability, market share and productivity goals (from the State of DevOps report by Puppet Labs 2016)
Tech Mahindra and CollabNet have worked together on a number of mission-critical projects, and over the course of their partnership have developed unique expertise in lifecycle, development-to-production metrics. Gain an understanding not only of what metrics are important, but also practical approaches to building reports and dashboards that deliver a single-pane view of all your delivery pipelines across the enterprise.
Participants will learn:
KPI’s of end-to-end dashboard driven development and delivery
Best practices for metrics in Agile / DevOps environments
Role of technology frameworks for integrated planning and reporting
Failure is an Option: Scaling Resilient Feature DeliveryOptimizely
Designing a perfect, failproof software delivery system is impossible. Failures will happen. What's more important is the speed and reliability of your recovery.
Shipping with feature flags helps you limit your risk in the first place and recover faster when the unexpected happens.
Today, with Optimizely Agent, companies that build their apps using service-oriented architectures can achieve production-scale faster with their feature delivery and experimentation platform.
Unlocking the Power of ChatGPT and AI in Testing - NextSteps, presented by Ap...Applitools
Gain insights into the practical applications of ChatGPT, Bard, and other AI-based technological advancements, including GitHub CoPilot and Applitools Self-Healing Cloud, in this session with Anand Bagmar. Through specific use cases, Anand demonstrates how to enhance test automation processes—making them faster, more stable, and easier to implement.
Session recording and more info at applitools.com
Uncover how these tools can revolutionize your testing strategies and stay ahead of the curve in the ever-evolving world of test automation.
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
What is your role as a BA on a Scrum team? How do you fit in? This presentation was given to the IIBA conference in NZ in 2010 by Stephen Reed. Stephen had worked extensively as a BA and moved into using Scrum with multiple teams at a large Insurance company. This experience led to a lot of questions around what the BA should be doing on a Scrum team. This presentation goes some way to listing what worked in the teams Stephen was involved in. The BA role does not change and all the skills of a great BA are necessary still on a great Software Development team, just more focused on being a team member and utilising those skills for the Scrum process of getting working software to the customer with more focus and clarity for the user.
How to feature flag and run experiments in iOS and AndroidOptimizely
Join Tom Zurkan and Kody O’Connell from Optimizely’s Engineering and Developer Relations teams to learn about the developer experience for the iOS and Android SDKs.
In this webinar, you’ll learn:
- How feature flagging sets a strong foundation for app development
- How the iOS and Android SDKs work
- What to expect when implementing and maintaining Full Stack in your app
- The steps to create feature flags and experiments in your app
- How to get started for free with Optimizely Rollouts
Continuous Delivery: Responding to Change Faster Than Ever Before - SDEC14Mike Bowler
Presentation given at SDEC14 in Winnipeg. The slides likely aren't very useful without the attending discussion but people have asked for the slides to be made available
This is the English version of my talk about agile software development practices at Agile Talks seminars in Ankara, Turkey. I tried to focus on the nature of software development and figure out the development practices that let us build software in natural way.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
How to Build in Quality from Day 1 using Lean QA and Agile TestingAtlassian
If you're struggling to implement QA methods that fit with agile's core principles, you're not alone. Join Giancarlo and Maurizio as they explain how their teams found a sweet spot at the intersection of agile and QA engineering. They'll share common pitfalls and how to avoid them. Plus, get tips and tricks on how to capture requirements and link JIRA to test repositories for complete traceability.
Agile Development of High Performance ApplicationsFabian Lange
Slides from my talk at gearconf 2010 in Düsseldorf, discussing Performance as an important non-functional requirement. Because NFRs are hard to test, I showed how AppDynamics Lite could be used to ease pain and build better performing apps.
If you are interested in performance and application performance monitoring, visit our blog:
http://blog.codecentric.de/en/category/performance-en/
If you want to try appdynamics lite yourself, download it at http://appdynamics.com/free
Accelerate User Driven Innovation [Webinar]Dynatrace
https://info.dynatrace.com/apm_dtm_ops_17q4_wc_accelerate_user_driven_innovation_en_registration.html
Accelerate User Driven Innovation [Webinar]
DevOps adopters are more agile, more reliable and more successful but, only 2% of companies worldwide have adopted DevOps best practices.
We know it’s more difficult for enterprises companies with legacy systems and processes to get started but it isn’t impossible.
To help you accelerate your own DevOps journey & realise some of the benefits, we’re thrilled to be hosting international DevOps experts Andreas Grabner, Mark Tomlinson and James Pulley.
With combined experience across hundreds of DevOps deployments they have some remarkable use cases to share including Verizon, and even our own story of transforming from on premise six month waterfall deployment to a cloud native one hour continuous delivery model.
Don’t miss these amazing insights. Register today!
Building Products That Think- Bhaskaran Srinivasan & Ashish GuptaISPMAIndia
Presenters:
Bhaskaran Srinivasan, Senior Strategy Consultant
Ashish Gupta, Senior Product Manager, Google
Abstract:
This workshop is designed to introduce participants to the opportunities that Generative AI offers through the process steps of a standard NPI. The program provides insights into the capabilities and limitations of Generative AI, offering a hands-on exploration of Gen AI tools tailored for product managers. Attendees will learn how to seamlessly integrate Generative AI into their daily product management workflows, identifying opportunities and prioritizing them based on impact and feasibility. The workshop introduces a robust framework for developing Generative AI-powered products, taking into account crucial factors such as customer pain points, market segment, data and algorithm biases, transparency, user control, and privacy. To enhance the learning experience, the workshop incorporates interactive talks, case study coverage, and group-based hands-on exercises. Geared towards mid-level product managers with a foundational understanding of product management best practices, the workshop is facilitated by two seasoned speakers with expertise in product innovation.
Clover Rings Up Digital Growth to Drive ExperimentationOptimizely
Clover's Digital Growth team is responsible for optimizing the merchant's digital experience and they rely on experimentation to guide digital decision-making. This enables them to quickly learn and measure what changes deliver the best outcomes for users.
Join us with Lead Product Manager of Growth, Monil Shah, to learn how Clover:
- Increased digital conversions amongst merchants with an investment in experimentation
- Grew experiment velocity by 4x after replacing Adobe Target
- Designed a framework to efficiently capture and prioritize test ideas, and roll out winners
Learn the real best practices and pitfalls of experimentation based on scientific research and insights. Hazjier is co-author of three studies on experimentation with Harvard Business School and his work is covered in the book Experimentation Works. This talk will dive into the best practices of experiment design, the role of hierarchy in experimentation teams, and the value of experimentation.
Atlassian's Mystique CLI, Minimizing the Experiment Development CycleOptimizely
Mystique CLI is an Atlassian developed CLI for Optimizely Web. It is a multi-phase project that is currently focusing on improving the development cycle for growth engineers. Currently, Mystique is the standard for developing web experiments at Atlassian, and is capable of a wide variety of operations utilizing Optimizely's REST API. This includes creating, updating, testing, and duplicating experiments/personalization campaigns, as well as "promoting" these entities between Optimizely projects for different environments (e.g. from QA => Prod). It has significantly reduced manual overhead and decreased development time by up to 95% for particular actions.
Autotrader Case Study: Migrating from Home-Grown Testing to Best-in-Class Too...Optimizely
Autotrader's Product and Engineering teams were ahead of the curve many years ago when they built a home-grown solution for leveraging feature flags to support server-side testing. Over the years, the industry eventually caught up and surpassed this proprietary tooling and the team had a choice to make: Re-invest into the local solution or completely retool. In this case study, Scott Povlot, Principal Technical Architect, and Seth Stuck, Director of R&D Analytics, will discuss their journey in selecting and then migrating to their next generation of experimentation tooling. They will discuss selection criteria, pros and cons, and outline how they were able to make the migration to Optimizely successful and lessons learned along the way.
Zillow + Optimizely: Building the Bridge to $20 Billion RevenueOptimizely
Join Jason Tabert, Senior CRO Marketing Specialist, and learn how Zillow is using Optimizely’s experimentation, personalization and integrations to help grow their revenue to $20 billion by helping their customers cross the real estate chasm from despair to delight.
The Future of Optimizely for Technical TeamsOptimizely
Optimizely has been reimagining the future of progressive delivery and experimentation, improving every part of the platform to empower technical teams to build, ship, and iterate faster. Learn about the latest enhancements to Optimizely Full Stack and the Optimizely Data Platform, and get a sneak peek at the upcoming roadmap.
Empowering Agents to Provide Service from Anywhere: Contact Centers in the Ti...Optimizely
The coronavirus pandemic has pushed contact center leaders to accelerate technology adoption and empower their teams to work remotely. Join this session with State Farm, Salesforce, and Optimizely to learn how contact centers can adapt quickly and successfully in the time of COVID.
Our new normal has accelerated eCommerce trends by 4-6 years. The Optimizely team shares how experimentation can help retailers fast forward their online sales strategy with Microsoft Dynamics 365 Commerce.
Building an Experiment Pipeline for GitHub’s New Free Team OfferingOptimizely
In April 2020, GitHub announced a new Free for Teams plan. Behind the scenes, the engineering team was also setting up an experiment pipeline and an integration with Optimizely. In this session, we will take a peek at the process of setting up the integration, learning about the behavior of this new Free for Teams customer segment, and the next steps for this experiment pipeline.
AMC Networks Experiments Faster on the Server SideOptimizely
Speeding up innovation only matters if it helps you drive positive outcomes. At AMC, experimentation enables the product and platform teams to challenge their assumptions, maximize impact, and evaluate ideas as painted door tests before investing in significant development. A commitment to test everything across 9 platforms fueled their search for the most scalable solution.
In this session, you'll learn how to:
Leverage server-side testing to experiment quickly
Scale across web, mobile, and OTT applications
Determine when client-side testing is more efficient
Evolving Experimentation from CRO to Product DevelopmentOptimizely
An obsession with data, efficiency, and delivering incredible customer experiences are just a few things that the CNN Consumer Science and Software Engineering teams have in common. Simple A/B testing practices evolved into a culture of experimentation, sparking new development practices across the organization. Learn how they drive results across their entire platform from websites to mobile apps.
Overcoming the Challenges of Experimentation on a Service Oriented ArchitectureOptimizely
Growing from an early stage startup to a national leader in financial literacy is no small feat, and there are a ton of lessons that we have learned at Greenlight as we have grown. Long gone are the days where we would ship something and cross our fingers hoping that it makes some kind of impact on our customers. Now we’re in a world where we can learn ahead of time how much impact a feature will have on the business, before we even launch! In today’s conversation, we’ll discuss how we use Optimizely’s feature flags in our microservice architecture using Optimizely Agent while keeping user IDs and context synchronized.
This session will cover:
How we set up Optimizely Agent and use it in a kubernetes deployment
How we created a user-aliasing service
How we access Optimizely both on the frontend and in the backend services.
How to build a full stack feature
How to manage the rollout using Optimizely’s feature flags
How The Zebra Utilized Feature Experiments To Increase Carrier Card Engagemen...Optimizely
A/B testing is an essential element in any product managers playbook. However having the freedom and flexibility to customize testing based on what the data is saying often requires a lot of time and effort, particularly when it comes to engineering resources. Optimizely offers a flexible approach to experimentation through the use of feature testing, which provides more customization options without the additional development effort typically required to implement these feature optimizations. Megan Bubley, a Senior Product Manager at The Zebra, will share her experience working with Optimizely’s feature tests to create a results page where users can compare multiple auto insurance options driven by actual user needs, as well as her experience customizing the experience based on device platform.
Making Your Hypothesis Work Harder to Inform Future Product StrategyOptimizely
At Treatwell, each experiment goes beyond improving a single business metric. Experimentation works to evolve their product while enriching customer insights in order to deliver the best digital experience to their users. Join Laura Howard, Lead Product Manager, and Dennis Meisner, Senior Product Analyst, to learn their secret to making their hypothesis work harder and how getting their hypothesis right has improved Treatwell’s funnel progression and order health, as well as helped them make critical decisions on their product experience.
Kick Your Assumptions: How Scholl's Test-Everything Culture Drives RevenueOptimizely
Amy Vetter, Consumer Experience Manager, Direct To Consumer, Europe, will walk you through some of the tests that she and her team run across the Scholl brand. Amy will highlight surprise learnings and how to remove the fear of failing. The team is empowered to test everything possible that will allow the customer to get the best experience and also support the brand’s goal for more revenue and customer data.
At Charles Schwab, they have a mantra of viewing the world through their client’s eyes. When it comes to building digital experiences and running experiments, winning isn’t just about moving metrics, it’s also about improving customer experience. Sara Tresch, SVP of Digital Services at Schwab will be discussing how Schwab designs products and experiments with a client-first mindset.
Shipping to Learn and Accelerate Growth with GitHubOptimizely
Will 2020 mark the shift to a remote-first world in the long run? For GitHub, a distributed workforce is nothing new. Join Sha Ma, VP of Engineering, and Gregory Ceccarelli, Director of Data Science, to learn how they built and scaled a successful experimentation program. They'll share their experience implementing Optimizely across timezones, a remote workforce, and a new business model.
In this session, you'll learn how to:
Optimize UX for a freemium business model
Use data to deliver customer-centered products
Scale experimentation and accelerate growth
Test Everything: TrustRadius Delivers Customer Value with ExperimentationOptimizely
When done right, experimentation can help you validate the product you’re building and create winning customer experiences. And it doesn’t take a big engineering team to make this happen.
TrustRadius, the most trusted review site for business technology, uses experimentation to build an online community through website and server-side experimentation. The small but mighty TrustRadius team runs experiments throughout the buyer’s journey to engage different user personas and understand outcomes in real-time.
Watch the webinar recording featuring Rilo Stark, product manager at TrustRadius, and Jack Peden, senior software engineer, to understand their data-driven experimentation strategy and how TrustRadius uses Optimizely Web and Full Stack products to tailor experiences to different customer segments and mitigate risk through A/B/N and painted door tests.
In this session, you will learn: how to embed feature flagging sitewide to deliver safer, faster releases, best practices for implementing feature flags in a services-oriented architecture, and the latest enhancements you need to help your team recover faster when ship happens.
The world of search engine optimization (SEO) is buzzing with discussions after Google confirmed that around 2,500 leaked internal documents related to its Search feature are indeed authentic. The revelation has sparked significant concerns within the SEO community. The leaked documents were initially reported by SEO experts Rand Fishkin and Mike King, igniting widespread analysis and discourse. For More Info:- https://news.arihantwebtech.com/search-disrupted-googles-leaked-documents-rock-the-seo-world/
Taurus Zodiac Sign_ Personality Traits and Sign Dates.pptxmy Pandit
Explore the world of the Taurus zodiac sign. Learn about their stability, determination, and appreciation for beauty. Discover how Taureans' grounded nature and hardworking mindset define their unique personality.
What is the TDS Return Filing Due Date for FY 2024-25.pdfseoforlegalpillers
It is crucial for the taxpayers to understand about the TDS Return Filing Due Date, so that they can fulfill your TDS obligations efficiently. Taxpayers can avoid penalties by sticking to the deadlines and by accurate filing of TDS. Timely filing of TDS will make sure about the availability of tax credits. You can also seek the professional guidance of experts like Legal Pillers for timely filing of the TDS Return.
Improving profitability for small businessBen Wann
In this comprehensive presentation, we will explore strategies and practical tips for enhancing profitability in small businesses. Tailored to meet the unique challenges faced by small enterprises, this session covers various aspects that directly impact the bottom line. Attendees will learn how to optimize operational efficiency, manage expenses, and increase revenue through innovative marketing and customer engagement techniques.
Remote sensing and monitoring are changing the mining industry for the better. These are providing innovative solutions to long-standing challenges. Those related to exploration, extraction, and overall environmental management by mining technology companies Odisha. These technologies make use of satellite imaging, aerial photography and sensors to collect data that might be inaccessible or from hazardous locations. With the use of this technology, mining operations are becoming increasingly efficient. Let us gain more insight into the key aspects associated with remote sensing and monitoring when it comes to mining.
Unveiling the Secrets How Does Generative AI Work.pdfSam H
At its core, generative artificial intelligence relies on the concept of generative models, which serve as engines that churn out entirely new data resembling their training data. It is like a sculptor who has studied so many forms found in nature and then uses this knowledge to create sculptures from his imagination that have never been seen before anywhere else. If taken to cyberspace, gans work almost the same way.
Business Valuation Principles for EntrepreneursBen Wann
This insightful presentation is designed to equip entrepreneurs with the essential knowledge and tools needed to accurately value their businesses. Understanding business valuation is crucial for making informed decisions, whether you're seeking investment, planning to sell, or simply want to gauge your company's worth.
Skye Residences | Extended Stay Residences Near Toronto Airportmarketingjdass
Experience unparalleled EXTENDED STAY and comfort at Skye Residences located just minutes from Toronto Airport. Discover sophisticated accommodations tailored for discerning travelers.
Website Link :
https://skyeresidences.com/
https://skyeresidences.com/about-us/
https://skyeresidences.com/gallery/
https://skyeresidences.com/rooms/
https://skyeresidences.com/near-by-attractions/
https://skyeresidences.com/commute/
https://skyeresidences.com/contact/
https://skyeresidences.com/queen-suite-with-sofa-bed/
https://skyeresidences.com/queen-suite-with-sofa-bed-and-balcony/
https://skyeresidences.com/queen-suite-with-sofa-bed-accessible/
https://skyeresidences.com/2-bedroom-deluxe-queen-suite-with-sofa-bed/
https://skyeresidences.com/2-bedroom-deluxe-king-queen-suite-with-sofa-bed/
https://skyeresidences.com/2-bedroom-deluxe-queen-suite-with-sofa-bed-accessible/
#Skye Residences Etobicoke, #Skye Residences Near Toronto Airport, #Skye Residences Toronto, #Skye Hotel Toronto, #Skye Hotel Near Toronto Airport, #Hotel Near Toronto Airport, #Near Toronto Airport Accommodation, #Suites Near Toronto Airport, #Etobicoke Suites Near Airport, #Hotel Near Toronto Pearson International Airport, #Toronto Airport Suite Rentals, #Pearson Airport Hotel Suites
Enterprise Excellence is Inclusive Excellence.pdfKaiNexus
Enterprise excellence and inclusive excellence are closely linked, and real-world challenges have shown that both are essential to the success of any organization. To achieve enterprise excellence, organizations must focus on improving their operations and processes while creating an inclusive environment that engages everyone. In this interactive session, the facilitator will highlight commonly established business practices and how they limit our ability to engage everyone every day. More importantly, though, participants will likely gain increased awareness of what we can do differently to maximize enterprise excellence through deliberate inclusion.
What is Enterprise Excellence?
Enterprise Excellence is a holistic approach that's aimed at achieving world-class performance across all aspects of the organization.
What might I learn?
A way to engage all in creating Inclusive Excellence. Lessons from the US military and their parallels to the story of Harry Potter. How belt systems and CI teams can destroy inclusive practices. How leadership language invites people to the party. There are three things leaders can do to engage everyone every day: maximizing psychological safety to create environments where folks learn, contribute, and challenge the status quo.
Who might benefit? Anyone and everyone leading folks from the shop floor to top floor.
Dr. William Harvey is a seasoned Operations Leader with extensive experience in chemical processing, manufacturing, and operations management. At Michelman, he currently oversees multiple sites, leading teams in strategic planning and coaching/practicing continuous improvement. William is set to start his eighth year of teaching at the University of Cincinnati where he teaches marketing, finance, and management. William holds various certifications in change management, quality, leadership, operational excellence, team building, and DiSC, among others.
Explore our most comprehensive guide on lookback analysis at SafePaaS, covering access governance and how it can transform modern ERP audits. Browse now!
RMD24 | Debunking the non-endemic revenue myth Marvin Vacquier Droop | First ...BBPMedia1
Marvin neemt je in deze presentatie mee in de voordelen van non-endemic advertising op retail media netwerken. Hij brengt ook de uitdagingen in beeld die de markt op dit moment heeft op het gebied van retail media voor niet-leveranciers.
Retail media wordt gezien als het nieuwe advertising-medium en ook mediabureaus richten massaal retail media-afdelingen op. Merken die niet in de betreffende winkel liggen staan ook nog niet in de rij om op de retail media netwerken te adverteren. Marvin belicht de uitdagingen die er zijn om echt aansluiting te vinden op die markt van non-endemic advertising.
Falcon stands out as a top-tier P2P Invoice Discounting platform in India, bridging esteemed blue-chip companies and eager investors. Our goal is to transform the investment landscape in India by establishing a comprehensive destination for borrowers and investors with diverse profiles and needs, all while minimizing risk. What sets Falcon apart is the elimination of intermediaries such as commercial banks and depository institutions, allowing investors to enjoy higher yields.
Accpac to QuickBooks Conversion Navigating the Transition with Online Account...PaulBryant58
This article provides a comprehensive guide on how to
effectively manage the convert Accpac to QuickBooks , with a particular focus on utilizing online accounting services to streamline the process.
5 Things You Need To Know Before Hiring a Videographer
Taking Your Product Development to the Next Level with Full Stack
1.
2. 2
▪ Sessions today will be recorded and will be available after
Opticon
▪ Join the conversation on Twitter at #Opticon19
▪ Like what you’ve seen at Opticon? Give feedback and rate
sessions on the mobile app
7. “Our success is a function of how
many experiments we do per
year, per month, per week, per
day.”
Jeff Bezos
“Our aim is to create the best
product for our customers, and
we do that through constant
innovation and testing.”
Gillan Tans, CEO
“Our company culture
encourages experimentation
and free flow of ideas.”
Larry Page
“We use experimentation and
testing to inform as much of the
business as we possibly can” -
Gregory Peters, CPO
Today’s Digital Leaders Win By Using
Experimentation At-Scale
8.
9. Frontend UI Backend Business
Logic & Data
The anatomy of an experience
i.e. navigation,
search location
& visual treatment
Copy
Images &
Colors
Layout Search algorithms
Personalize content
based on previous
behavior
Recommendations
Make your headlines
more personal
16. 18
Full Stack Mission
To provide best-in-class product experimentation and
feature flagging infrastructure that is accessible, flexible,
and easy for any business to adopt.
17. 19
How it Works
Project Datafile
Client SDKs
Server SDKs
Event Tracking
Event Tracking
1. Configure Flags and
Experiments in
Optimizely
1. Update the Datafile
1. SDKs make decisions
locally, track events
asynchronously
1. Review results in
Optimizely
20. “
”Al Boley, Senior Product Manager, BBC
What if at the end of an episode, we
automatically played the next
episode? Let’s just try it…
21. Next episode starts in…
Peaky Blinders
1
Series 5, Episode 2
The Peaky Blinders come
under fire when Tommy finds
danger on his doorstep and a
friend is brutally attacked.
Cancel
27. “
”- Emily Dresner, Chief Technology Officer, Upside Travel
We want to rapidly prune out the ideas that
will lower conversion. If we put something
out in production that doesn’t seem to be
working, we want to get rid of it quickly.
31. “
”- Kyla Workman, Product Owner - Brightside at ATB
Financial
Optimizely improves our developer workflow,
allows to manage features securely, and gives us
more confidence. Now, we can deploy incomplete
features safely behind a feature flag and
dynamically update who gets access to features.
34. Easy-to-use Scalable
Developers can get started
quickly, from install through first
flag
and first experiment
Meets your technical and
governance requirements
Supports the technologies you use
and use cases you care about
Flexible
35. 39Opticon18 Opticon19 Q1 2020
Q4 2018 Q1 2019 Q2 2019 Q4 2019
Easy-to-use
TRACK1TRACK2TRACK3
Scalable
Flexible
JSON Variables
Easy Event
Tracking
Fast
Datafile
Updates
Flexible
Targeting
Optimizely
Rollouts Event
Processor
Automatic
Datafile
Updates
Go SDKReact Native
SDK
React SDKSwift SDK Full Stack
Service
Project Config
APIs
Change History
+ Audit Log
Targeted
Rollouts
Results for
Environments
Full Stack
Console
36.
37. 41
How it Works
Project Datafile
Client SDKs
Server SDKs
Event Tracking
Event Tracking
1. Configure Flags and
Experiments in
Optimizely
1. Update the Datafile
1. SDKs make decisions
locally, track events
asynchronously
1. Review results in
Optimizely
40. 44
1/10Developers created flags
in <30min without help
10/10Developers created flags
in <30min without help
Before Automatic
Datafile Management
With Automatic
Datafile Management
41. “
”- Lucas Reis, Senior Software Engineer II, Compass.
The automatic datafile management
in the Java SDK is great, it made
overall adoption super easy and
smooth.
74. “
”- Michael Alley, Head of Product, StubHub
We’ve integrated Optimizely as part of our
infrastructure, which enables weekly changes to
the entire pricing portfolio; visibility into the
impact of price on conversion; and thousands of
decisions in near-real time.
80. Begin your journey to product experimentation
Start with
Optimizely Rollouts for free
to ship faster with less risk
When you’re ready to
experiment then upgrade to
Optimizely Full Stack
81. 101
Fast Datafile
Updates
Rollouts +
Environments
Easy Event
Tracking
Flexible
Targeting
Cross-Project
Events
Automatic
Datafile
Updates
Swift SDK
Optimizely
Rollouts
Event
Processor
(beta)
React SDK
(beta)
Go SDK (beta)
Change History
+ Audit Log
Targeted
Rollouts
Results for
Environments
React Native
SDK
Full Stack
Service
Full Stack
Console
JSON Variables
Opticon18 Opticon19
Project Config
APIs
85. Up Next…
▪ Refreshments now being served in the Expo Hall
▪ Fireside Chat with Optimizely Co-founder Dan Siroker at 2:15pm
▪ Closing Keynote with Dr. Mae Jemison at 2:45pm
Editor's Notes
Welcome to Take Your Product to the Next Level with Full Stack — the final breakout session at Opticon!
I’m Jamie Connolly, Senior Product Manager at Optimizely. I lead our Full Stack product, as well as the core app platform that serves both Web and Full Stack.
I’ve been with the company for six and a half years — this is my sixth Opticon. I’m incredibly excited to be here today, and to speak with you all about this subject.
This presentation covers four topics:
- Why we at Optimizely believe product experimentation is so important — i.e. the reasons we built Full Stack
- What’s required from a product experimentation platform
- How Full Stack works, and how our customers use it
- And finally, our roadmap – the features we’ve built — and are building now — and the reasons those features are important
But first, I want to begin with a celebration
Today is Full Stack’s third birthday!
Let’s consider an example — AirBnB’s website, or your company’s website
- The set of things that you con test on the frontend is limited …
- But, there’s so much more beyond the frontend
- Search, recommendation, the algorithms that you might use to personalize your site, or help your users discover your products. The business logic that defines your customer experience
And for many businesses, your website is just one of many customer touchpoints. You may have mobile experiences, OTT or IOT experiences, perhaps a kiosk in your physical store.
Your call centers / support channels, the algorithms that route product through your warehouse and into customer’s hands.
Ultimately, then frontend of your website is just the tip of the iceberg.
It’s an important tip – acquiring new business is essential. But if you’re only experimenting on the look and feel of your acquisition funnel, you’re just scratching the surface.
Let’s look at Optimizely, as a specific example. If you count lines in our codebase, the marketing website — i.e. our acquisition funnel — represents about 13% of our customer experience.
Our product covers the remaining 87%
And, this estimate is conservative — I didn’t differentiate between server-side marketing website code and client-side marketing website code. If I had, the distribution would be even more skewed.
While this is just a rough approximation, and while your business may be different from ours, it provides a loose sense of just how much you’re missing if you aren’t experimenting in product
If you aren’t familiar with Full Stack, I want to introduce you to a few companies who are having success today,
how they’re experimenting in their products
Examples of their use cases
Don’t talk about pricing
It's worth mentioning that there are several different kinds of rollout you can do.
One of the most common ones is to have something first enabled just in a local environment for a single developer
And then roll it out to a staging environment.So whether that's a preproduction environment or a staging, you can actually use these rollouts to launch something in there.
And then to go from staging out to maybe a small set of Beta users. So there's a different kind of rollout that's actually targeted to a certain audience or a certain whitelist of people that you've specifically decided should see your new stuff. We do this all the time. As a B2B company, we find friendly customers that wanna give new features a try, even some of our bigger companies might be more sensitive. We're not quite ready to try out a new feature until it's more fully baked.
From there, once you've validated in the Beta, you can do a gradual rollout where you slowly ramp up traffic to a larger audience and roll back if anything goes wrong.
And then and only then we can do that 100% rollout where everybody has a new feature. And the key idea here is that we can mix and match these techniques. It's not that one of these is the right answer. I think for each different business and each different product or feature within that, you wanna choose what the right rollout strategy is. But I would argue the right rollout strategy is almost never to just flip the switch. The gradual process is usually much more reliable.
If you aren’t familiar with Full Stack, I want to introduce you to a few companies who are having success today,
How they’re experimenting in their products
Examples of their use cases
**** Call BBC out as “one of our longest tenured Full Stack customers
*** This was already highlighted in last year’s keynote
Either call that out o
r replace
Anyone who say it last year might think we’re struggling for new success stories
This is a sample quote slide
This is a sample quote slide
- Emphasize that this means we’re in their critical path, and that they trust us to be in their critical path
We just looked at several successful in-product experimenters, and the aggregate growth of product experimentation across our customer. I want to close with one more example, this time of a customer who’s just getting started.
ATB Financial is an 80 year old Canadian bank that recently launched Brightside, a new business — and entirely digital bank. Brightside’s goal is to bring ATB into the modern world — providing a mobile banking service that fits the preferences and patterns of young customers.
ATB uses Rollouts, the free version of Full Stack, with the following goal — to wrap every new feature in a feature flag, both a safeguard and to facilitate data-driven development.
One customer that’s adopting Rollouts to help transform the way they ship product is ATB Financial. ATB is a Canadian financial institution that’s been around over 80 years and has over 5K employees. To respond to their customers needs and trends in the market, they decided to build a new type of bank. An all-digital, mobile-first bank and in order to roll out it safely they choose Optimizely Rollouts
Established Canadian bank launching an all-digital new business.
And they’ve been successful. Kyla Workman, a Brightside Product Owner, said the following:
As I mentioned a moment ago, this is was achieved entirely with Rollouts — our free product. If you aren’t experimenting in product today, I would strongly encourage you to give Rollouts a try. It’s very powerful and valuable on its own, and, once you’re ready, the transition from Rollouts to Full Stack is seamless.
If you or you company are new to this idea — or if you’re looking to ship faster with less risk, we’ve made getting started incredible easy via Optimizely rollouts. Rollouts is a free product build on the Full Stack platform — with the key features required for a business to get started.
I do wanna mention Optimizely Rollouts. This is actually our newest product that we just launched just about a month ago and it's a free solution for doing feature flagging and rollouts. So everything we just talked about, about Canary Releases, silent launches, Feature Toggling. You can do yourself in your own application all for free. You don't need to pay for any new products, so I would really encourage you to check out optimizely.com/rollouts and see if this could be a fit for your team. Please encourage your developers to try this out. We are real believers in this way of working. That's why we've actually made this free and open source. We want anybody to be able to experience the power of Feature Flag in Rollouts. And we see that as a great on-ramp towards adopting these other pieces of experimentation. Optimizely Rollouts is available in 10 different languages, including all the major mobile frameworks as well as Java, JavaScript, C#, Python, PHP, Ruby, Node, you name it, all the major languages. You can start implementing features in Rollouts all for free and see if that's a good fit for your development team.
This is a sample quote slide
Alright, so – that’s my pitch — why we think product experimentation is important, what we’ve built to democratize the process, and a bit about how customers are using the product today.
For the remainder of our session, I want to talk about the product. Specifically our roadmap — that things we’ve built, and the things we’re building.
Our roadmap is governed by three principles: developer ease-of-use, flexibility, and scalability.
We want to make the product easy to adopt, from setup, to first flag, to first experiment
The product must be flexible — both in terms of the technologies it supports, and the use cases it unlocks
And finally, it needs to scale – both in terms of processes and technical requirements
It's worth mentioning that there are several different kinds of rollout you can do.
One of the most common ones is to have something first enabled just in a local environment for a single developer
And then roll it out to a staging environment.So whether that's a preproduction environment or a staging, you can actually use these rollouts to launch something in there.
And then to go from staging out to maybe a small set of Beta users. So there's a different kind of rollout that's actually targeted to a certain audience or a certain whitelist of people that you've specifically decided should see your new stuff. We do this all the time. As a B2B company, we find friendly customers that wanna give new features a try, even some of our bigger companies might be more sensitive. We're not quite ready to try out a new feature until it's more fully baked.
From there, once you've validated in the Beta, you can do a gradual rollout where you slowly ramp up traffic to a larger audience and roll back if anything goes wrong.
And then and only then we can do that 100% rollout where everybody has a new feature. And the key idea here is that we can mix and match these techniques. It's not that one of these is the right answer. I think for each different business and each different product or feature within that, you wanna choose what the right rollout strategy is. But I would argue the right rollout strategy is almost never to just flip the switch. The gradual process is usually much more reliable.
Everything we’re building aligns with one of these principles.
There’s a lot on this slide — I don’t expect you to memorize all of it — but I share it to convey how we’re thinking about the future of in-product experimentation
Everything you see here is either live today or in progress. This will all be available within the next few months
Let’s dig into a few examples
First, I want to talk about developer ease of use — making the process of getting up and running delightful
Recall the architecture slide we spoke about a few minutes ago. I want to highlight one specific piece of this diagram — the datafile, and the process by which it’s downloaded to your SDK
Historically, we left the process of managing your datafile up to our customers. We did this for several reason — e.g. to give folks the flexibility to integrate datafile management with their particular networking constraints.
But leaving this to customers was — excuse my French — a pain in the ass. It meant the developer who’s just getting started had to implement a simple feature before creating their first test or flag.
Here’s an example of a datafile manager — or, at least, part of a datafile manager. There are more than a 100 lines of code here — quite a bit of investment to just get started.
This investment, however, is no longer necessary. Over the past few months, we’ve added automatic datafile management to every SDK…
…replacing the code on the left with a one-line initialization. Installing your SDK is now as simple as a copy and paste.
We validated automatic datafile management by conducting a usability study with twenty engineers.
Among first group, who got started without automatic datafile management, only 1 of 10 were able to create and deploy a flag in <30min
Among the second group, all ten succeeded.
This, in my mind, was a huge win
Lucas Reis, Senior Softare Engineer at Compass, validated the feature, stating that installing the Java SDK with automatic datafile management was simple and smooth.
And, this is just one example of several features we’ve added that make the implementing engineer’s life much easier. For example, we’ve also rewritten our event processor, which eliminates the need to implement a custom event dispatcher – a second hurdle that, like datafile management, new customers were historically required to clear.
With changes like these, we make the process of getting up and running dramatically easier.
Next, let’s talk about governance and process.
Early on, you may be experimenting with a small team;
Everyone knows eachother, what’s happening when and why
But, as you scale, this becomes less and less true.
Multiple teams, multiple parts of your stack, multiple locations.
As this happens, you need governance — an area where Full Stack has historically fallen short.
Over the past three years, the most requested feature missing from our application is Change History – a record of the changes user’s make to their experiments and flags.
I’m happy to report that this gap is nearly closed.
What we’re looking at now is a real screenshot of an in-progress solution — in this case, the Change History view of one of Optimizely’s favorite customers, Dunder-Mifflin Paper.
Let’s consider an example. Imagine that I’m Michael Scott, and I’m curious about a recent experiment.
Specifically, an experiment that launched in early August.
So, I filter my Change History to show only the relevant experiments.
And I find the test I’m looking for
I can then drill into the details of exactly what was changed.
In this case, the experiment key and experiment description were updated, and the traffic allocation was changed — from 50/50 to 60/40
This same sort’ve detail will be available for every change — along with the user, timestamp, and other associated details.
We’re also going to make this data exportable, so that you can integrate your change history with other systems, to provide a comprehensive audit log of your tests and flag.s
All of this is in progress now, and coming very soon. We expect to begin giving customers early access in late October.
We’re also making improvements that will help your scale your experimentation and feature management processes.
For example, we’re now looking at the change history for a somewhat famous paper company, Dunder-Mifflin. And we want to view changes that occured over a three week period in August.
PUNCHLINE: Flexible
Many of you may remember Snapchat's rollout of their new app about a year ago where there was a total backlash on the Snapchat redesign. People hated the new user experience. They didn't like the new navigation. Kim Kardashian loudly announced she was moving to Instagram because of the better UI. And it really blew up in Snapchat's face and in the process drew a big drop in their share price as well because users were flocking away to a different application. There's another case where this experimentation mindset could have really helped avoid this problem. We could have actually caught this challenge much earlier and done much better usability testing or rolled out this new experience to a small segment of users to see how they'd react before blowing sort of the brand on this big launch to the entire customer base at once.
Earlier in this presentation — and in the keynote yesterday — we spoke about the concept of a rollout, i.e. the process of using a feature flag to control the release of a feature. Rollouts are a form of protection against bugs, outages, and other issues, like this example — in which Amazon accidentally made all of their products available for next to nothing.
One of my favorite examples, this is one from a few years ago, Amazon had a glitch in its marketplace where anybody could buy product for a penny. Obviously it didn't last long or Amazon would have been cleaned out, but for a while there, their billing system was screwed up and every product just cost one cent. And so Amazon had a problem where people were going in and buying, you know, hundreds of X boxes for a penny each, so just paying a few dollars for it. And the worst part was they couldn't just cancel these orders because they'd already gone out to third party suppliers for all these things. And so it was a huge mess to untangle all based on a simple software bug that was rounding the wrong way. And we see these all over the place. Sometimes it's these kind of more concrete software errors, but sometimes it's more of a design challenge.
At Opticon two years ago we announced feature management, which allows customers to conduct rollouts — to gradually expose users to…
5%
25%
50%
And eventually 100% of your audience. This kind of safeguard is tremendously powerful, and has become very popular across our customer base.
But the example we’re looking at here is quite simple — just naively exposing percentages of our users to a feature over time.
Oftentimes, you may want to release your feature using more specific rules — to specific users at specific times.
A famous example was described in this economist article a couple of years ago. Are there any Kiwis in the audience? If yes, I apologize, because we’re going to pick on you for a couple of minutes.
The process described here involves launching your feature to a specific country first — in this case, New Zealand. You can think fo New Zealand as a stand-in for any customer group — beta users, or users with a specific subscription — the idea is that we’re isolating audiences during our feature release.
And I'll just throw out one more use case that I think is fascinating and something that we can all take to heart for our own development which is the increasing use of New Zealand as a target for doing stage rollouts. So many companies like Facebook, Yahoo, and Microsoft have started taking new risky product launches and rolling them out to just people in New Zealand before they roll it out to other bigger countries. And they choose New Zealand because it's a pretty small country. It's pretty isolated from other countries where these companies operate. It speaks English. And so the market is somewhat similar to places like the United States or the UK. And a lot of people there are socially connected with technology.
And so what these companies will do is, for example, Facebook will make a bold change to the newsfeed in just New Zealand. And they'll study that entire population to see how it works. And only if they're happy with New Zealand will they continue to roll out to say Australia and then the UK and then the United States. And that way, again, they've contained the damage of the blast radius of this thing they're doing. So I'd encourage all of you to think about what is your New Zealand? Maybe it is New Zealand, maybe it's Beta testers, maybe it's just a random slice of your traffic, but what's that smaller segment that we can actually try out these ideas on?
I’m excited to announce that we’re bringing this capability to Full Stack. In this example, we’re rolling our feature our to four different geos — NZ, USA, France, and Spain.
We begin with our poor friends in New Zealand, launching to 5% of users, then
25%
25%
And eventually 100%
And we only go to 100% once we've validated that rollout at smaller scale. The beauty of this is that if something does go wrong, and let's be honest, with many software launches, something does go wrong...
*** Clarify what feature variables and that they’re configurable remotely
And we only go to 100% once we've validated that rollout at smaller scale. The beauty of this is that if something does go wrong, and let's be honest, with many software launches, something does go wrong...
And we only go to 100% once we've validated that rollout at smaller scale. The beauty of this is that if something does go wrong, and let's be honest, with many software launches, something does go wrong...
It's worth mentioning that there are several different kinds of rollout you can do.
One of the most common ones is to have something first enabled just in a local environment for a single developer
And then roll it out to a staging environment.So whether that's a preproduction environment or a staging, you can actually use these rollouts to launch something in there.
And then to go from staging out to maybe a small set of Beta users. So there's a different kind of rollout that's actually targeted to a certain audience or a certain whitelist of people that you've specifically decided should see your new stuff. We do this all the time. As a B2B company, we find friendly customers that wanna give new features a try, even some of our bigger companies might be more sensitive. We're not quite ready to try out a new feature until it's more fully baked.
From there, once you've validated in the Beta, you can do a gradual rollout where you slowly ramp up traffic to a larger audience and roll back if anything goes wrong.
And then and only then we can do that 100% rollout where everybody has a new feature. And the key idea here is that we can mix and match these techniques. It's not that one of these is the right answer. I think for each different business and each different product or feature within that, you wanna choose what the right rollout strategy is. But I would argue the right rollout strategy is almost never to just flip the switch. The gradual process is usually much more reliable.
It's worth mentioning that there are several different kinds of rollout you can do.
One of the most common ones is to have something first enabled just in a local environment for a single developer
And then roll it out to a staging environment.So whether that's a preproduction environment or a staging, you can actually use these rollouts to launch something in there.
And then to go from staging out to maybe a small set of Beta users. So there's a different kind of rollout that's actually targeted to a certain audience or a certain whitelist of people that you've specifically decided should see your new stuff. We do this all the time. As a B2B company, we find friendly customers that wanna give new features a try, even some of our bigger companies might be more sensitive. We're not quite ready to try out a new feature until it's more fully baked.
From there, once you've validated in the Beta, you can do a gradual rollout where you slowly ramp up traffic to a larger audience and roll back if anything goes wrong.
And then and only then we can do that 100% rollout where everybody has a new feature. And the key idea here is that we can mix and match these techniques. It's not that one of these is the right answer. I think for each different business and each different product or feature within that, you wanna choose what the right rollout strategy is. But I would argue the right rollout strategy is almost never to just flip the switch. The gradual process is usually much more reliable.
It's worth mentioning that there are several different kinds of rollout you can do.
One of the most common ones is to have something first enabled just in a local environment for a single developer
And then roll it out to a staging environment.So whether that's a preproduction environment or a staging, you can actually use these rollouts to launch something in there.
And then to go from staging out to maybe a small set of Beta users. So there's a different kind of rollout that's actually targeted to a certain audience or a certain whitelist of people that you've specifically decided should see your new stuff. We do this all the time. As a B2B company, we find friendly customers that wanna give new features a try, even some of our bigger companies might be more sensitive. We're not quite ready to try out a new feature until it's more fully baked.
From there, once you've validated in the Beta, you can do a gradual rollout where you slowly ramp up traffic to a larger audience and roll back if anything goes wrong.
And then and only then we can do that 100% rollout where everybody has a new feature. And the key idea here is that we can mix and match these techniques. It's not that one of these is the right answer. I think for each different business and each different product or feature within that, you wanna choose what the right rollout strategy is. But I would argue the right rollout strategy is almost never to just flip the switch. The gradual process is usually much more reliable.
We’re supporting 10 years worth of different packages entirely w/ Full Stack Targeted Rollouts
We’re supporting 10 years worth of different packages entirely w/ Full Stack Targeted Rollouts
We’re supporting 10 years worth of different packages entirely w/ Full Stack Targeted Rollouts
We’re supporting 10 years worth of different packages entirely w/ Full Stack Targeted Rollouts
PUNCHLINE: Scalable
Build order: old SDKs, Swift, React, React Native, Go
Swift — working in the iOS language of choice, modernizing 2nd most popular sdk
React — most popular frontend language, again supporting patterns developers prefer
React Native — customers have used the JS SDK in React Native apps, but, we just talked about ease of use, so we want to make the React Native developer’s life easy
Go — finally, over the past 18 months, Go is (by far) the most requested new SDK; it’s in beta now with GA coming very soon
Finally, I want to talk about the feature that I’m most excited about — Full Stack as a Service — something that we believe will be transformative.
Recall the companies we spoke about at the beginning
Netflix, Facebook, Google aren’t just implementing an SDK in a single service
They’re building massive-scale platforms that serve thousands of tests across thousands of users
Our customers are starting to do the same thing.
Consider a hypothetical architecture that contains multiple services — an approach that is increasingly popular among companies today.
One possible approach to installing Full Stack in such an architecture is to embed an SDK in each service — in each application
But, this approach has downsides
It adds significant maintenance overhead
Each team is installing and maintaining their own Optimizely instance
It
- don’t be negative about many SDKs — just explain reasons for different architectural
- Significantly less engineering investment than doing this out of the box
- Reduce engineering effort, not no engineering effort
Now, you may be asking yourself — why am I looking at a slide full of LEGOs? Well, two reasons —
First, for the non-technical folks in the room, the prior explanation may have been a bit inaccessible. A different way to think about it — and an analogy that I like — is to think about product experimentation as a collection of building blocks.
Full Stack historically – and the solutions provided by our competitors — gave you a kit of tools that you could use to implement the platform of your choice. This works — often quite well — but it leaves the task of assembly to the user.
This example solution is technical, and perhaps
Be clear about the purpose of metaphor
Full Stack as a Service replaces that toolkit of disassembled LEGOs with with a much more complete solution — something that looks much more like the finished product.
And our plan is for that finished product to be grand — like the Taj Mahal
Full Stack Service will do everything your SDK does, and a whole lot more. By providing you with a service, rather than an SDK, we can implement sophisticated features that aren’t possible with a simple library.
We’re tremendously excited about this — we have big plans.
- Significantly less engineering investment than doing this out of the box
- Reduce engineering effort, not no engineering effort
Stubhub’s customer experience is driven by algorithms they develop in house
For example, the recommended events you see when you visit Stubhub.com are created by the data science team. They take into account your location, prior purchase and browsing history on the site, time until the event, and many other factors to determine whether to show you sports, music, or other events, which teams, and which events.
Every time they make a change to this algorithm, they are testing how it impacts their conversion rates.
One more customer example — I mentioned a moment ago that many customers have chosen to implement Full Stack as a service
StubHub is one such customer.
And they’ve leveraged that architecture to tremendous gain. StubHub uses Full Stack to experiment on everything
Stubhub’s customer experience is driven by algorithms they develop in house
For example, the recommended events you see when you visit Stubhub.com are created by the data science team. They take into account your location, prior purchase and browsing history on the site, time until the event, and many other factors to determine whether to show you sports, music, or other events, which teams, and which events.
Every time they make a change to this algorithm, they are testing how it impacts their conversion rates.
This is a sample quote slide
Michael Alley, Sr. Product Manager at StubHub, has this to say:
PUNCHLINE: So, you want to get started?
We see Rollouts as a start of a journey and that's why we're making it free, so you can actually start shipping faster with less risk. I'd also encourage you to think about whether you're ready to drive that measurable product impact. So really being able to see the results of those rollouts and measure how different groups are performing. And if so, I'd encourage you to check out Optimizely's Full Stack experimentation as well.
- Be explicit that I’m not committing to deliver dates
- should we remove this
- Be explicit that I’m not committing to deliver dates
- should we remove this