Introducing Continuous Quality

Editor's Notes

• #5: There’s a but, High user expectations. As complicated as the mobile content delivery chain complete with both back end and third party services / ad networks or the fact that the quality of user network conditions vary widely – users expect apps to work, and work flawlessly with near immediate responsiveness. Mobile has nearly eliminated any switching cost between apps. Users encountering a negative experience are highly likely shift their attention and engagement to a competitive offering. This also extends to vendors who fail to leverage the very latest mobile innovation including the internet of things trend. Keep up or risk being abandoned. DAUs/MAUs (ratio of daily active users to monthly active users) – What percentage of your users are visiting every day? You can also break this down and see what percentage of your users are visiting 8 times a month, 4 times a month, etc.Average visits per month – How often does each user open the app? Some app managers look at the inverse of this which is visit interval or what is the average time between visits. You can look at it either way. The insight is similar.Time in app – How long is the duration of each visit?Screen views – How many screens is each user visiting?Retention – What percent of new installs are visiting the next day, the day after that, the day after that, etc.? The most common metric for this is 30/60/90 day retention (how many users are still visiting 30, 60, and 90 days after the first install).
• #6: It’s clear, SOME enterprises are realizing material top line revenue growth driven by investing in quality mobile experiences. For example, numerous banks are already projecting when mobile will become the primary customer engagement point. Retailers Source: Harvard Business Review: Business Transformation and the CIO Role https://enterprisersproject.com/sites/default/files/Business%20Transformation%20and%20the%20CIO%20Role.pdf
• #8: Revenue data – source: Marriott, Security Analyst Meeting Transcript, September 8, 2014 Marriott seeks mobile contextual moments that matter (http://www.mobilecommercedaily.com/marriott-seeks-mobile-contextual-moments-that-matter) Marriot Mcommerce Conference May 2014 Marriott is analyzing target customers to understand how extend engagement with customers by analyzing which contextual moments can most effectively be address via. The commitment to become a mobile first company are driving top line outcomes – 10% of revenue is direwctly attributable to mobnile
• #12: This is our point of view of the challenges
• #14: Build #1 – Test automation pyramid, developed by Mike Cohn, 2009. Describes a test strategy that suggest the greatest investment should be in testing the smallest units of code. From there the next investment should be on system or integration testing. And the smallest investment made at the most brittle application layer the UI #2 – While this is an excellent investment strategy, the objective should be on building “automation that actually works.” Automation should be viewed and treated as code and not a second class citizen. Therefore, reuse should be planned for in day one with thoughts of building a framework or component library at the forefront of each automation team’s agenda. Recognizing the uniquely mobile aspects of apps, effective test automation will require control of both the system (or for iOS springboard) level control AND in-app control. Combined these will enable coverage. #3 The Always Ready Lab – automation alone is not good enough for mobile. Mobile app quality requires access to a test environment that is nearly a production replica without burdening devtest teams the burden of managing 20, 30, 5o devices in house or worse in numerous difference locations. #4 CI Nearly every app team is striving to accelerate and CI is emerging as a leading solution. Automation is cornerstone for these strategies to become effective – Automating the process and testing along with an always ready lab provides teams with fast feedback #5 Service virtualization is being rapidly adopted by team struggling due to lacking access to services provided by systems of record or third party providers. SV enables teams to execute testing while mimicking the behavior and data flows of these systems. #6 Fundamental to truly optimizing flows for faster delivery is recognizing that common out of cycle tests should coincide with earlier testing phases.