We need to start taking requirements seriously.  The impact of missed requirements can cost organizations millions and damage reputations.

The problem is actually a people problem.  Communication, collaboration, and the ability to properly use techniques such as observation will help address some issues.

Don’t get more detailed than you need to for the situation.  Doing so artificially constrains creativity to develop a solution.

Listen to the full episode to hear Jerry’s views on the challenges associated with software requirements and what to do about it.

http://traffic.libsyn.com/masteringbusinessanalysis/MBA130.mp3

Start talking requirements seriously.  Explore options and impacts to understand your requirements.  Finally, iterate on your requirements.  You can’t know everything upfront.

Author, Teacher, Consultant

For more than half a century, Jerry Weinberg has worked on transforming software organizations, particularly emphasizing the interaction of technical and human issues. After spending between 1956 and 1969 as software developer, researcher, teacher, and designer of software curricula at IBM, formed the consulting firm of Weinberg & Weinberg to help software engineering organizations manage the change process in a more fully human way.

Jerry has published more than 40 books and more than 400 articles including books on quality software management, systems thinking, and requirements.

• Twitter
• LinkedIn

To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes and other podcatchers.

Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.

.      

The post MBA130: Exploring Requirements with Jerry Weinberg appeared first on Mastering Business Analysis.