Test Manager

Tired of the claims that Scrum, XP, and kanban don’t scale beyond a few teams? Overwhelmed by management’s resistance to the organizational changes needed to really follow agile principles? Concerned with the lack of proven practices required to scale agile methods to the next level? Exploring the Scaled Agile Framework™, Dean Leffingwell dispels these claims and answers these questions—and more.

With the rapid rise of mobile devices including smartphones and tablets, many organizations are rolling out mobile apps to extend the reach of their traditional web applications. Although the methodology for mobile application testing is fundamentally the same as that of traditional web and desktop application testing, mobile apps testing presents some unique challenges and issues including coverage of a myriad of mobile devices, usability testing, integration of mobile testing with web interface testing, mobile app performance, and security issues.

Requirements defects are often the source of the majority of all software defects. Discovering and correcting a defect during testing is typically twenty-five times more expensive than correcting it during the requirements definition phase. Identifying and removing defects early in the software development lifecycle provides many benefits including reduced rework costs, less wasted effort, and greater team productivity. This translates into software projects that deliver the committed functionality on schedule, within budget, and with higher levels of customer satisfaction.

Erik Costlow says that, as more and more business is transacted on mobile platforms, securing the applications and data that run on them is a business imperative. Developers and their managers are asked to make key decisions regarding data caching, authorized permissions, authentication requirements on the backend, and safe coding practices—all of which contribute to the protection of their organization’s intellectual property. However, hackers have taken advantage of a knowledge gap to develop creative attacks against mobile applications.

Continuous delivery is a practice that enables teams to release code at any time, based on changing business requirements. However, continuous delivery requires a substantial investment in infrastructure and possibly fundamental architectural changes to support the process. Anti-patterns that would render a continuous delivery pipeline a burden rather than a beneficial tool for continuous delivery must be avoided.

What can we learn from Angry Birds, which has been downloaded more than one billion times? What makes games engaging and fun? What is the secret that motivates players to mastery, even when they fail 80 percent of the time? What if we could reverse-engineer the principles behind a well-designed game and graft them to a real-life business challenge? Based on psychology, design, strategy, and technology, gamification is an emerging and exciting concept. Ram Srinivasan describes the principles behind player engagement, social connectivity, and self-motivation to mastery.

Kent Beck, inventor of eXtreme Programming, defined agile success as delivering more useful functionality with fewer defects. Against that definition, early research revealed mixed success. Many organizations did not know how to measure and thus could not have “fact-based” conversations about productivity and cost. Some teams achieved faster delivery, but quality did not improve. Others found both. What factors made the difference? New benchmark analysis by QSM Associates reveals the latest productivity, time-to-market, quality, and cost patterns.

One of software development’s  greatest challenges is combining business needs with technical abilities to build products that customers want. Many development methodologies attempt to achieve this, but Nir Szilagyi and Janarthanan Eindhal think that few connect the dots as well as behavior-driven development (BDD), an agile development methodology derived from test-driven development (TDD) and other agile practices. Unlike TDD, which focuses on code design, BDD focuses on the customer.

The key impediments that prevent many organizations from ever realizing the promise of agile and lean aren’t rooted in processes or tools. The impediments stem from the organization’s leaders. Sharing an interdisciplinary overview of the most compelling science and research in the aspects of team performance, Michael DePaoli shows that it is largely ignored.

Until 2009, the Atlassian JIRA team shipped a major release of its software every nine to twelve months. Everything was tested—every story and every bug fix—and everything still contained serious bugs. Story development moved quickly, but after the feature-complete date, several month-long hardening periods were required to make the software actually shippable. Integrating the release into Atlassian’s hosted platform took another three or four months.

Most of us take language for granted. We use words without thinking about how they may affect others and then are surprised at the reaction we get. Learn the importance of language in building and maintaining high performing agile teams. Become more aware of the words you choose and the impact of those words on your listeners. Steven “Doc” List presents a series of exercises in a game show format. Participants attempt to identify loaded words in seemingly simple statements and questions. Some of the exercises are written, others are acted out in role play.

Every decision made during the course of a project can affect the quality of the final product.  Compromises in functionality, design, or implementation invariably come with a cost, which must be paid. Without an adequate measure of the debt a product is carrying, no strategy to repay it can be formulated, and the project may ultimately become bankrupt, affecting your business case, your users’ productivity, and your organization’s bottom line. Taking from the concept of technical debt, Jordan Setters gives it a quality twist.

Is agile—or lean, kanban, lean startup, etc.—starting to follow the path of other management buzzwords in your organization? Is it losing steam, now resembling only a minor change from the old ways? Have you compromised to "make agile work in our organization?” As organizations introduce new paradigms, they often run into roadblocks of inertia. When these are not overcome, the initial excitement and the potential benefits drain away. Treating changes such as agile as merely a software delivery approach typically means disregarding four other key facets of the agile organization.

There is no doubt that agile is an accepted development methodology. However, if you work in a regulated industry like health care where you have to comply with its standard operating procedures, heaps of paperwork, and frequent audits, don’t these conflict with agile’s core tenets? Chris Ampenberger describes his operating environment and the applicable regulations that define the constraints for the software development process he can use. He shares how they overcame the incongruity between agile and regulatory requirements.

The Kanban Pizza Game is a hands-on simulation designed to teach the core elements of a kanban system—visualize the workflow, limit your work-in-process (WIP), manage flow, make process policies explicit, and improve collaboratively.

Organizations are under pressure to release faster with higher quality, while business and technology environments are increasingly becoming more and more complex. How can you deploy great products quickly in such a challenging environment? Intuit, maker of TurboTax, is solving this problem with continuous delivery practices. Continuous delivery is the next stage of agile, allowing organizations to achieve greater velocity, repeatability, and sustainability through a continuous build, test, and deploy process.