Conference Presentations

Uncovering User Needs with Critical Incident Task Analysis

What do users really need? Do they really know what they need? Although developers and testers are expected to implement stories and requirements that add real value, users often describe wants rather than needs and ask for features rather than solutions. Rob Sabourin shares his experiences applying task analysis using the “critical incident method” to better understand user processes and determine needs and desired solutions. Rob does not ask “what the system should do for the user” but rather learns “what the user does with the system.” The critical incident task analysis method is a fast and systematic way to study user experiences and analyze business needs. From brilliant successes and dismal failures we learn to identify and understand the user process.

Rob Sabourin, AmiBug.com, Inc.
Measure the Measurable: Improving Software Quality Through Telemetry

Observing customers in a usability lab can be invaluable for improving product design. But, once your software leaves the lab, do you know what your customers are actually doing and whether or not your software meets their expectations? Learn how engineers on the Microsoft Office team apply a variety of software telemetry techniques to understand real-world usage, how the results drive product improvements, and how you can apply similar techniques.

Jamie Campbell's picture Jamie Campbell
working together Harvesting Stakeholder Perspectives to Organize Your Backlog

When Mary Gorman and Ellen Gottesdiener facilitated a game called The Backlog Is in the Eye of the Beholder for the Boston chapter of the International Institute of Business Analysis, both the players and the facilitators learned some important lessons in organizing a project requirements backlog. In this article, they describe the game and what it revealed, including the value of truly knowing your stakeholders.

Enterprise Agile and the Business Analyst

Agile is making its way into the enterprise as a project methodology for industrial-strength projects. Why the popularity? The answer lies in the requirements paradox: “We want requirements to be stable, but requirements are never stable.” Discover some key agile concepts as they affect business analysts.

John C. Goodpasture's picture John C. Goodpasture
Busted: 5 Myths of Testing Regulated Software

Testing regulated software is often seen as a tedious job that generates stacks of documentation and is subject to crippling rules. See five of these assumptions exposed as mere myths, and learn how regulated testers can use the same approaches, techniques, and tools at any other tester's disposal while still passing a process audit.

John McConda
Simplify Your Combinatorial Testing

Combinatorial testing is effective for testing multiple, non-sequential inputs that affect a common output in complex software. But, it's easy to misapply it or become a slave to the output. Learn to overcome limitations and benefit fully from this technique.

Bj Rollison's picture Bj Rollison
Four Paths To Predictable, Repeatable, Reusable Test Data

Modern applications operate in highly integrated environments, and critical systems rely on massive amounts of data that likely contain sensitive information. Discover useful strategies for preparing your baseline, handling interfaces, designing input data, and planning for output results.

Linda Hayes's picture Linda Hayes
Believe the Territory

Test plans are seldom followed as written, project plans hardly ever fit the actual progress, and process models are rarely followed to the letter. Markus Gaertner examines why most of our documents become obsolete and gives advice about whether or not to continue to write and maintain them.
 

Markus Gärtner's picture Markus Gärtner
The Weekend Testers

This is the true story of freedom from the monotonous work of checking. It is the story of what happened when a few passionate testers took responsibility for their own education and fun in testing. Explore how they test, learn, and contribute to the open source.

A Release Without a Tester

In this article inspired by an unfortunate video store rental, Lee Copeland invites software organizations that think testing is expensive to try the alternative.

Lee Copeland's picture Lee Copeland

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.