Conference Presentations

Requirements Are Requirements—or Maybe Not

Many people talk about requirements. They 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 yet another has a different approach. These “experts” seem unaware of...

Robin Goldsmith, Go Pro Management, Inc.
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
Non-Functional Requirements: Forgotten, Neglected, and Misunderstood

Implementing non-functional requirements is essential to build the right product. Yet teams often struggle with when and how to discover, specify, and test these requirements. Many teams neglect non-functional requirements up front, considering them less important or unrelated to user...

Paul Reed, EBG Consulting
Meeting Strict Documentation Requirements in Agile

Teams in many organizations are still expected to produce and maintain significant amounts of documentation. This is generally the case in Federal, state, and local governments where systems must comply with SOX, HIPPA, NAIC, FDA, or SEC directives. In recent years, Agile has made...

Craeg Strong, Savant Financial Technologies, Inc.
Avoiding Over Design and Under Design

The question of how much design to do up-front on a project is an engaging conundrum. Too much design often results in excess complexity and wasted effort. Too little design results in a poor architecture or insufficient system structures which require expensive rework and hurt more in the...

Al Shalloway, Net Objectives
Develop a Defect Prevention Strategy—or Else!

Defects occurring throughout the development of a software project penalize the project. The effort spent remediating these defects robs the project team of valuable time, resources, and money that could otherwise be used for further innovation and delivering the highest possible quality...

Scott Aziz, Cognizant
Testing Lessons Learned from Monty Python

And now for something completely different...

Rob Sabourin,
Top Challenges in Testing Requirements

Studies show that at least half of all software defects are rooted in poor, ambiguous, or incomplete requirements. For decades, testing has complained about the lack of solid concrete...

Lloyd Roden, Lloyd Roden Consultancy
Ambiguity Reviews: Building Quality Requirements

Are you frustrated by the false expectation that we can test quality into a product? By the time an application is delivered to testing, our ability to introduce quality principles is...

Susan Schanta, Cognizant Technology Solutions
Why Classic Software Testing Doesn’t Work Anymore

The classic software testing team is becoming increasingly obsolete. Traditional processes and tools just don’t meet today’s testing challenges. With the introduction of methodologies...

Regg Struyk, Polarion Software


AgileConnection is a TechWell community.

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