Mobile DevOps: Rapid Response to Feedback and continuous delivery in a mobile world
Upcoming SlideShare
Loading in...5
×
 

Mobile DevOps: Rapid Response to Feedback and continuous delivery in a mobile world

on

  • 1,083 views

Mobile DevOps from our Senior IBM Product Manager, Derek Baron.

Mobile DevOps from our Senior IBM Product Manager, Derek Baron.

Statistics

Views

Total Views
1,083
Slideshare-icon Views on SlideShare
1,082
Embed Views
1

Actions

Likes
1
Downloads
28
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Mobile DevOps: Rapid Response to Feedback and continuous delivery in a mobile world Mobile DevOps: Rapid Response to Feedback and continuous delivery in a mobile world Presentation Transcript

    • Rapid response to feedback – Continuous delivery in a mobile world Derek Baron – Senior Product Manager Mobile Products ddbaron@us.ibm.com Dec 18, 2013
    • Agenda 1 DevOps 2 Agile mobile app delivery 3 Continuous deployment 4 Quality and feedback © 2013 International Business Machines Corporation 2
    • Software delivery is at the heart of today’s top technology trends Big Data Cloud Insights on new products by more efficiently interpreting massive quantities of data Demand for apps requires fast, scalable environments for dev and test, as well as production Social Business Instrumented Products Broader set of stakeholders collaborates to deliver continuous innovation and value Industry requirements demand faster response to regulations and standards, with traceability and quality Mobile Modern workforce expects constantly updated software to connect to enterprise systems © 2013 International Business Machines Corporation Software delivery Intelligent/ Connected Systems Software component in smart products driving increased value and differentiation 3
    • A lack of continuous delivery impacts the entire business enterprise in the new reality of Systems of Interaction Line-of-business Takes too long to introduce or make changes to mobile apps and services Operations Rapid app releases impact system stability and compliance Systems of Interaction >70% of budgets devoted to maintenance and operations Systems of Engagement >45% Systems of Record CRM HR DB ERP 4-6 weeks to deliver even minor application changes to customers of customers experience production delays >50% Continuous client experience Cloud-based Services Development/Test Speed mismatch between faster moving front office and slower moving back office systems, delaying time to obtain feedback © 2013 International Business Machines Corporation Partner value chain of outsourced projects fail to meet objectives Suppliers Delivery in the context of agile 4
    • DevOps takes a closed-loop approach to application delivery Extending Lean and Agile practices across the entire software value chain Business Owner Idea Service Developer/Tester Plan and Measure Continuous Business Planning Service Operations Develop and Test Release and Deploy Collaborative Development Target Customer Monitor and Optimize Market Continuous Monitoring Continuous Testing Continuous Release and Deployment DevOps Continuous feedback and Optimization Lean and Agile principles © 2013 International Business Machines Corporation 5
    • Agenda 1 DevOps 2 Agile mobile app delivery 3 Continuous deployment 4 Quality and feedback © 2013 International Business Machines Corporation 6
    • Mobile applications shift the development lifecycle focus Lifecycle Focus Time to Feedback Systems of Engagement Systems of Record Time to Certainty Time to Safety Systems of Operation Source: Hammond, Jeffrey. Build Great Mobile Apps That Drive Engagement. Rep. Forrester Research, 25 July 2012. Web. 8 Mar. 2013 © 2013 International Business Machines Corporation 7
    • Poor mobile application quality has real business impact Financial exposure due to security breach $10B of eBay sales done thru Mobile 2 star rating 30% loss of subscribers © 2013 International Business Machines Corporation 8
    • The best mobile apps evolve rapidly in response to feedback Increased customer loyalty by virtue of more compelling and “stickier” self-service options like real-time notification Approximate 80% reduction in per-check-in cost compared to traditional counter check-in Greater than 50% reduction in time required to launch new services or channels through the reuse of existing service assets © 2013 International Business Machines Corporation 9
    • Challenges Company estimated that up to 40 percent of its future business would come from providing mobile accessibility to its products and services. They sought a solution that would provide the scalability needed to support high volumes of data, significant numbers of users and a sizable development team. Solution Implemented IBM Worklight software to support its mobile-application-development project. The Worklight software provides the scalability the client needs to address the predicted increase in data and user volumes anticipated once the project is completed. “We utilize a hybrid/HTML5 approach to achieve our goals with Worklight using web technologies (HTML, Java Scripting, CSS) everywhere we can, and native code where we need to.” © 2013 International Business Machines Corporation Benefits Able to develop mobile apps quickly and efficiently, supporting future business growth at a lower cost than its previous provider could offer. Gained scalability to support higher data and user volumes once the mobile apps were deployed. 10
    • IBM Worklight Mobile application platform to speed development and ongoing management of mobile apps Standards-based cross platform mobile application development Connect and synchronize with back-end systems Governance and security at the application, network and data layer "Best Mobile Development Solution" as voted by SIIA members for 2013 CODiE Awards What’s new in IBM Worklight 6.0 Embedded functional testing Geo-location toolkit Analyze application usage and responsiveness © 2013 International Business Machines Corporation 11
    • Gartner has recognized IBM as a leader in the Magic Quadrant for Mobile Application Development Platforms Magic Quadrant for Mobile Application Development Platforms Ian Finley, Van L. Baker, Ken Parmelee, David Mitchell Smith, Ray Valdes, Gordon Van Huizen Aug 7, 2013 “As unprecedented numbers of enterprises build mobile applications, the mobile application development platform market continues to grow and evolve rapidly.” This Magic Quadrant graphic was published by Gartner, Inc. as part of a larger research note and should be evaluated in the context of the entire report. The full report is available at http://ibm.co/13TU2Dm Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose © 2013 International Business Machines Corporation 12
    • Why is Agile attractive to mobile development teams? Agile teams produce higher quality results, deliver faster, are more likely to deliver the right functionality, and are more likely to provide greater ROI than traditional teams An agile software development project follows an iterative process which is also lightweight, highly collaborative, self-organizing, and quality focused. E.g.: OpenUP, Scrum, and XP. Source: Results from Scott Ambler’s 2011 IT Project Success Survey [www.agilemodeling.com] © 2013 International Business Machines Corporation 13
    • A typical mobile app release schedule Features + Defect fixes V 2.1 V 2.0 V 1.2.1 V 1.2.2 V 1.2 V 1.0 (MVP) New OS version released Regression + Emergency Patch Regular Internal Sprint Cycle + Beta Testing (2 weeks) Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Source: Hammond, Jeffrey. Forrester Research, IBM Innovate 2013, June 2013 © 2013 International Business Machines Corporation 14
    • Agile collaboration imperatives for mobile dev teams Improve quality with Lifecycle Traceability – Example: Trace continuous build/test results to the work that created it Accelerate time to delivery with Real-Time Planning – Example: Adjust plans quickly, based on continuous build/test results and user feedback Maximize product value with In-Context Collaboration – Example: discuss issues within work items; review and approve work; get feedback from stakeholders http://jazz.net/library/article/637 © 2013 International Business Machines Corporation 15
    • hub.jazz.net © 2013 International Business Machines Corporation 16
    • IBM Rational is a recognized leader in ALM “Efficient coordination and automation of the delivery process requires new, collaborative approaches to the planning, measurement, execution, control and reporting of activities.” IBM earns “Strong Positive” ― the highest possible rating “These new approaches are what differentiate current application life cycle management (ALM) tools, and what make ALM processes vital to leading-edge development activities.” “ALM is what enables sustainable agile practices. ALM creates a management framework providing consistent, auditable records of the decisions and activities of agile teams.” Duggan, Jim & Murphy, Thomas E., “MarketScope for Application Lifecycle Management,” Gartner, Inc., 11 November 2010 ID Number: G00208572 , pp2,6 © 2010 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. or its affiliates. This publication may not be reproduced or distributed in any form without Gartner's prior written permission. The information contained in this publication has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information and shall have no liability for errors, omissions or inadequacies in such information. This publication consists of the opinions of Gartner's research organization and should not be construed as statements of fact. The opinions expressed herein are subject to change without notice. Although Gartner research may include a discussion of related legal issues, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner is a public company, and its shareholders may include firms and funds that have financial interests in entities covered in Gartner research. Gartner's Board of Directors may include senior managers of these firms or funds. Gartner research is produced independently by its research organization without input or influence from these firms, funds or their managers. For further information on the independence and integrity of Gartner research, see "Guiding Principles on Independence and Objectivity" on its website, http://www.gartner.com/technology/about/ombudsman/omb_guide2.jsp 17 © 2013 International Business Machines Corporation 17
    • Agenda 1 DevOps 2 Agile mobile app delivery 3 Continuous deployment 4 Quality and feedback © 2013 International Business Machines Corporation 18
    • Continuous build & test leads to usable builds, faster Agile process supported by IBM Rational CLM Mobile App © 2013 International Business Machines Corporation 19
    • Continuous Integration using RTC Rational Team Concert build engine provides gives developers more control and productivity with controlled builds (BOTH individual and team integration) and distributed builds for mobile apps Ant build-script task categories: •Ant-specific tasks – Provide information to Ant and drive overall build flow •Worklight/Mobile tasks – Build and deploy IBM Worklight / Mobile applications and adapters Mobile build server farm Build •Mobile SDK tasks SCM – Produce the native platform binary •RTC tasks executables, logfiles sources – Interact with the build system to define results Worklight Integration RIM SDK © 2013 International Business Machines Corporation Android SDK iOS SDK 20
    • New DevOps solutions for Systems of Interaction Activities across multi-tier app delivery moving at different pace need to be carefully coordinated Rapid deployments Develop Test AppStore Release Systems of Engagement Frequent deployments Develop Test Release Integration Production Environment Cloud Few deployments Transactional systems or packaged apps Systems of Record © 2013 International Business Machines Corporation 21
    • Deployment Automation for Mobile DevOps IBM UrbanCode Deploy v6.0 What’s New • Automatic deployment of mobile applications to IBM Worklight Platform • Support for application deployments to Cloud • Test virtualization support for application deployment • Integrations with Application Lifecycle Management solution the Features/Business Value • Automated application deployment and orchestration • Environment and configuration management • Store deployment artifacts more securely to enable traceability. • Middleware configuration management • Security, approvals and notifications Client Benefits IBM UrbanCode Deploy orchestrates and automates the deployment of applications, middleware configuration, and database changes into development, test, and production environments, accelerating time to market and reducing cost by shrinking manual efforts from days to minutes with automation, while reducing risk by cutting deployment errors by up to 90 percent. © 2013 International Business Machines Corporation 22
    • IBM UrbanCode Deploy V6.0 integration with IBM Worklight V6.0 The new plugin enables automated deployment to Worklight Console and Application Center Supports Worklight Apps targeting iOS and Android SCM UrbanCode Deploy Process Worklight Console runtime calls CodeStation Build .wlapp Application Center Install/update app adapter Binary (IPA/APK) Use App Server, Database and other plugins to configure environments and Worklight projects © 2013 International Business Machines Corporation 23
    • Agenda 1 DevOps 2 Agile mobile app delivery 3 Continuous deployment 4 Quality and feedback © 2013 International Business Machines Corporation 24
    • What do mobile testers need? Test Management Manual Testing Service Virtualization Security Testing • Test planning, reporting, and dashboarding • Test case, suite, environment construction • Integration with ALM • Integration with multiple execution engines • Still most used mobile testing method • Necessary for some validation • Integration with test management • Frequently key in outsourcing and crowd sourcing scenarios • Isolate front-end from backend • Control over data and interface • Decrease expensive set-up costs • • • • Network connections Server data Client data Injections and data flow analysis Device Access Performance Testing Mobile UI Automation • Remotely accessible • Shareable across teams / geographies • Access to diverse selection • Device clouds minimize cost of ownership • • • • • Device / platform agnostic • Application instrumented automation • Optical / image recognition automation © 2013 International Business Machines Corporation Middle-tier and back-end Mobile client code Mobile network Mobile client experience 25
    • Automated Mobile App Functional Testing IBM Rational Test Workbench Comprehensive Playback Recording • Android and iOS, Native, hybrid, and web Complete • Record, edit, and run on mobile devices Reporting Authoring Resilient • Same test runs across multiple devices Simple • Natural language scripts for developers and nondevelopers alike • Leverage production-like environments using “Being agile, we are developing tests as we write our code, so automating the virtualized services functional tests of our mobile apps and using them for regression on multiple platforms makes our team much more productive!” Mobile developer. Shifting mobile testing to the left: test earlier, more often, for less. © 2013 International Business Machines Corporation 26
    • Virtualize back-end services to maintain agility Mobile development team can meet aggressive schedules and reduce MIPS usage on enterprise systems Rational Test Workbench Client Tier Devices UI Testing © 2013 International Business Machines Corporation Service Virtualization support for isolating mobile client tier For focused automated mobile client tier functional testing, use Service Virtualization to simulate the mobile middle tier and back office systems. 27
    • A Problem Statement to be Addressed Enterprises need to deliver high quality mobile apps that fully engage their customers with high ROI quickly, but they don’t have the confidence to answer the following questions in pre-production and production: • How well does the mobile app work? • How much do customers like it? • How well does it meet the business objectives? • What can we do to improve in the next update? © 2013 International Business Machines Corporation 28
    • IBM Mobile Quality Assurance Open Beta http://bit.ly/mobile-quality-assurance Features/Business Value • Sentiment analysis – mine app ratings and reviews to respond to issues before they go viral • Evidence-based Prioritization – Enable business and IT to collaborate on mobile strategy and user experience • Over the air app distribution – get the latest in the hands of testers as soon as it is available • Frictionless bug reporting – spend every minute on testing latest and greatest builds, not the hassles • In-app crash reporting – rapid understanding of why an app fails © 2013 International Business Machines Corporation What’s New • End user feedback and quality metrics available at every stage of development • App quality assurance in a fragmented and complex environment Client Benefits • Improve Mobile App Quality with holistic visibility into user experience, including bugs, crashes, feedback, and user sentiment. 29
    • Reducing Time to Feedback Initial release will address five key use cases, attacking pain points for all key users User Feedback Crash logs 4 Crash log reporting Bugs vs. Crashes Bugs LOB/Digital Marketer Developer 5 Sentiment Analysis Quality Dashboard with Sentiment Analysis 1 Over the air build distribution End Users Tester 2 In app bug reporting 3 In app user feedback Builds © 2013 International Business Machines Corporation 30
    • Combine strategies to reduce response time to feedback The best mobile apps evolve rapidly in response to feedback and needs Release cycles take too long and cost too much Late understanding of feedback means poor ratings fester App passed build and tests Continuous Build & Test • • • • • In-app bug reporting Crash logs In-app user feedback App Store analytics Crash results Feedback Management Continuous Innovation, Feedback and Improvements © 2013 International Business Machines Corporation 31
    • IBM solutions seen today: Worklight – Develop multi-tier, multi-platform, business critical mobile apps Rational Collaborative Lifecycle Management – Agile process support for mobile teams – Continuous Integration for mobile Rational Test Workbench – Mobile app UI testing Rational Test Virtualization Server – Virtualize backend systems for mobile apps UrbanCode Deploy – Automate mobile app deployments as part of a DevOps practice Mobile Quality Assurance Open Beta – http://bit.ly/mobile-quality-assurance © 2013 International Business Machines Corporation 32
    • Increase your velocity 1 2 3 Download the free IBM Worklight Developer Edition: ibm.co/worklightde Take part in the IBM Mobile Quality Assurance open beta: https://ibm.biz/BdDSHt Learn more: ibm.com/mobilefirst © 2013 International Business Machines Corporation 33
    • © 2013 International Business Machines Corporation 34
    • Legal Disclaimer © IBM Corporation 2013. All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. If you reference Java™ in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only. © 2013 International Business Machines Corporation 35