Login

Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  How to shoot yourself in the foot. 7 ways to do software requirements poorly
Previous Previous
 
Next Next
New Post 6/2/2010 6:27 AM
User is offline Seilevel
13 posts
10th Level Poster


How to shoot yourself in the foot. 7 ways to do software requirements poorly  
Modified By Adrian M. on 6/6/2010 3:38:03 AM)

How to shoot yourself in the foot.

7 ways to do software requirements poorly to set your project up for failure and what to do instead.

 
By Bhoffman
 
Why spend precious project cycle time on software requirements rather than just getting down to business on design and implementation? Back in the 1970’s Barry Boehm published extensive data from large projects showing that an error created early in the project, for example during requirements specification, costs 50 to 1,000 times as much to correct late in the project as it does to correct (or avoid) close to the point where it was originally created. His landmark study has been confirmed over and over again on countless projects in the decades since.
 
Why are errors so much more costly to correct downstream? There are two main reasons: project artifacts to be corrected increase over time and more people need to get involved in defect correction as the life cycle progresses. A poor requirement or an unneeded requirement will become the ‘tip of the iceberg’ ...
 
This is a lengthy article that includes pictures. To view the rest of this article please click here.
 
 
 Page 1 of 1
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  How to shoot yourself in the foot. 7 ways to do software requirements poorly

Community Blog - Latest Posts

Jayaram.K
Jayaram.K

DOR & DOD: The BA’s Compass in Agile Delivery

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
Jayaram.K
Jayaram.K

The Business Analyst's Superpower: Bridging the Gap Between Business and IT

In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
Bekka Ball
Bekka Ball

Recipe Redesign: There Is No Box, Only Possibilities

I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 



Upcoming Live Webinars




 

brought to you by Modern Analyst Media LLC enabling practitioners & organizations to achieve their goals using:

Copyright 2006-2025 by Modern Analyst Media LLC