Welcome to Requirements.net!

Requirements.net is home of the industry consortium for business analysis. Through focus on requirements definition, visualization, and management, the companies behind Requirements.net are driven to share and sponsor best practices and technologies to improve industry requirements practices.

There are currently no upcoming events.

See All Events »

Entries Tagged as 'Best Practices'

When “Story Cards” are Not Enough…

Posted May 6th, 2008 by Martin Crisp

A popular and valuable technique within Agile development teams is to create a “story card“, to capture requirements. Although initially created for iteration and release planning purposes, you can sometimes get away with using the story card as the requirement spec, as it may provide “just enough” details.
These story cards, which are typically […]

Requirement Ranking - No, No, No to High, Medium or Low

Posted April 25th, 2008 by Steven Davis

Many software development teams today are faced with developing twice as much in half the time for even less budget. The risks this imposes to the business expecting and needing the software is much too high. A mechanism to deal with the risk is to rank and then prioritize requirements. Ranking requirements […]

Prioritizing Requirements

Posted April 9th, 2008 by Patrick Walsh

One key factor that is often overlooked or underestimated during requirements elicitation is prioritizing requirements. If there are 150 documented itemized requirements, and 147 can be met by a software solution, you may think that would be a great percentage to have. But what if the 3 requirements that were not/cannot be met were the […]

Elicit Requirements for Business Needs, not Wants

Posted April 3rd, 2008 by Steven Davis

The following is a mission statement for every software development or maintenance team:

To promise and deliver to the business,
on time and within budget,
innovative software
that meets end user needs and expectations
requiring minimal rework and maintenance.
This mission statement says a lot but let’s focus on business needs this time. […]

Eliciting Requirements and Linking Them Downstream

Posted April 2nd, 2008 by Tracy Lynne Dedore

In the context of a software project or application, requirements management is the translation of the business goals and objectives into a realized, software-enabled business process. Requirements are really a complex chain of business, technical, functional, performance and security requirements that drive a complex chain of activities with a lot of involvement from […]

Developers: Requirements Management Leads to Fun

Posted March 18th, 2008 by Gerald Heller

A note to software developers: By managing requirements you can have more fun! Don’t believe me?
Indeed, we’re sure you don’t like being bothered with all that requirements “stuff” because it hinders you from spending time on tasks that allow you to be creative, such as design and coding. Consider what typically happens: Requirements are documented, […]

Reduce Software Rework Costs with Pennies

Posted March 17th, 2008 by Steven Davis

Software rework, as everyone knows, is a scourge of many software development and maintenance efforts. This has been the case since software was first developed. A major reason for software rework has been a lack of quality and detail in elicited software requirements. This has been known for many years, but unfortunately knowing the issue […]

Improve Requirements through Capturing User Interactions

Posted March 17th, 2008 by Matt Morgan

Check out this awesome post (by Keith Harrison-Broninski) on RQNG that focuses on improving project success rates by capturing user interactions.
From the post:
In the end, software applications are only there to support human work. Even a low-level, highly automated software application for (say) car numberplate recognition or payroll calculation is only there to meet the […]