IBM Mobile Quality Assurance Study Group Session 6
•
1 gefällt mir•1,520 views
Part of the MQA Open Beta Study Group series.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie IBM Mobile Quality Assurance Study Group Session 6
Ähnlich wie IBM Mobile Quality Assurance Study Group Session 6 (20)
Mehr von Roger Snook
Mehr von Roger Snook (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
IBM Mobile Quality Assurance Study Group Session 6
- 1. IBM Mobile Quality Assurance (Open Beta) Continuously deliver quality mobile apps, rapidly respond to feedback! MQA Study Group – 20 February 2014 Host: Roger Snook, WorldWide Enablement Leader: Mobile, SOA & Design +1.703.943.1170, RCSnook@us.ibm.com Session 6: Sentiment Analysis (Prior Session Slides and Recordings: http://ibm.co/174C6ug) © 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. Mobile Enterprise Lifecycle “big picture”: Focus on Mobile Quality Design & Develop Instrument Obtain Insight Integrate Manage Test Scan & Certify Deploy 3 #IBMMobile © 2013 IBM Corporation
- 4. Mobile Enterprise Lifecycle supported by a DevOps capability Continuously deliver high quality mobile apps and rapidly respond to feedback. Design & Develop Instrument Obtain Insight Integrate Manage Test Scan & Certify Deploy 4 #IBMMobile © 2013 IBM Corporation
- 5. 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 5 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
- 6. 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 6 • 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
- 7. Streamline the feedback loop into development, before and after release – five use cases (aligned with this Study Group) 2 Report Bugs 3 Developer 7 1 4 Provide Feedback Report Crashes / Logs Distribute to testers and users #IBMMobile Tester 5 Users Analyze AppStore © 2013 IBM Corporation
- 8. Mobile Quality Assurance features that support the Use Cases Session 6 Focus: Sentiment Analysis User Feedback Crash logs 4 Crash log reporting Bugs Bugs vs. Crashes Tester LOB/Digital Marketer Developer 5 Sentiment Analysis Quality Dashboard with Sentiment Analysis 8 1 Over the air build distribution 2 In app bug reporting End Users 3 In app user feedback Builds #IBMMobile © 2013 IBM Corporation
- 9. 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? 9 • • 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
- 10. User Sentiment Mine app ratings and reviews to extract actionable feedback User Sentiment enables key stakeholders throughout the SDLC to •Consolidate all their app store ratings and reviews into easy to view "collections" •Analyze mountains of explicit user feedback about features, performance and usability •Understand what users are saying about their app – why they're cheering and why they're not •Compare their apps against competitors to see how they stack up, and how they can improve end user satisfaction Enables line of business to mine user sentiment 10 #IBMMobile © 2013 IBM Corporation
- 11. User Sentiment User Sentiment Score •Provides overall score •View overall score over time •Compare score over versions Enables line of business to mine user sentiment 11 #IBMMobile © 2013 IBM Corporation
- 12. User Sentiment User Sentiment Attributes •Breaks down score into ten key User Sentiment Attributes •Provide deeper level of insight into areas that require improvement •Compare to competitors across attributes Enables line of business to mine user sentiment 12 #IBMMobile © 2013 IBM Corporation
- 13. User Sentiment User Sentiment Signals •View consolidated positive and negative signals from end user reviews •Match signals to public app store star ratings Enables line of business to mine user sentiment 13 #IBMMobile © 2013 IBM Corporation
- 14. Your next steps: 1. Try It: MQA Open Beta – click on this button from the landing page. 2. Give us feedback directly in the beta site or in the Mobile Learning Circle forum (developerWorks) 3. Visit any of the reference info: • Watch the MQA Tutorial Video • Tools and Technologies for MobileFirst Developers: http://www.ibm.com/developerworks/mobile/ • Read the CTO Mobile Frontier Blog: https://www.ibm.com/developerworks/community/blogs/mobileblog • Watch the PRIOR Study Group sessions 14 #IBMMobile © 2013 IBM Corporation
- 15. IBM Mobile Quality Assurance Open Beta Study Group: http://ibm.co/174C6ug 15 #IBMMobile © 2013 IBM Corporation
- 16. Teşekkür ederim Turkish Hindi Traditional Chinese Gracias Spanish Russian Thank You Obrigado Portuguese English Arabic Danke Grazie German Italian Merci French Multumesc Romanian Simplified Chinese Korean Japanese 16 #IBMMobile © 2013 IBM Corporation
- 17. 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. 17 #IBMMobile © 2013 IBM Corporation
Hinweis der Redaktion
- MAIN POINT: The Mobile Enterprise Lifecycle is more than just creating great code. There are lots of other activities developers (and other team members) get involved in to continuously deliver a high quality mobile app. 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: 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.
- 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
- 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
- Author Note: Optional Rational slide. Graphic is available in English only.