Conference Presentations

Collocated East Logo Requirements Are Simply Requirements—or Maybe Not
Slideshow

When talking about requirements, people 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.
Requirements Are Simply Requirements—or Maybe Not
Slideshow

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.
Agile Dev, Better Software & DevOps Conference West 2015: EARS: The Easy Approach to Requirements Syntax
Slideshow

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
Agile Development Conference & Better Software Conference East 2014: EARS: The Easy Approach to Requirements Syntax
Slideshow

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
Slideshow

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
Avoiding Over Design and Under Design
Slideshow

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
Requirements Are Requirements—or Maybe Not
Slideshow

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.
Testing Lessons Learned from Monty Python
Slideshow

And now for something completely different...

Rob Sabourin, AmiBug.com
Top Challenges in Testing Requirements
Slideshow

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
Requirements Elicitation—the Social Media Way
Slideshow

Agile methods have proven their ability to improve project success rates. However, when agile methods are applied to complex projects, we need to further explore the area of effective customer involvement. According to the agile philosophy, the users must be part of the development team.

Stefano Rizzo, Polarion Software

Pages

AgileConnection is a TechWell community.

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