Conference Presentations

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
Requirements and Acceptance Tests: Yes, They Go Together
Slideshow

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
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
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
Meeting Strict Documentation Requirements in Agile
Slideshow

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

And now for something completely different...
Rob Sabourin, AmiBug.com

Pages

CMCrossroads is a TechWell community.

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