Conference Presentations

Requirements Are Simply Requirements—or Maybe Not

People talk about requirements, use identical terms, and think they have a common understanding. Yet, one says user stories are requirements; another claims user stories must be combined with requirements; and another has a still different approach. These “experts” seem unaware of the...

Robin Goldsmith, Go Pro Management, Inc.
Mobile App Testing: Design Automation Patterns You Should Use

In mobile app development, better test design is important to project velocity and user satisfaction. Jon Hagar explores underused or poorly practiced test design automation approaches that you should employ in development and testing. Jon begins by defining the domain of mobile app...

Jon Hagar, Grand Software Testing
Conflict: To Know It Is to Love It

We all talk about conflict. We all experience it. But do we really understand what causes it and how we deal with it? Do we have any idea what to do about it? Much research and study has been done, but that doesn't help when you're in the middle of conflict. You don't have time to...

Doc List, Doc List Enterprises
Enough about Process, Let’s Use Patterns

When new developers and testers join the company, we want them to learn the “way we do software here.” So we give them the “stone tablets”―the volumes of process documentation― to study. However, the problem is that the details in this documentation are primarily for beginners and don’t...

Paul E. McMahon, PEM Systems
EARS: The Easy Approach to Requirements Syntax

One key to specifying effective functional requirements is minimizing misinterpretation and ambiguity. By employing a consistent syntax in your requirements, you can improve readability and help ensure that everyone on the team understands exactly what to develop. John Terzakis provides...

John Terzakis, Intel
Lean Software Development Is for Everyone

Lean software engineering emphasizes continuous delivery of high quality applications. Ken Pugh explains the principles and practices that form the basis of lean software development―concentrating on developing a continuous flow by eliminating delays and loopbacks; delivering quickly by...

Ken Pugh, Net Objectives
Requirements and Acceptance Tests: Yes, They Go Together

The practice of software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust. Developers implement their perceived interpretation of requirements; testers test against their perceptions. Disagreement can...

Ken Pugh, Net Objectives
Innovation for Existing Software Product: An R&D Approach

In the world of software, innovating an existing product often makes the difference between continued success and rapid irrelevance and failure. Although innovation can come from many different sources, it can be difficult to develop breakthrough innovations while simultaneously...

Aaron Barrett, Infusionsoft
Making Numbers Count: Metrics That Matter

As testers and test managers, we are frequently asked to report to stakeholders on the progress and results of our testing. Questions like How is testing going? may seem simple enough, but the answer is ultimately based on our ability to extract useful metrics from our work and present...

Mike Trites, PQA Testing
User Stories: From Fuzzy to Razor Sharp

User stories are the basis for products built using agile development. User stories are relatively short, comprised of enough information to start the development process, and designed to initiate further conversation about details. Short doesn’t necessarily mean useful. Ambiguous stories...

Phil Ricci, Agile-Now


AgileConnection is a TechWell community.

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