STARCANADA 2018 - Tutorials

Avoiding siloed development is a tricky business. It’s so easy for agile teams to fall into the rut in which testers only do traditional testing activities, and programmers strictly do their time-worn coding activities. Rob Sabourin shares a number of examples of how testing skills can be applied to a wide variety of activities in an agile project. Testers are among the most skilled team members in story grooming, elicitation, and exploration. Risk analysis in self-organized agile teams empowers testers to drive design decisions. A tester’s affinity analysis skills help clear the way for...

To be most effective, those in testing roles (whether Agile or traditional) must develop and use metrics to help the team direct the testing effort and help the team make informed recommendations about the software’s release readiness and associated risks. Because one important testing activity is to “measure” the quality of the software, teams must measure the results of both the development and testing processes. Collecting, analyzing, and using metrics are complicated because many developers and testers are concerned that the metrics will be used against them. Join Mike Sowers as he...

Cognitive Adaptive Testing means harnessing the power of analytics and autonomics in support of continuous delivery. The emergence of cognitive, adaptive testing is driven by trends towards omnichannel content delivery, utilization of big data and improved customer experience. Our software/systems need to be extremely responsive to customer sentiment, work across a variety of devices, be resilient in the face of unpredictable failure modes, and process vast amounts of unstructured data. Such scenarios put extreme pressure on IT systems and processes to be not only more responsive but...

Anyone who has ever attempted to estimate software testing effort realizes just how difficult the task can be. The number of factors that can affect the estimate is virtually unlimited. The keys to good estimates are understanding the primary variables, comparing them to known standards, and normalizing the estimates based on their differences. This is easy to say but difficult to accomplish because estimates are frequently required even when we know very little about the project—and what we do know is constantly changing. Throw in a healthy dose of politics and a bit of wishful thinking,...

Innovation is a word frequently tossed around in organizations today. The standard cliché is “Do more with less.” People and teams want to be innovative but often struggle with how to define, prioritize, implement, and track their innovation efforts. Jennifer Bonine shares the Innovation Types model to give you new tools to evolve and expand your innovation capabilities. Find out if your innovation ideas and efforts match your team and company goals. Learn how to classify your innovation and improvement efforts as core (to the business) or context (essential but non-revenue generating)....

Agile teams deliver “potentially” shippable software at the end of every iteration (one to four weeks) or possibly every day. Janet Gregory says that this goal can't be achieved without automated tests, and many teams struggle with test automation. The challenge of automating functional regression tests frightens many testers, who feel their skills aren’t up to the job. So, how can you deliver good quality when you have to release so often? By combining a collaborative team approach with appropriate tools and design approaches, you can not only automate your regression tests but also use...