Conference Presentations

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
The Agile PMO: Right Work, Right Time, Right People

One of the core functions of a PMO is to help an organization standardize efficient processes to select and execute strategic projects. Unfortunately, many PMOs are finding themselves struggling to justify their own existence. In a recent survey, more than half of the respondents reported...

Heather Fleming, Gilt Groupe, and Justin Riservato, Gilt Groupe
Seven Deadly Habits of Ineffective Software Managers

As if releasing a quality software project on time were not difficult enough, poor management of planning, people, and process issues can be deadly to a project. Presenting a series of anti-pattern case studies, Ken Whitaker describes the most common deadly habits—along with ways to avoid...

Ken Whitaker, Leading Software Maniacs
Product Management: Optimizing the What to Develop

Most organizations struggle with the processes that define what software they should develop, when to do it, and how it will evolve over time—all parts of the product management role and activities. Because repeatable processes have not been established and organizations cope with...

Ernani Ferrari, Mondo Strategies
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
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.
Balancing the Crusty and Old with the Shiny and New

In his journeys, Bob Galen has discovered that testing takes on many forms. Some organizations have no automated tests and struggle to run massive manual regression tests within very short iterative releases. Other organizations are going “all in”―writing thousands of acceptance tests...

Bob Galen, Velocity Partners
When Testers Feel Left Out in the Cold

When you're responsible for testing, it's almost a given that you will find yourself in a situation in which you feel alone and out in the cold. Management commitment for testing might...

Hans Buwalda, LogiGear
ADC-BSC EAST 2013 Keynote: Reading the Tea Leaves: Predicting a Project’s Future

Is a project’s fate preordained? Does a project’s past suggest its likely future? Can anything be done to influence that future when the current signs aren’t promising? Payson Hall has participated in and reviewed many projects during his thirty-year career in software development.

Payson Hall, Catalysis Group Inc.


AgileConnection is a TechWell community.

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