Requirements
Conference Presentations
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
|
|
Develop a Defect Prevention Strategy—or Else!
Slideshow
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
|
|
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.
|
|
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
|
|
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
|
|
Ambiguity Reviews: Building Quality Requirements
Slideshow
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
|
|
Testing Lessons Learned from Monty Python
Slideshow
And now for something completely different... |
Rob Sabourin, AmiBug.com
|
|
Why Classic Software Testing Doesn’t Work Anymore
Slideshow
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
|
|
Better Software Conference East 2013: Data Collection and Analysis for Better Requirements
Slideshow
According to studies, 64 percent of features in systems are rarely—or never—used. How does this happen? Today, the work of eliciting the customers' true needs, which often remains elusive, can be enhanced using data-driven requirements techniques. Brandon Carlson describes why traditional... |
Brandon Carlson, Lean TECHniques, Inc.
|
|
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
|