Application Lifecycle Management

For the past couple of years, Dan North has been working with and studying teams who are dramatically more productive than any he's ever seen. In weeks they produce results that take other teams months. One of the central behaviors Dan has observed is their ability to embrace uncertainty, holding multiple contradictory opinions at the same time and deferring commitment until there is a good reason. Embracing uncertainty lies at the heart of agile delivery and is one of the primary reasons organizations struggle with agile adoption. We are desperately uncomfortable with uncertainty, so much so that we will replace it with anything-even things we know to be wrong. Dan claims we have turned our back on the original Agile Manifesto, and explains why understanding risk and embracing uncertainty are fundamental to agile delivery-and why we find it so scary.

Although many software development teams rely on their QA/Test departments to uncover critical product defects near the end of development, we all recognize the inefficiency of this approach. It’s better to find and fix defects earlier in the software development process to save time and money in the long run! Colby Litnak explores key concepts that encourage and empower developers to take primary responsibility for producing quality software. As with a souped-up race car, developers need specially designed tools and practices when they are at the wheel: fail-fast frameworks, one-click test execution, automated defect prevention principles, automatic notifications of untested code, hurtful test failures, and much more. Discover the principles developers must embrace to produce high quality code the first time-before it goes to QA/Test.

Because the mobile market is extremely dynamic, maintaining consistent application quality is always difficult. Managing the risk exposures with mobile apps and embedded software requires comprehensive testing of a wide variety of platforms operating on multiple networks. Testers have to contend with short development cycles that require continuous QA efforts. Three key building blocks are required to overcome these obstacles: device-agnostic automation, access to a large selection of handsets and tablets, and ways to seamlessly apply your existing testing tools, skills, and knowledge to mobile. From his experience working with enterprises going mobile, Eran Yaniv shares the do's and don'ts for selecting an enterprise-grade mobile testing and automation platform, and offers his analysis of the advantages and disadvantages of the various approaches.

Remove software and service dependencies enabling continuous integration and testing across the development lifecycle. Stand up test environments faster and at a lower cost accelerating development and test cycles. Balance quality and speed - deliver high quality software faster.