IBM Mobile Quality Assurance - Open Beta Study Group Session 1
•Descargar como PPT, PDF•
2 recomendaciones•5,355 vistas
IBM is introducing a new Mobile Quality Assurance tool in open beta to help organizations continuously deliver high quality mobile applications. The tool provides features across the mobile development lifecycle like over the air app distribution to testers, in-app bug reporting, direct user feedback collection, crash log reporting, and planned sentiment analysis of app store reviews. These capabilities are meant to streamline the feedback loop from users and testers to development teams to integrate user input before and after application releases. The goal is to improve mobile app quality and proactively manage quality risks through rapid issue identification and reduced development cycles.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (11)
Similar a IBM Mobile Quality Assurance - Open Beta Study Group Session 1
Similar a IBM Mobile Quality Assurance - Open Beta Study Group Session 1 (20)
Más de Roger Snook
Más de Roger Snook (20)
Último
Último (20)
IBM Mobile Quality Assurance - Open Beta Study Group Session 1
- 1. IBM Mobile Quality Assurance Continuously deliver quality mobile apps – MQA Study Group - 25 October 2013 Host: Roger Snook, WorldWide Enablement Leader: Mobile, SOA & Design +1.703.943.1170, RCSnook@us.ibm.com © 2013 IBM Corporation
- 2. Please note – This discussion is about an Open Beta IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. 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. 2 #IBMMobile © 2013 IBM Corporation
- 3. A business in motion must be MobileFirst Mobile enables the Mobile enables the Internet of Things Internet of Things Mobile is primary Mobile is primary 91% of mobile users keep 91% of mobile users keep their device within arm’s their device within arm’s reach 100% of the time reach 100% of the time Global Machine-to-machine Global Machine-to-machine connections will increase connections will increase from 22billion in 2011 to 18 from billion in 2011 to 18 billion at the end of 2022 billion at the end of 2022 Mobile must create aa Mobile must create continuous brand continuous brand experience experience Insights from mobile Insights from mobile data provide new data provide new opportunities opportunities 90% of users use multiple 90% of users use multiple screens as channels come screens as channels come together to create together to create integrated experiences integrated experiences 75% of mobile shoppers 75% of mobile shoppers take action after receiving aa take action after receiving location based messages location based messages Mobile is about transacting Mobile is about transacting 96% year to year increase in mobile cyber 96% year to year increase in mobile cyber Monday sales between 2012 and 2011 Monday sales between 2012 and 2011 3 #IBMMobile © 2013 IBM Corporation
- 4. Since apps just don’t fall out of the sky..... Mobile application development is a top priority for businesses! 35% of developers are currently 29% of mobile developers targeting tablets, with more than 90% plan to develop for tablets in the near future. currently focus on Hybrid app development. In the next 12 months 77% of developers will be focused on Hybrid application development. Nearly 90% of developers are currently extending enterprise apps to mobile or plan to in the near future. More than 200m people updated to iOS7 in the first week 25+ Almost all expect to deploy more than 25 mobility applications in the next two years Source: Evans Data Mobile Developer Survey Mobile Development Report 2012 Volume Source: Business Insider (September 2012) 4 #IBMMobile © 2013 IBM Corporation
- 5. Why mobile development is different Development is different. Mobile apps are different. • They are more strategic – Greater urgency and immediacy of engagement • They are context-aware –know where you are and what you are doing • They run on unstable networks–interruption is the norm, not the exception • Smaller footprint – More challenging to make compelling and easy to use • Always on – An opportunity to deliver greater value Security is different. Management is different. • Smaller screens pulling content from more sources: need to choreograph content from multiple repositories and applications , both on premises and in the cloud • Greater challenges of application governance, distribution, and version management • AppStore Terms of Service present challenges for managing B2C apps 5 • Faster development cycles • More devices to support, each with its own set of capabilities, OS and UI behaviors • More development approaches to choose from – Web, HTML, Native • More third-party and open-source tools, frameworks and libraries to choose from • Consumerization of Technology is changing the definition of mobile app quality #IBMMobile • Greater risks of exposing applications and data on small, light and always on portable devices • Greater authentication challenges associated with content mashups • AppStore Terms of Service can limit security options © 2013 IBM Corporation
- 6. A mobile enterprise lifecycle has many “success disciplines” Design & Develop Instrument Obtain Insight Integrate Manage Test Scan & Certify Deploy 6 #IBMMobile © 2013 IBM Corporation
- 7. Organizations that effectively leverage software development outperform their competitors... yet few are able to deliver it effectively 86 % of companies believe software delivery is important or critical of those who leverage software delivery today 69 But only… 25 % leverage software delivery effectively today % outperform those who don’t Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013 7 #IBMMobile © 2013 IBM Corporation
- 8. IBM MobileFirst offering portfolio Industry Solutions Banking Insuranc e Retail Transpor t Telecom Government Healthcare Automotive Strategy & Design Services Application & Data Platform Management Devices Security Network Analytics Servers Development & Integration Services IBM & Partner Applications Cloud & Managed Services 8 #IBMMobile © 2013 IBM Corporation
- 9. Mobile enterprise lifecycle: Focus on Mobile Quality Design & Develop Instrument Obtain Insight Integrate Manage Test Scan & Certify Deploy 9 #IBMMobile © 2013 IBM Corporation
- 10. Mobile quality has a tremendous business impact: Quality vs Time $10B of eBay sales done thru Mobile Financial exposure due to security breach The same percentage of mobile developers who claim Testing and Quality Assurance is in their top 5 concerns… Also claim they are SD Times: “More than challenged with half of organizations are building mobile developing applications as applications” http://www.sdtimes.com/link/36553 quickly as management wants 10 #IBMMobile 2 star rating 30% loss of subscribers © 2013 IBM Corporation
- 11. Mobile application quality is more complex 100,000+ different devices for Android devices only, 500+ brands Doesn’t account for OS versions, carriers or locations Doesn’t account for iOS, Windows Phone or Blackberry 11 #IBMMobile © 2013 IBM Corporation
- 12. Mobile quality presents unique needs Consumerization of Technology is Changing the Definition of Quality − Usability and fit-to-purpose are important aspects of perceived quality − Quality of Experience is defined as “the overall acceptability of an application or service, as perceived subjectively by the end user.” Time to Feedback − Mobile engagement requires a lifecycle focus on “time to feedback” − Shorter iterations, and more frequent delivery − Majority of the testing performed by developers Focus is on reducing time to feedback vs. bug count 12 #IBMMobile © 2013 IBM Corporation
- 13. Mobile Quality automation fundamental to a DevOps Lifecycle Continuously deliver high-quality mobile applications (HTML5, hybrid and native) and support multiple mobile operating environments and devices with the simplicity of a single, shared code base DevOps Lifecycle Customers Business Owners Development/Test Operations/Production Systems of Interaction Continuous Innovation, Feedback and Improvements Develop and Test Worklight IBM Mobile Quality Assurance Rational Test Workbench Release and Deploy Best Practices Ecosystem Plan and Measure Monitor and Optimize Judge mobile application quality and customer readiness across multiple dimensions, to deliver apps that better meet customer expectations 13 Automate and orchestrate the delivery pipeline for IT infrastructure and the mobile app, reducing cycle times to respond faster to feedback #IBMMobile © 2013 IBM Corporation
- 14. Updated xx-xx-12 Introducing IBM Mobile Quality Assurance (beta) Continuously deliver high quality mobile applications What’s New • End user feedback and quality metrics available at every stage of development IBM Mobile Quality Assurance (beta) • App quality assurance in a fragmented and complex environment Features/Business Value • 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 • Sentiment analysis – mine app ratings and reviews to extract actionable feedback before they go viral(coming soon) Client Benefits 14 • Improve mobile app quality with holistic visibility into user experience, including bugs, crashes, feedback, and user sentiment • Proactively manage quality risks through rapid assessment of issues and reduced cycle time #IBMMobile ”What you are talking about doing is fantastic. You have a very powerful approach here and it will drive a lot of what people will want to do in the market” © 2013 IBM Corporation
- 15. Streamline the feedback loop into development, before and after release – five use cases (aligned with this Study Group) 2 Developer 1 15 Report Bugs Distribute to testers and users 5 4 Tester 3 Provide Feedback Users Devices Report Crashes / Logs Analyze AppStore #IBMMobile © 2013 IBM Corporation
- 16. Mobile Quality Assurance features that support the Use Cases User Feedback Crash logs 4 Crash log reporting Bugs vs. Crashes Bugs LOB/Digital Marketer Developer Coming soon 5 Sentiment Analysis 1 Over the air build distribution 2 Quality Dashboard with Sentiment Analysis 16 Tester In app bug reporting End Users 3 In app user feedback Builds #IBMMobile © 2013 IBM Corporation
- 17. Helping the software team get smarter about their mobile apps “When someone leaves a negative review in the app store, it scars your app for life, you can’t respond to it, and you can’t learn more about the problem in order to fix it quickly.” - Mobile Orchard LOB/Digital Marketer Developer • How effective our mobile app is at engaging customers? • How can I stay on top of current quality metrics, and turn them into an actionable strategy? 17 • • How could I get visibility to issues that customers experience in production so that I can address them quickly? How can I get more people to test the apps so that we can cover different devices, network carriers, #IBMMobile and OS versions? End Users Tester • • How can I get the latest and greatest build without wasting my time to track that down? How can I quickly submit bug reports with screenshots and device details right from the application? • How can I provide direct and constructive feedback? © 2013 IBM Corporation
- 18. Over the air app distribution Developer uploads new build Identifies test devices IBM MQA notifies testers Testers download new version through the app or thru IBM MQA Enables developers to distribute new builds to test devices 18 #IBMMobile © 2013 IBM Corporation
- 19. In app bug reporting When bugs are identified, user simply shakes their device 1. IBM MQA is activated 2. Bug details are reported in structured manner to RTC Bug details include •Device maker & model •OS & version •Carrier & connection speed •Battery life & resolution •Repro steps & screenshot Enables developers to receive bug reports 19 #IBMMobile © 2013 IBM Corporation
- 20. Direct user feedback Developers can customize the feedback workflow When user has feedback, they trigger a feedback widget IBM Mobile Quality Assurance is activated Free-form feedback is shared directly to IBM MQA Enables developers to connect with users 20 #IBMMobile © 2013 IBM Corporation
- 21. Crash log reporting When your app crashes, IBM MQA logs the event IBM MQA captures the crash details •Device maker & model •OS version •Carrier & connectivity •Battery life •Stack trace •Logs IBM MQA aggregates all crashes into an easy-to-use reporting UI Enables developers to know when and why crashes occur 21 #IBMMobile © 2013 IBM Corporation
- 22. IBM Mobile Quality Assurance 22 #IBMMobile © 2013 IBM Corporation
- 23. Sentiment Analysis Mine app ratings and reviews to extract actionable feedback IBM MQA allows users to see •Review stats on their mobile apps •Detailed attribute scores •Cumulative sentiment score and trends Coming soon – Not yet in Open Beta Enables line of business to mine user sentiment 23 #IBMMobile © 2013 IBM Corporation
- 24. Evidence-based prioritization Collaborate on mobile strategy and end user experience IBM MQA delivers •Tracking of app installations •Cumulative usage sessions •Crash report tracking over time Enables prioritization of action on mobile app development 24 #IBMMobile © 2013 IBM Corporation
- 25. Your Study Group Action Items for Today: 1. Take Brief Survey – Your feedback helps! (Coming soon to your inbox) 2. Try It: MQA Open Beta http://www.quality4mobile.com NOTE: This is the current URL and may change in the future. To be sure you can access this, use the landing page. 25 #IBMMobile © 2013 IBM Corporation
- 26. Ways to get started with IBM MobileFirst 1 2 3 Tools and Technologies for MobileFirst Developers: http://www.ibm.com/developerworks/mobile/ Take part in the IBM Mobile Quality Assurance open beta: http://ibm.co/174C6ug Read the CTO Mobile Frontier Blog: https://www.ibm.com/developerworks/community/blogs/mobileblog Our Next Session: IBM Mobile Quality Assurance Study Group Session 2: Viewing crashes and bug reports Nov 1, 2013 9:00 AM https://events.na.collabserv.com/register.php?id=44a9a6a4dd&l=en-US Further Study: Mobile Learning Circle (coming soon) Mobile Testing Product Usage Learning Roadmap (coming soon) 26 #IBMMobile © 2013 IBM Corporation
- 27. 27 #IBMMobile © 2013 IBM Corporation
- 28. 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. 28 #IBMMobile © 2013 IBM Corporation
Notas del editor
- MAIN POINT: There is a lot of compelling data in the marketplace, but we have identified five key trends or observations – supported by market data and by customer successes – that we believe have strong implications for the future of mobile. SPEAKER NOTES: [1] Mobile is the universal sensor. It is with most of us 100% of the time and is the primary means we use to interact with our employers, our customers, our family and our friends. [2] As they interact they are creating vast streams of data that, with the right analytics, can teach us things about their behavior and their preferences that we could not learn in any other way. [3] These interactions inherently become transactions. Whether shopping, purchasing, searching for or providing information, collaborating or seeking service, mobile enabled people and objects are seeking not simply to connect, but to complete tasks when, where and how they wish. [4] Thus, the mobile experience must transcend any single device to accommodate multiple screens and touchpoints. [5] Finally, as we think about mobile, we can’t confine our thinking to devices like phones and tablets. The ability to tag things, sense things, power things and shrink things has extended mobility beyond people to nearly every other type of object on the planet. As we have said since the start of smarter planet things are becoming more instrumented, interconnected and intelligent than ever before, and mobile is right at the center of that story and will fundamentally change the way the world works. I just highlighted five key mobile trends that drive IBM’s strategy of the mobile enterprise market. Each trend brings with it an opportunity that I want to highlight here. Trend Opportunity 1. Mobile is primary Transform the value chain 2. Insights from mobile data provide new opportunities Deliver contextually relevant experience 3. Mobile is about transacting Drive revenue and productivity 4. Mobile must create a continuous brand experience Deepen engagement 5. Mobile enables the Internet of Things Leverage industry transformations Let’s begin with the first key trend, that mobile is about transacting and all of the notions that make up a “transaction”. Let’s flesh that out a bit further, because with each trend comes opportunities that your enterprise should leverage. With mobile transactions, the opportunity is to drive new and additional revenue and productivity through mobile. This requires businesses to re-imagine every interaction in a Mobile First world. Moving to the second trend you highlighted around mobile insights – this brings with it an opportunity to deliver a contextually relevant experience to your employees, partners and customers. This enables you to harness deep insights to inform new mobile innovations. Thirdly, mobile is primary. We all know that already. So what does it mean to you and your business? Simply put, you deliver mobile apps that transform the value chain because you recognize the importance of prioritizing ‘mobile first’ since it is the way of the future. Moving along, let’s focus on this requirement that a user’s experience must be consistent across all channels. We must prioritize and leverage user imperatives to benefit the enterprise, meaning you can deepen relationships with consistent brand experience by integrating your front-end presence regardless of hardware or operating system it is presented on with your back-end, regardless if its locally or remotely hosted infrastructure. The ‘how’ doesn’t matter anymore – people expect it to work seamlessly. Lastly, let’s move beyond phones. Because ‘mobile’ really isn’t just about a phone, or a tablet. By broadening our scope of what we consider ‘mobile’ we capitalize on other opportunities for your business. Machine-to-machine is HUGE. Thus, why not leverage industry transformations driven by M2M through cloud technologies and whatever comes along next in order to capitalize on this 18 billion opportunity expected by the end of 2022.
- The Situation: Mobile First applications allow you to turn every interaction into an opportunity for value. Whether they help you to create deeper engagement with your customers, enable your employees to work more productively, or connect you to your ecosystem of partners, the application is often the first point of contact and it must allow users to take action anytime and anywhere.
- Anyone/anything/anywhere While the opportunities mobile presents are significant and mobile has become an enterprise requirement, it’s not simple to: Engage with anyone especially if they own and control their own device Extend to anything – think about the volume of different types of smart mobile device platforms out there – not to mention other types of instrumented machines and back-end systems. Execute real business anywhere – full business transactions need to be enabled with low latency request/response characteristics 24x7 from anywhere in the world at anytime.
- MAIN POINT: A DevOps approach to delivery of mobile applications is crucial. DevOps and its set of principles and best practices enables mobile teams to rapidly deliver quality mobile applications that fully engage the end-user, integrate seamlessly with back-end systems of record, and interact with their environment and the systems of operation. This is an aspirational framework – not all teams will undertake all of these activities for each project. But it’s a way of thinking about continuous delivery of mobile apps, and applying the same discipline to this lifecycle as you do any business-critical process. Let’s look at the steps in this lifecycle: Design We start with designing the user experience, optimally using an outside-in approach. (Worklight) Develop We design the architecture and develop the application, using a cross-platform development approach that will maximize code reuse. (Worklight) Instrument We instrument the application for your application for analytics, security, and management control. (Tealeaf) Integrate –We integrate with back-end data, systems and cloud services. (Worklight, Cast Iron) Test –We test the application (Rational Test Workbench) Certify – We use a vulnerability analysis tool scan, evaluate, and certify your application (AppScan) Deploy -- We distribute the applications –using a combination of internal and external App Stores ( to Worklight and back-end servers with UrbanCode Deploy; to managed devices with Endpoint Manager; Worklight’s integrated catalog for unmanaged devices, and external App Stores) Manage – Using the Worklight Application Console, we manage authentication, enforced updates, and versions. Obtain Insight – We analyze and improve the effectiveness of your application design by viewing detailed customer usage patterns (Tealeaf) And of course this understanding influences the next iteration of our product design, closing the iterative circle.
- Main Point: We know organizations have a gap between the software delivery capabilities they need to succeed and the ones they have in house currently. Successful organizations know that when they improve their abilities in this area, they increase their success. In fact a recent IBV study where organizations self-reported that... Insights from 435 executives in 58 countries, spanning 18 industries 85% realize and reported it is important to critical Only 25% say they are able to fully leverage software delivery effectively So there is a gap -- but when companies that can close the resulting execution gap stand to benefit. Almost 70 percent of the companies currently leveraging software development for competitive advantage outperform their peers from a profitability standpoint TRANSITION – so there is a huge opportunity for our clients to close that gap…let’s move to the next slide and talk about how -------------------------------------------------------------------------------------------------- Note: Outperformers were determined by a self-assessment of profitability against peers in the industry, ranging from 1 (Significant underperformers) to 5 (Significant outperformers) Significant outperformers were ranked as a 5, Average performers a 3-4 and Underperformers 1-2 new Rational/WebSphere IBV Study "The Software Edge - How effective software development drives competitive advantage" This study examined the correlation between software delivery competency and industry competitive advantage Insights from 435 executives in 58 countries, spanning 18 industries Roles included executives at director level and above in IT and other software organizations Software delivery refers to all areas of development, operations, and support within IT and other development / engineering organizations “There was 54% of the companies who said they believe software is critical and 32 percent who called it moderately important – so that’s 86 percent of the respondents say software is either critical or moderately important and that points to the need for better tooling for software development and delivery.” said Randy Newell, director of capabilities marketing for IBM Software Group with a focus on the Rational brand.
- This chart represents all of what IBM is doing in mobility on a single page. When we launched MobileFirst back in February at the Mobile World Congress in Barcelona, we were reacting to the fact that no one in the industry had yet laid out a vision of the key services and capabilities that will be needed in this technology transition. Now we know that you all work with many vendors and partners, so think of this as a blueprint for what you need (you may not get everything from IBM, but we will work to provide the integration across these areas to make things go smoother). Today I want to focus on some of the key areas, going around the chart to highlight some of what we do and what’s new in each of the areas. Let’s begin with the application and data platform.
- MAIN POINT: A DevOps approach to delivery of mobile applications is crucial. DevOps and its set of principles and best practices enables mobile teams to rapidly deliver quality mobile applications that fully engage the end-user, integrate seamlessly with back-end systems of record, and interact with their environment and the systems of operation. This is an aspirational framework – not all teams will undertake all of these activities for each project. But it’s a way of thinking about continuous delivery of mobile apps, and applying the same discipline to this lifecycle as you do any business-critical process. Let’s look at the steps in this lifecycle: Design We start with designing the user experience, optimally using an outside-in approach. (Worklight) Develop We design the architecture and develop the application, using a cross-platform development approach that will maximize code reuse. (Worklight) Instrument We instrument the application for your application for analytics, security, and management control. (Tealeaf) Integrate –We integrate with back-end data, systems and cloud services. (Worklight, Cast Iron) Test –We test the application (Rational Test Workbench) Certify – We use a vulnerability analysis tool scan, evaluate, and certify your application (AppScan) Deploy -- We distribute the applications –using a combination of internal and external App Stores ( to Worklight and back-end servers with UrbanCode Deploy; to managed devices with Endpoint Manager; Worklight’s integrated catalog for unmanaged devices, and external App Stores) Manage – Using the Worklight Application Console, we manage authentication, enforced updates, and versions. Obtain Insight – We analyze and improve the effectiveness of your application design by viewing detailed customer usage patterns (Tealeaf) And of course this understanding influences the next iteration of our product design, closing the iterative circle.
- Enterprises that don't pay attention to this often find that mobile app quality can have a huge affect on their business, driving how their brand is perceived. Here are just a few examples of what can happen with poor quality, including loss of sales and security exposures. The bottom line is that businesses who deliver high quality mobile apps that engage their customers will thrive. Businesses that fail to deliver quality will see results like the ones on this slide. eBay: http://www.ecommercebytes.com/cab/abn/y12/m09/i14/s01 NatWest: http://www.independent.co.uk/news/uk/home-news/natwest-suspends-getcash-app-over-fraud-concerns-8205756.html WSJ: http://www.nngroup.com/articles/why-wsj-mobile-app-gets-bad-reviews/
- Traditional Test Lab Model is losing relevance Less time for traditional staging and full regression testing Majority of the testing performed by developers Rapid change of mobile apps undermines the effectiveness of automated GUI testing More focus on field testing to address Combinatorial # of devices, network carriers, OS versions, etc Context awareness of mobile apps: location, applications interactions Variable device states (connected/disconnected, device orientation, no GPS signal, etc.)
- It is important to note that Mobile app quality management is different from that for systems of records applications. Mobile as a result of IT consumerization is changing definition of quality and lifecycle focus. And the focus has shifted from bug counts for system of records to reducing time to feedback with shorter iteration and more incremental and frequent delivery for systems of engagements. Traditional test lab is losing relevance with more and more testing done by development. There is less time for traditional staging and full regression testing. More and more mobile teams leverages field testing to address the complexity of mobile testing. And they see the need to get immediate user feedback, including sentiment analysis, and be able to respond to feedback quickly. Quality of Experience is defined as “the overall acceptability of an application or service, as perceived subjectively by the end user.” by ITU- T P.10/G.100 Almost 12,000 different Android devices creating huge fragmentation issues “There are almost 12,000 unique Android devices on the market” “In terms of operating system fragmentation... the report found that 8 different versions of Android were still in use. “ “...among all of the different Android versions lie mobile operator and manufacturer "skins", adding yet more variety to an already complex marketplace”
- SPEAKER NOTES PRESENTERS may want to delete speaker notes prior to presenting to clients/external audience Offering Name: IBM Mobile Quality Assurance Offering Description: IBM Mobile Quality Assurance provides everything an organization needs to deliver high quality mobile apps, bringing together in one place, user feedback, app performance, test results, bug reports, and sentiment analysis to drive prioritization and development of mobile app updates that address issues before they affect reputation. Target Market/Industries: All What is New News? This is a brand new SaaS offering, being delivered as a free open beta for all organizations needing to deliver the highest quality mobile apps possible. Client Needs Addressed: Making sure that the app design meets the end user need and achieves the business objectives Verify that the app works correctly in a fragmented (complex) environment of mobile devices and operating systems Value Proposition: (Describe how the offering helps the consumer improve operations, deliver/access new capabilities, increase revenues/profits, perform roles more efficiently, perform functions previously not possible ) IBM Mobile Quality Assurance provide line of business professionals with insightful and streamlined quality feedback and metrics, enabling them to dramatically improve decisions on mobile app priorities and investments. IBM Mobile Quality Assurance equips mobile app development teams with everything they need to deliver the highest quality mobile applications through rapid inclusion of quality feedback throughout the development cycle. Key Benefits: (for Launch Theme) Over the air app distribution – get the latest in the hands of testers as soon as it is available In-app crash reporting – rapid understanding of why an app fails In-app user feedback – frictionless way to determine user likes and dislikes Sentiment analysis – mine app ratings to respond to issues before they go viral Competitors & Differentiation: (List appropriate competitors and key differentiation from IBM vs. Competitors) TestFlight Crittercism Bugsense Jira Mobile Connect HockeyApp; Zubhium Differentiation: Mobile specific aggregated feedback for rapid assessment of quality and prioritization of effort Incorporate end user feedback and quality data at every stage of development Assess how the app behaves across many combinations of devices, diverse network conditions, and with back end service Sparklers: (Measurable or significant performance/capability facts or proof points) bullet bullet Quote is from Ken Parmalee, Gartner Research
- So, with those pain points in mind, our initial tech preview will focus on five key use cases… For the DEVELOPER: Over-the-Air Build Distribution – Developers can distribute new builds over-the-air to real devices for testing purposes; automatically ensures that testers have the latest build For the TESTER: In-App Bug Reporting – Bug reports can be submitted directly from the app; available for pre- and post-launch; importantly, this also saves the contextual information around the bug, packaging up what is needed (like crash logs) to make it easy to get them to the developer For the END USERS: In-App User Feedback – User feedback can be submitted directly from the app, enabling developers to easily spot trends, discover issues and receive new ideas from end users; also …Crash Reporting – Automated, real-time crash reports are filtered by OS version, device and other parameters; available for pre- and post-launch For the LOB / Digital Marketer: Sentiment Analysis, providing these users with details from the app stores on user feedback for their impressions or “sentiment” regarding mobile applications; this is based on crawling through every rating and review and then boiling it down to a single score as a means to measure user satisfaction… this will allow clients to monitor and measure how their mobile apps are performing in the eyes of users.
- Over the air build distribution: Distribute build to tester, beta users, etc. Automatically sign mobile apps Ensure testers test the latest build In-app bug reporting: Submit bug right from mobile device Save contextual data Over-the-Air Build Distribution – Developers can distribute new builds over-the-air to real devices for testing purposes Crash Reporting – Automated, real-time crash reports are filtered by OS version, device and other parameters; available for pre- and post-launch In-App Bug Reporting – Bug reports can be submitted directly from the app; available for pre- and post-launch In-App User Feedback – User feedback can be submitted directly from the app, enabling developers to easily spot trends, discover issues and receive new ideas from end users
- Author Note: Optional Rational DEMO slide. Available in English only.
- Marketing is the science of choosing target markets through market analysis and market segmentation, as well as understanding consumer buying behavior and providing superior customer value. Source: http://en.wikipedia.org/wiki/Marketing
- IBM Mobile Quality Assurance Overview and Use Cases (Mobile Study Group Session 1) Oct 25, 2013 9:00 AM - https://events.na.collabserv.com/register.php?id=89922788f7&l=en-US IBM Mobile Quality Assurance Study Group Session 2: Viewing crashes and bug reports Nov 1, 2013 9:00 AMhttps://events.na.collabserv.com/register.php?id=44a9a6a4dd&l=en-US IBM Mobile Quality Assurance Study Group Session 3: Connecting mobile app end-users and the developer environment Nov 8, 2013 9:00 AMhttps://events.na.collabserv.com/register.php?id=b6855e07bb&l=en-US IBM Mobile Quality Assurance Study Group Session 4: Over the air build distribution Nov 15, 2013 9:00 AMhttps://events.na.collabserv.com/register.php?id=6ab12a9957&l=en-US IBM Mobile Quality Assurance Study Group Session 5: Mobile user sentiment and analytics Nov 22, 2013 9:00 AMhttps://events.na.collabserv.com/register.php?id=bdba44a231&l=en-US