Over the years, I’ve come to the conclusion that one of the most destructive notions circulating inside technical groups involves “gathering requirements.” For decades, virtually everyone in the industry has accepted that the first phase of every IT project should be to gather requirements from business users. At least in theory, it should be the point of departure for all our efforts. (Of course, it’s also the phase of the project that’s most often skipped.) So now that our success rate for IT projects has risen to the still-dismal level of about 25%, perhaps we should question some of this time-honored wisdom.
Calculating ROI on your Investment in Requirements Management Tools
There’s no question that a commercial Requirements Management tool is very useful; but, can it pay for itself at your company? In this article we’ll look at a model to help you calculate ROI on Requirements Management tools.
10 Tips to Gather Business Requirements
Definition: Differentiate between client and customer: client is someone who would like your help in creating a product or service for someone; a customer is the person who pays for some service or product.
Requirements for Effective Boards Beyond Fine Tuning
As CEO, you’re accountable for results whether your board helps or hinders you in working toward them. Ensuring that key requirements are met, requirements that affect how well equipped board members are to work together, will provide a sound foundation from which the strategic leadership and fulfillment of role and responsibilities will more likely occur. These requirements go beyond fine tuning they are essential.